Zitat von Ben McGinnes <b...@adversary.org>:
On 5/11/10 4:31 PM, mouss wrote:hmmm. here: $ host 74.125.45.27 27.45.125.74.in-addr.arpa domain name pointer yx-in-f27.1e100.net. $ host gmail-smtp-in.l.google.com gmail-smtp-in.l.google.com has address 209.85.227.27 74.125.45.27 is a google IP, but I don't see it listed as the IP of one of the MX's.Whereas I have: bash-3.2$ host 74.125.45.27 27.45.125.74.in-addr.arpa domain name pointer yx-in-f27.1e100.net. bash-3.2$ host gmail-smtp-in.l.google.com gmail-smtp-in.l.google.com has address 74.125.155.27 bash-3.2$ This is because Google use geolocation IPs. For specific hosts you will obtain the IP that appears to be "closest" to your network.
It looks like gmail-smtp-in.l.google.com is in fact different dependant from where you are looking at it. It is the MX with highest priority, but as said even from my side of the planet the IP listed at the OPs message is a valid MX for gmail.com so it should not reply "relay denied". On the other hand i have seen MXs replying with "relay denied" when they in fact mean "user does not exist".
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
