We're using Postfix 2.1.5 on an old Debian 5 Linux system as an incoming, but not outgoing mail server. (We host several domains on our server and don't want the mail headers for outgoing mail from (say) CompanyA.com to say that they originated from a hostname that might be CompanyB.com, CompanyC.com, etc.
So, we point our mail clients to use our Time Warner SMTP server for outgoing mail, which is smtp-server.triad.rr.com . Now here's the problem: Mail from CompanyA.com sent to any address of any outside domain: DELIVERED Mail from any outside domain sent back to m...@companya.com: DELIVERED Mail from m...@companya.com to m...@companya.com: DISAPPEARS And by "disappears", I mean that it is accepted for delivery by smtp-server.triad.rr.com, but is never delivered back to our server, nor is any bounce message sent back to me. It is never heard from again. Time Warner has been useless in diagnosing the problem. I cannot make them understand that this USED to work just fine, for years, but has only started failing in the last month or so. They have no suggestions. The only other clue I have is that I've suddenly started seeing a lot of this in the mail log: Nov 4 17:18:49 www postfix/smtpd[10395]: warning: smtpd_peer_init: 107.14.166.226: hostname cdptpa-outbound-snat.email.rr.com verification failed: Name or service not known Nov 4 17:26:49 www postfix/smtpd[10418]: warning: smtpd_peer_init: 107.14.166.225: hostname cdptpa-outbound-snat.email.rr.com verification failed: Name or service not known Nov 4 17:34:14 www postfix/smtpd[10418]: warning: smtpd_peer_init: 107.14.166.226: hostname cdptpa-outbound-snat.email.rr.com verification failed: Name or service not known Nov 4 17:35:48 www postfix/smtpd[10453]: warning: smtpd_peer_init: 107.14.166.225: hostname cdptpa-outbound-snat.email.rr.com verification failed: Name or service not known etc. >From what I understand about the smtpd_peer_init message, that usually seems to indicate that a Bad Guy is trying to either relay or otherwise abuse my mailserver but that it was blocked. But perhaps in this case, is the error message telling me something about the problem I'm having? Does it point to some clue as to why the messages aren't be delivered back to us? Some misconfiguration on Time Warner's part? Or on my part? If more info from me is needed to resolve this, I'll be happy to provide what I can. Thanks to anyone who can help!
