On Tuesday 29 October 2002 23:31, Peter Kleiweg wrote:
I get these warnings by fetchmail:
reading message 1 of 2 (3113 octets) .fetchmail: SMTP error: 553 5.1.8 <jimc@xena.cft.ca.us>... Domain of sender address jimc@xena.cft.ca.us does not exist fetchmail: mail from FETCHMAIL-DAEMON@kleigh.nl bounced to jimc@xena.cft.ca.us
I know, that "bug" has been around for years, at least since suse 6.4. In fact, it is documented: 553 (invalid sending domain) Delete the message from the server. Send bounce-mail to the origina tor. Fetchmail fetches from your account, and forwards to sendmail for local delivery. This checks the domain of the poster, and rejects the mail if it doesn't exist. The recomended action is a "temporary failure", as they told you here; but that does not make sense when fetching from a pop/imap account, as it will remain there for ever. It makes sense on a server, because the sender will eventually give up or correct the address. You could disable that feature in sendmail, somehow. Otherwise, try to add this line: set no spambounce to your ".fetchmailrc" file. It doesn't always work, though; i'm not sure why. Perhaps that only affects mails rejected with a 550 or 571 code or similar. Perhaps you could try: set no bouncemail Direct error mail to postmaster rather than sender But it won't work much better, either, if it emails the sender's postmaster, who of course does not exist :-(
What is the point of bouncing a message to a domain you know does not exist? These warnings always result in two error-messages in my inbox about mail that could not be delivered. Undoubtedly some security feature, but is there a way to switch it of? It is quite annoying.
Absolutely! -- Cheers, Carlos Robinson