MX priorities not working within server environment

[evydaemon]

Simple as that:

We have a domain.com with 2 mx records:
mail.domain.com 10 (A-Record: clients mail server)
mx2.domain.com 20 (A-Record: this server)

When sending emails to an existing email address in domain.com from an email address that is hosted on the same server, these emails won't reach mail.domain.com as it should corresponding to the priority=10. The server with this priority is of course reachable and would accept mails.
Instead emails are sent to mx2.domain.com. (That works..)

I'm using postfix.

 

[BMcKinney]

Perhaps the server realizes it's sending the mail to itself and does so... making it unnecessary to even perform a DNS lookup to resolve an MX? Or so I'm guessing...

 

[Alex van Os]

Same here...

Previously it worked fine, now i have the same problem... Some of my clients use 'Google Apps for your domain', so the mailbox is on the Google Network...

It was never a problem before, untill a few days ago..

Now when a CMS or some other program uses sendmail, it can't send anything because the local mailbox doesn't exist and the server doesn't resolve the MX-records that are stated in the DNS...

Can anyone offer a good piece of advice?


Regards,



Alex van Os

 

[evydaemon]

This is growing to a major issue here!
I urge all admins to get this fixed soon. Is there any work around?

 

[elger]

Try to find out if you can find the proper MX:
in the shell do this:
dig @localhost myremodemaildomain.com
and also:
dig @127.0.0.1 myremodemaildomain.com

If both resolve the remote mail record correctly, try to send an email by hand. Use a search engine to fine something on "telnet test SMTP"

Google got me this site:
http://arnab.org/notes/using-telnet-to-send-mail-by-smtp

now you know where your problem is, if these two tests work, php is not allowed/able to send remote mail. Else you have either DNS or firewall problems.

Some ISP's do not allow you to send to SMTP ports other then their own smtp-servers ports