On Fri, 20 Sep 2013, James Harper <james.harper@bendigoit.com.au> wrote:
Is it doing sender address validation in any way, eg is the address represented by "logcheck@server1.example.com" a valid address, and/or is server1 making that verification correctly?
There is sender address validation, and it is a little complex. But it's not the issue in this case as both email addresses will work when sending mail from server0 and neither works when sending from server1. Thanks for the suggestion, I'm really stuck here. Below is an example of the swaks output from server1. The exact same data when sent from server0 gives a 250 ok response from mx0. I used sed to change the domain to example.com, but apart from that it's all a copy. While there are some other differences between server0 and server1 (Squeeze vs Wheezy) I don't think that they apply as I've verified all the text on "->" lines from Swaks and it's the same. As an aside for those who don't know of it Swaks is an excellent SMTP test tool, everyone who runs a mail server should know how to use it and have it installed in case of problems. <- 220 mx0.example.com ESMTP Postfix (Debian/GNU) -> EHLO example.com <- 250-mx0.example.com <- 250-PIPELINING <- 250-SIZE 51200000 <- 250-VRFY <- 250-ETRN <- 250-STARTTLS <- 250-ENHANCEDSTATUSCODES <- 250-8BITMIME <- 250 DSN -> MAIL FROM:<logcheck@server0.example.com> <- 250 2.1.0 Ok -> RCPT TO:<etbe@example.com> <** 554 5.7.1 <logcheck@server0.example.com>: Sender address rejected: forged mail -> QUIT -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/