On 8/26/11 4:53 PM, lance raymond wrote:
Sorry for the previous, I don't wish to make things complicated, so
focusing on my in-house server. I have moved my application server to
use this server and I see mail is going out, to the main google,
yahoo, etc. but get one deferred on an .edu server. The error is
"host mail-mx1-prod-v.cc.nd.edu
<http://mail-mx1-prod-v.cc.nd.edu>[129.74.250.243] said: 451 4.1.8
Possibly forged hostname for myIP (in reply to RCPT TO command)
Now, the problem is simply that 'ourdomain.com <http://ourdomain.com>'
is hosted at google and we cant relay though him. Our application
sends mail from noem...@mydomain.com <mailto:noem...@mydomain.com>.
Now I guess there doing a comparison to the mx on mydomain.com
<http://mydomain.com> which points to google then where the mail came
from. So the easy question is am I correct? Next, can I setup my
inhouse postfix to send mail from mydomain.com <http://mydomain.com>
or will I have issues later (this could be just the 1st).
If not, I guess my other option is looking for all the places mail
get's sent and change the name to like noem...@sub.mydomain.com
<mailto:noem...@sub.mydomain.com> and then use that.
So now the question is easier, am I correct with #1 (if so I am
wondering how others that use google are getting around it).
Thanks
cc.nd.edu probably isn't comparing the domain in the email address to
the mx for the domain, as that frequently doesn't match. What they are
probably checking is the domain name your SMTP server is advertising
compared to the rDNS domain for its IP address.
There is no reason to change your email *addresses* to be "from" a
subdomain. What is important is that if your mail server says it name is
mailer.example.com, that a rDNS lookup of its IP should evaluate to
mailer.example,com, and it should be reachable at the IP that is gotten
from a DNS lookup mailer.example.com.
--
Richard Damon