From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Georg Faerber <georg@riseup.net>, notmuch@notmuchmail.org
Subject: Re: viewing duplicate messages
Date: Sun, 28 Jul 2019 21:07:56 -0400 [thread overview]
Message-ID: <8736ipveab.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20190717150849.GA8232@debian>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
On Wed 2019-07-17 15:08:49 +0000, Georg Faerber wrote:
> On 19-07-17 14:50:50, drebs wrote:
>> When I send a message to a schleuder list, it is first encrypted to
>> the list's OpenPGP certificate before leaving my computer. Schleuder
>> will then decrypt it and re-encrypt to the subscribers' certificates,
>> and it will maintain the Message-Id untouched.
>
> FWIW: That's configurable, see [1]. Unfortunately, that's currently the
> only place which documents this kind of stuff.
fwiw, i don't think setting keep_msgid: false in schleuder is a good
answer, because setting it causes pretty nasty threading failures.
hopefully we can think through a better approach for dealing with this
from the client side.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-07-29 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 14:50 viewing duplicate messages drebs
2019-07-17 15:08 ` Georg Faerber
2019-07-29 1:07 ` Daniel Kahn Gillmor [this message]
2019-07-29 13:34 ` Georg Faerber
-- strict thread matches above, loose matches on Subject: below --
2019-05-30 16:34 Rollins, Jameson
2019-05-30 22:11 ` Jorge P. de Morais Neto
2019-05-30 22:17 ` Rollins, Jameson
2019-05-30 23:02 ` Daniel Kahn Gillmor
2019-05-31 15:45 ` Jorge P. de Morais Neto
2019-05-31 16:32 ` Daniel Kahn Gillmor
2019-08-17 22:12 ` Jorge P. de Morais Neto
2019-08-18 20:20 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736ipveab.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=georg@riseup.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).