The 03.09.04 at 13:49, Carlos E. R. wrote:
I have tested the above locally. Now I will go online and see what happens
:-)
Well, there is another little snag: fetchmail reports to the originator:
Sep 4 13:53:25 nimrodel fetchmail[4785]: SMTP>. (EOM)
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 550 Error: Message content rejected
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP error: 550 Error: Message content rejected
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 220 nimrodel.valinor ESMTP Postfix
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP> HELO localhost
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 250 nimrodel.valinor
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP> MAIL FROM:
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 250 Ok
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP> RCPT TO:
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 250 Ok
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP> DATA
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 354 End data with <CR><LF>.<CR><LF>
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP: (bounce-message body)
Sep 4 13:53:26 nimrodel fetchmail[4785]: SMTP>. (EOM)
And it is indeed sent to the originator, and accepted by his server:
Sep 4 13:53:26 nimrodel postfix/qmgr[4170]: 8A73429F55: from=, size=1691, nrcpt=1 (queue activeSep 4 13:53:26 nimrodel fetchmail[4785]: SMTP< 250 Ok: queued as 8A73429F55
Notice that my from address is absolutely bogus, invented! Nice checking
by the receiver host ;-)
By the way, this means that "set no spambounce" in .fetchmailrc doesn't
work for this. Perhaps I could use "-nobounce", but it would affect all
bounces:
The --nobounce option suppresses the normal action of
bouncing errors back to the sender in an RFC1894-confor
mant error message. If nobounce is on, the message will
go to the postmaster instead.
Whose postmaster? Me, or the originator server?
--
Cheers,
Carlos Robinson