Michael Epting wrote:
I haven't changed any configuration files and I don't see any new fetchmail bugs, but I'm having big problems the last few days. Sid, fetchmail, exim3 (I've been meaning to upgrade to exim4, but I'm not going to do that when my mail is already broken.) I'm seeing stuff like this in my fetchmail log: fetchmail: awakened at Thu Aug 14 21:50:22 2003 fetchmail: 3 messages for epting at popd.ix.netcom.com (57678 octets).fetchmail: reading message epting@popd.ix.netcom.com:1 of 3 (3274 octets) fetchmail: SMTP error: 501 <bounce-debian-user=@lists.debian.org>: malformed address: @[]> may not follow <bounce-debian-user=@lists.debian.org-fetchmail: not flushed fetchmail: client/server protocol error while fetching from popd.ix.netcom.com fetchmail: Query status=4 (PROTOCOL) fetchmail: sleeping at Thu Aug 14 21:50:28 2003 This results in my not getting any mail. Actually, until today the problem seemed to be spam-related, but as you can see, this problem message is on debian-user. I've been able to remove the logjam by using Mozilla mail and deleting messages from the server that have these "bad" headers. They seem to be in the Reply To: header. Am I the only one seeing this? Does anybody know how to tell fetchmail to fetch the "bad" messages anyway?
I am seeing it too[though it didn't actually create a logjam, other messages were still being fetched, just all the list mail wasn't cause it all had these bad headers] I now have a procmail recipe that is essentially:
:0fw | sed -e 's$lists.debian.org-@\[\]$lists.debian.org$g'which fixes the messages enough so that fetchmail doesn't barf, but that is of course a gross hack.
Attachment:
pgpPFSr8bPxQk.pgp
Description: PGP signature