I finally followed up on some log messages saying that my Exim server
had rejected mail from fetchmail... and I discovered that the rejected
mail had an envelope To of the form:
<undisclosed-recipients:;@funknet.net>
That is, the original sender had used the RFC822 group address syntax
<undisclosed-recipients:;> to hide the addresses from the To header,
and fetchmail decided to add my mail server's domain to the end of
that.
I'm using Debian's fetchmail 5.9.11-7 package. I thought this problem
was fixed a LONG time ago:
----- Forwarded message from "Eric S. Raymond"
<esr(_at_)snark(_dot_)thyrsus(_dot_)com> -----
Date: Tue, 27 May 1997 22:49:05 -0400 (EDT)
From: "Eric S. Raymond" <esr(_at_)snark(_dot_)thyrsus(_dot_)com>
Subject: Re: RFC822 group address
To: rfunk(_at_)peri(_dot_)acs(_dot_)ohio-state(_dot_)edu (Rob Funk)
Cc: fetchmail-friends(_at_)ccil(_dot_)org
One more thing....
The rewrite (er, reply_hack) routine doesn't recognize group addresses
of the form "listname:;" or (more explicitly)
"listname: user(_at_)here(_dot_)org, Big Bill <bill(_at_)evil(_dot_)com>;".
See sections 6.1, 6.2.6, and A.1.5 of RFC822.
I'm on a mailing list that goes out with a To: line of
To: shws:;
When I have rewrite on, I end up with
To: shws:;@peri.acs.ohio-state.edu
which doesn't make sense according to rfc822. This is the only
remaining reason I turn off rewrite.
I've never seen a live example of the explicit version; that would be
harder to rewrite. The short version should be relatively easy to
recognize though.
No problem. I've already put in guard code that will prevent rewriting
in this case. It will be in 3.9.6.
--
<a href="http://www.ccil.org/~esr";>Eric S. Raymond</a>
----- End forwarded message -----
Back to putting "no rewrite" in my fetchmail defaults....
--
==============================| "A slice of life isn't the whole cake
Rob Funk <rfunk(_at_)funknet(_dot_)net> | One tooth will never make a full
grin"
http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"