[Mailman-Users] Re: Poster not receiving his own posts
acc at anthonychavez.org
Mon Dec 13 21:27:54 CET 2004
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, 13 Dec 2004 12:09:45 -0800 "John W. Baxter" <jwblist at olympus.net> wrote:
> On 12/13/2004 10:54, "Anthony Chavez" <acc at anthonychavez.org> wrote:
>> 3. He includes a Cc: header with no value in every post. This seems
>> like it *could* be interfering, but why would it?
> Well, it *could* be confusing the NoDups code (if that code contains a bug).
Actually, after some fiddling, I see that the bit that affects delivery
back to the poster is the "not metoo" bit. You can confirm this by
using the administrative Web interface (Membership Management) and
toggling the "Receive your own posts to the list?" bit in your personal
> I'm not good enough at reading RFC 2822 to know whether a blank Cc: header
> is legal or not (after spending only a few minutes, I lean toward not
> legal), but either way having such a header mess up NoDups processing would
> be a Mailman bug.
I am inclined to agree with you (except that as stated above, I think
that the bit in question is "not metoo").
> A test here with Mailman 2.1.2 seems to say that a blank Cc: header doesn't
> bother the NoDups processing in that version. (Where "blank" means either
> just a space after Cc: or nothing after Cc:) (Test run using telnet to the
> mail server by hand.)
This particular use is posting with a blank space after Cc:.
I'm running 2.1.5, BTW. FWIW, htdig 3.2.0b6 is installed but not
configured nor running. Same goes for AMaViS 2.2.0, ClamAV 0.75, and
SpamAssassin 2.64, none of which are being piped any messages, AFAICT.
All on FreeBSD 5.3-RELEASE-p2.
Anthony Chavez http://anthonychavez.org/
mailto:acc at anthonychavez.org jabber:acc at jabber.anthonychavez.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (Darwin)
-----END PGP SIGNATURE-----
More information about the Mailman-Users