I did the following test:
[CODE]C:>telnet mail2.****.com 25
220 mail2.mhere.biz ESMTP
MAIL FROM: <test@equ*****.com>
250 ok
RCPT TO: <erik@sky.com>
553 sorry, that domain isn’t allowed to be relayed thru this MTA (#5.7.1)
QUIT
221 mail2.m****here.biz
Connection to host lost.[/CODE]
The obscured domains are valid, and this exercise works on mail4. This fails on mail2 for every domain I’ve tested (about a dozen now), and all thise domains are hosted on Jodohost, and have “mail relay” enabled in the CP.
The problem came to light because a customer called and his e-mail was bouncing. I got a copy of the bounce, and the mail was being sent via mail2.
I don’t know why it was being sent via mail2, maybe mail4 was slow to respond and the other MTA decided to go for the secondary MX. But that shouldn’t matter. If mail2 is listed as a valid MX, it should accept the mail, correct?
If not, then publishing mail2 as a valid secondary is breaking the RFCs, isn’t it?
What should I do? Disable mail relay and apologise to the client?