On Tue, 19 Sep 2000, Don Hayward wrote:
> exim -v -bt user1@wmmc_po.ah.org
> user1@wmmc_po.ah.org
> deliver to user1@wmmc_po.ah.org
> router = lookuphost, transport = remote_smtp
> host mail1.ah.org [209.79.214.233] MX=1
> host smtp-relay.pbi.net [206.13.28.30] MX=100
> host smtp-relay.pbi.net [206.13.28.8] MX=100
>
> The configure file contains: dns_check_names = false
That allows Exim to do DNS lookups on syntactially invalid host names.
However, sending mail to another host involves the use of SMTP. This is
defined by RFC 821, which explicitly allows only letters, digits,
hyphens, and dots in domain names. So as soon as you try to actually
deliver to such a domain, there is a high chance that one of several
bits of software that is involved in the SMTP transfer at either the
sender or recipient end, will object.
As somebody else pointed out, there seems to be a wildcard MX involved.
If you try wmmc-po.ah.org instead (underscore replaced by hyphen), the
DNS lookups work just the same.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
