On Wed, 21 Jan 1998, Jon Morby wrote:
>
> The output below is from exim -d9 -M message-id
>
> It reports mx_only set to false, but I can't find any documentation on
> mx_only.
It is an internal flag that gets set as a result of various options.
mx_only if TRUE, require MX record(s) to exist
Since it is reported as being FALSE, it means the lookup should proceed
to search for an A record, having failed on an MX record.
> Any ideas?
Try with -d10, in order to see the DNS resolver debugging output, but
actually I think there is no problem (with Exim):
Looking for that domain in the DNS gives neither an MX nor an A record.
So that is consistent: you told Exim to send the message to a particular
host, but that host doesn't exist. Exim says "Aarrgghh!! There's a mess
in the configuration."
-------- Nameserver sec1.dns.uk.psi.net --------
suffi.demon.co.uk has no MX record at sec1.dns.uk.psi.net (Authoritative answer)
-------- Nameserver ns0.demon.co.uk --------
suffi.demon.co.uk has no MX record at ns0.demon.co.uk (Authoritative answer)
-------- Nameserver ns1.demon.co.uk --------
suffi.demon.co.uk has no MX record at ns1.demon.co.uk (Authoritative answer)
-------- Nameserver ns0.demon.co.uk --------
suffi.demon.co.uk has no A record at ns0.demon.co.uk (Authoritative answer)
-------- Nameserver ns1.demon.co.uk --------
suffi.demon.co.uk has no A record at ns1.demon.co.uk (Authoritative answer)
-------- Nameserver sec1.dns.uk.psi.net --------
suffi.demon.co.uk has no A record at sec1.dns.uk.psi.net (Authoritative answer)
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
