Your message dated Mon, 17 Dec 2012 21:09:41 +0100 (CET)
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #676268,
regarding fetchmail socket error after receiving SMTP 553 code
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
676268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676268
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fetchmail
Version: 6.3.21
A remote POP3 server has some emails we want to fetch with bad FROM
addresses, it would appear. This causes fetchamil to quit that fetch and
the mail piles up in that POP3 box and end users think they are not
getting any email. On each subsequent fetchmail run it tries to get the
same bogus message and dies at the same place. It never gets past it.
fetchmail: SMTP> MAIL FROM:<DE@@email.bigpublications.ca> BODY=8BITMIME
SIZE=15587
fetchmail: SMTP< 553 5.1.3 <DE@@email.bigpublications.ca>... Invalid route
address
fetchmail: SMTP> RSET
fetchmail: SMTP< 250 2.0.0 Reset state
........fetchmail: socket error while fetching from [email protected]
At the MAIL FROM stage, the fetchmail source appears to ignore any
antispam directives (like "antispam 553"). Errors at this stage are not
handled well.
Fetchmail should look at the antispam codes at this stage also, and react
accordingly. In this case I would want it to drop this email and keep
going with the fetch. Alternatively, fetchmail could look at the FROM and
fix it, though that may be a bad idea for many reasons.
The config line in question looks like:
poll remote.hide.me with proto POP3 auth password
user 'bob' there with password 'pw' is 'bob' here options
fetchall stripcr mimedecode fetchlimit 15 antispam 553
Also tried with many variations for antispam, and fetchlimit 1 for
debugging/testing.
--- End Message ---
--- Begin Message ---
lack of useful information, probably no SW bug
--- End Message ---
