Date: Fri, 4 Dec 2009 13:52:20 -0500
From: Michael Alan Dorman <mdorman@ironicdesign.com>
To: notmuch@notmuchmail.org
Message-ID: <20091204135220.0a8e38c2@vimes.local>
In-Reply-To: <87aaxysjdj.fsf@vertex.dottedmag>
References: <1259267025-28733-1-git-send-email-dottedmag@dottedmag.net>
	<1259788526-14205-1-git-send-email-dottedmag@dottedmag.net>
	<87zl5zfty5.fsf@yoom.home.cworth.org>
	<87k4x29732.wl%bremner@pivot.cs.unb.ca>
	<87bpiefwdq.fsf@yoom.home.cworth.org>
	<87aaxysjdj.fsf@vertex.dottedmag>
Organization: Ironic Design, Inc.
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
	boundary="Sig_/KnwYnfAo71flcZJVFL+=Wcd";
	protocol="application/pgp-signature"
Subject: Re: [notmuch] [PATCH (rebased)] Handle message renames in mail spool
Precedence: list

--Sig_/KnwYnfAo71flcZJVFL+=Wcd
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

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.

--Sig_/KnwYnfAo71flcZJVFL+=Wcd
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAksZWmQACgkQybLJkm2FpB6HNQCcDCeVTmLuAR1kR6UuqgppmNfj
GLwAn0QX7Xt+Pnr8x+0XVBaIUCOxx1cK
=UYPM
-----END PGP SIGNATURE-----

--Sig_/KnwYnfAo71flcZJVFL+=Wcd--