• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 724
  • Last Modified:

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.
1 Solution
1) Are you sure that all the MX records are accurate and working ?

Have you tried to update to the latest 6.5x with service packs ?

anything on the IBM site ?

I hope this helps !
Sjef BosmanGroupware ConsultantCommented:
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
(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
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Madmuda1Author Commented:
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.
If Domino (or any other mail server for that matter) can connect on port 25 to the first MX record, there is no reason to go to the lower priority MX records... unless sending server receives 4xx error during smtp session from receiving server... but even in the situation where sending server receives 4xx error the sending server can connect again to primary mx
Madmuda1Author Commented:
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.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now