Noel Jones wrote: > Bob Proulx wrote: > > But this confuses me. It appears to me that the message was rejected > > at SMTP time with a 554 code. Therefore shouldn't that generate a > > bounce message immediately? Why is dsn=4.7.1 being logged there? > > The remote server greeted postfix with a 554 code. By default, postfix > defers mail when the remote server does this. If you would rather have > postfix immediately bounce the mail, see: > http://www.postfix.org/postconf.5.html#smtp_skip_5xx_greeting
"By default, the Postfix SMTP client moves on the next mail exchanger. Specify "smtp_skip_5xx_greeting = no" if Postfix should bounce the mail immediately. Caution: the latter behavior appears to contradict RFC 2821." Hmm... I read through RFC 2821 and it isn't clear to me why 554 Transaction Failed needs to be interpreted as a temporary failure needing a retry. I am sure there is some historical experience of servers using 554 for temporary conditions for which I am missing that makes that behavior the correct default behavior. I thought all of the 5xx codes were non-temporary and should be treated as hard errors. But regardless that is exactly the answer I needed! I am going to set that for my friend's system as I think that is the best setting. > As for why it's being rejected, you'll need to contact the relay postmaster. > Looks like the IP has been "manually blacklisted," so one would presume it > will need to be manually whitelisted. Right. But I have no dillusions about that happening with hostedemail.com which does not seem to be responsive. And actually I would not be surprised if the recipient simply decided to report the messages as spam as a lazy way of saying don't type at me anymore. Thank you for the information! It got me unstuck. :-) Bob
