>
> > We're running Active Directory on Windows 2003 Servers. 99% of the
> > time, all is well. Occassionally we seem to be pulling erroneous MX
> > information. When I do an nslookup type=MX from the Imail server, I get
> > the correct information... most of the time. The erroneous server is
> > always another server that's located at the provider for the company in
> > question. I check their DNS server and can find no problems...
> >
> > I even had one where we'd apparently come up with the IP of an
> > internal POP server for earthlink, instead of one of their outward
facing
> > MX servers....
>
> Given what you describe, it sounds like IMail is getting the A record
> rather than the MX record. However, if this is the case, the "nslookup
> type=MX" should always produce the correct results. Specifically, if the
> MX record doesn't exist, IMail tries the A record (per the RFCs).
>
> Note that if you have more than one DNS server listed in the IMail SMTP
> settings, you should remove all but one. Otherwise, if the primary DNS
> server is failing, when IMail sees the failure for the MX record, it could
> cause IMail to switch to the secondary -- which will report the correct A
> record (which is not what you want).
>
-Scott
The weird thing is... When we receive the wrong MX record it's always an
IP address for another mail server that's supplied by that ISP. Just not
the correct one. The IP address is never the A record for the domain. The
error is usually that the mailbox couldn't be found on that server.
In every case, where we've had this isssue, our customer's mail server
is supplied by an ISP and never an in-house box.
Thanx for the response, Scott...
-Gil
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
