[SOLVED] Delivery delayed - MX points to 4 A Records

Raise/discuss any potential issues with MailEnable for consideration in project issue register.
Post Reply
kbuchl
Posts: 4
Joined: Sun Sep 30, 2012 5:14 pm
Location: Vienna, Austria

[SOLVED] Delivery delayed - MX points to 4 A Records

Post by kbuchl » Sun Sep 30, 2012 5:49 pm

Hello,

I face the following situation, where an outbound message delivery is delayed though 3 other IP adresses exist for the MX record.

the DNS records look like this

sample.com MX preference = 10, mail exchanger = smtp.sample.com
smtp.sample.com internet address = 198.77.155.1
smtp.sample.com internet address = 198.77.155.2
smtp.sample.com internet address = 198.77.155.3
smtp.sample.com internet address = 198.77.155.4

Now the host with the internet address = 198.77.155.1 is down and does not accept connections.
The other hosts are reachable and a connection on port 25 is possible having the server respond with "220 smtp.sample.com ESMTP postfix" waiting for commands.

When Mailenable is trying to connect to smtp.sample.com it is picking exactly the ip address of the host node which is down, and does not try the other ip addresses for delivery but does send a message delivery delay notification.

Is it possible to change the configuration of Mailenable to have the mail delivered to one of the other A Records?
Or does this need a change in the way how Mailenable is working?

Regards,
Klaus-Dieter

MailEnable-Ian
Site Admin
Posts: 9028
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: Delivery delayed though MX points to host with 4 A recor

Post by MailEnable-Ian » Mon Oct 01, 2012 3:44 am

Hi,

Thanks for pointing this out. It has been addressed for the next release. I do not have specific date of release at this stage.
Regards,

Ian Margarone
MailEnable Support

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Re: Delivery delayed though MX points to host with 4 A recor

Post by MailEnable » Thu Nov 29, 2012 12:05 am

This issue has been resolved in current releases
Regards, Andrew

Post Reply