Madmuda1
asked on
Domino not looking for all mx records?
Does anyone know about this? It seems that my server is stopping at the first mx record and if mail fails to that address, it looks no further. Not sure what other info would help.
Can you tell more in detail what is happening, or what not? What's your network, incoming or outgoing mail, only the relevant elements? Thanks.
set notes.ini variable
debugrouter=3
(0=none, 1=Little information, 2=more information, 3=verbose )
and log_mailrouting=40
and get more informartion on the issue.
Are you sure that first MX is not responding and completely unavailable? If host listed as first MX record is responding - i.e. you can open connection but then it timesout - then there is no reason for Domino to go to the next MX
debugrouter=3
(0=none, 1=Little information, 2=more information, 3=verbose )
and log_mailrouting=40
and get more informartion on the issue.
Are you sure that first MX is not responding and completely unavailable? If host listed as first MX record is responding - i.e. you can open connection but then it timesout - then there is no reason for Domino to go to the next MX
ASKER
SysExpert: Not able to update it yet. Considering moving to 7 soon.
sjef_bosman: This is outbound mail. Most mail is going out, just not going to a couple of domains. (One of them is AOL, but I have a feeling that they are blocking us or the reverse lookups aren't functioning correctly) The one that I am most concerned with is having to route all of their traffic to an mx record that has a lower priority, because the main mail server is down.
fgrushevsky: I am able to connect on 25 to the first mx record, but shouldn't it look for the next if it can't send mail to that mx record? I will set the notes.ini settings and let you know.
All: I have had this problem in the past and was forced to create a record in the host file that went to the correct address. That is basically what I have done at this point as a work around for this issue, but I am unable to send to some Bellsouth.net addresses, and I don't want to keep doing the workaround.
sjef_bosman: This is outbound mail. Most mail is going out, just not going to a couple of domains. (One of them is AOL, but I have a feeling that they are blocking us or the reverse lookups aren't functioning correctly) The one that I am most concerned with is having to route all of their traffic to an mx record that has a lower priority, because the main mail server is down.
fgrushevsky: I am able to connect on 25 to the first mx record, but shouldn't it look for the next if it can't send mail to that mx record? I will set the notes.ini settings and let you know.
All: I have had this problem in the past and was forced to create a record in the host file that went to the correct address. That is basically what I have done at this point as a work around for this issue, but I am unable to send to some Bellsouth.net addresses, and I don't want to keep doing the workaround.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help. The domino server was functioning properly, the problem ended up being that our new IP address was blacklisted on their incoming mail server, so it just wouldn't accept our traffic and wasn't reporting anything back to us. Because of this, our mail server didn't look any further because as you stated, it didn't have any reason to.
Have you tried to update to the latest 6.5x with service packs ?
anything on the IBM site ?
I hope this helps !