From: Michael Alan Dorman <mdorman@ironicdesign.com>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH (rebased)] Handle message renames in mail spool
Date: Fri, 4 Dec 2009 13:52:20 -0500 [thread overview]
Message-ID: <20091204135220.0a8e38c2@vimes.local> (raw)
In-Reply-To: <87aaxysjdj.fsf@vertex.dottedmag>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Sat, 05 Dec 2009 00:07:36 +0600
Mikhail Gusarov <dottedmag@dottedmag.net> wrote:
> The only problem with Cc is that Mailman suppresses duplicate
> messages and hence there is no List-Id: on message.
Err, this makes no sense. How can Mailman have any knowledge of, and
therefore "do anything" to any message that came by way of a CC?
Now, your mail transfer agent might do duplicate suppression, and if
the direct email reaches you before the one that went through the
mailing list, you won't have a copy that includes the list-id header,
but that's an issue on your end, not with the mailing list software.
Mike.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-04 18:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 20:23 [PATCH] Handle message renames in mail spool Mikhail Gusarov
2009-12-02 21:15 ` [PATCH (rebased)] " Mikhail Gusarov
2009-12-04 0:45 ` Carl Worth
2009-12-04 13:55 ` david
2009-12-04 18:05 ` Carl Worth
2009-12-04 18:07 ` Mikhail Gusarov
2009-12-04 18:35 ` Carl Worth
2009-12-04 18:42 ` Mikhail Gusarov
2009-12-04 19:09 ` Michael Alan Dorman
2009-12-05 0:32 ` Carl Worth
2009-12-05 0:39 ` Carl Worth
2009-12-05 0:47 ` Mikhail Gusarov
2009-12-05 8:51 ` Marten Veldthuis
2009-12-05 22:48 ` Carl Worth
2009-12-16 23:51 ` Bdale Garbee
2009-12-17 0:01 ` Mikhail Gusarov
2009-12-17 2:57 ` Bdale Garbee
2009-12-17 1:36 ` Michael Alan Dorman
2009-12-04 18:52 ` Michael Alan Dorman [this message]
2009-12-04 18:55 ` Mikhail Gusarov
2009-12-04 19:40 ` Michael Alan Dorman
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=20091204135220.0a8e38c2@vimes.local \
--to=mdorman@ironicdesign.com \
--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).