Re: MX failure - going to A record
- From: per@xxxxxxxxxxxx (Per Hedeland)
- Date: Thu, 1 Jun 2006 22:37:22 +0000 (UTC)
In article <yeklkshc5il.fsf@xxxxxxxxxxxxxxxxx> Bruce Barnett
<spamhater113+U060601102641@xxxxxxxxxxxx> writes:
Bruce Barnett <spamhater113+U060601071205@xxxxxxxxxxxx> writes:
I have a broadband connection, and use it to connect to a second ISP
through a OpenVPN connection. I suspect it's a name server problem, but
I'm not sure how to track down this occasional error.
My ISP (a friend and network guru) suggests that I add
define(`confTRY_NULL_MX_LIST', `False')
Not useful - first of all False is the default anyway, second the
setting only comes into play if
a) some MX records are found, and
b) a local host name (class {w}) is found in the MX list, which per the
specs means that this entry and all of same or lower priority (higher
number) should be deleted, and
c) the list is empty after deletion per b).
That way I will never connect to an A record.
Not correct.
I'll try that. I hope I
don't have to deal with some domains that don't have MX records.
That will work anyway (of course, since False is the default).
--Per Hedeland
per@xxxxxxxxxxxx
.
- Follow-Ups:
- Re: MX failure - going to A record
- From: Robert Harker
- Re: MX failure - going to A record
- References:
- MX failure - going to A record
- From: Bruce Barnett
- Re: MX failure - going to A record
- From: Per Hedeland
- Re: MX failure - going to A record
- From: Bruce Barnett
- Re: MX failure - going to A record
- From: Bruce Barnett
- MX failure - going to A record
- Prev by Date: Re: Only allow connections from ip with rDNS details
- Next by Date: Re: Sendmail 8.13.6 on Solaris
- Previous by thread: Re: MX failure - going to A record
- Next by thread: Re: MX failure - going to A record
- Index(es):
Relevant Pages
|