Trevor, thank you for taking the time to report a problem.
However, it is not helpful if bug reporters get carried away to guess what might have happened, and draw false conclusions. Facts: - fetchmail treats response codes the same no matter if they are returned in reponse to MAIL FROM, or RCPT TO. - antispam and 553-code special handling do apply to MAIL FROM - fetchmail's softbounce feature can cause messages to be left on the POP3 or IMAP server. Use --nosoftbounce to delete permanently undeliverable mail. - Trevor's log contains a "socket error". Chances are that the POP3 server or session crashed at that point, and got restarted for the next login. In order to make progress, please post a relevant transcript with sufficient verbosity, according to <http://www.fetchmail.info/fetchmail-FAQ.html#G3>, and leave it to the experts to interpret it. I currently believe that the POP3 server is faulty, and not fetchmail. Best regards, Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
