>Ioannis, disable all the firewalls but for basic SPI NAT/PAT (if you're using >NAT) on the dedicated Shorewall guest. Route TCP 25 inbound via a PAT rule to >the Postfix guest. See if that eliminates the timeout and related TCP errors. >-- >Stan
Dear Stan, I was just about to get enthusiastic about the result of your suggestions... Indeed by moving postfix from dmz to local, eliminated 98% of my problems, still two mail servers are having the following errors: (lost connection with mx1.mail.eu.yahoo.com[77.238.177.9] while sending end of data -- message may be sent more than once) (lost connection with mx2.mail.eu.yahoo.com[77.238.184.241] while sending end of data -- message may be sent more than once) (host some.domain.gr[62.1.1.1] said: 451 Requested action aborted: local error in processing (in reply to end of DATA command)) It seems to me that the tcp/ip related issues are eliminated. I know for sure that one of the mail servers is running exchange 2003, and the others, from what you can see, are yahoo mail servers. For now, the communication issues are just isolated on a yahoo and an exchange 2003 server, let's say that I could live with that (not that I can), but what if things do escalate and other mail servers join the queue. Thank you, and everyone else for your input so far. -- Ioannis __________ Information from ESET Smart Security, version of virus signature database 5165 (20100602) __________ The message was checked by ESET Smart Security. http://www.eset.com
