🚀 go-pugleaf

In article <1992Apr12.162426.25161@fmsrl7.srl.ford.com>, moconnor@pms704.pms.ford.com (Mike O'Connor) writes:
> In article <1992Apr11.211356.1@ptavv.llnl.gov> oberman@ptavv.llnl.gov writes:
> 
> :with what the mailer accepts from the user. Any reasonable mailer should make a
> :reasonable attempt to use aliases and local names by converting them into
> :FQDNs. I've never seen one which wouldn't, although I know of one System V
> 
> Just for the record, VMS MAIL (with most TCP/IP implementations)
> experiences this problem.  You Cc: a local/user alias/symbol/logical
> and that never gets FQDNized.  It's quite annoying.

Sounds like a configuration problem, to me. It is specific to the mailer and
has nothing to do with the TCP/IP implementations. Of course, it's quite
possible that the mailer was included.

I am the postmaster on a VMS system and, while mail only passes FQDNs out the
door, it certainly accepts lots of other things, even things like
QUICKMAIL::SMITH, where QUICKMAIL is an IP MX entry. Of course I have to admit
that I'm running a proprietary commercial mail product. PMDF.

I suspect that a change in BIND in 4.8.3 may be behind this whole thing. In
earlier versions of BIND, the default behavior was to try to resolve an address
by appending the local domain to it. I believe that BIND now tries to resolve
the name exactly as it is received. If it's not a FQDN, the lookup fails.

The merits of this change have been heavily debated in BIND forums, but that is
probably the reason for the situation. My mailer trys to append the local
domain name to all queries which are not otherwise in a valid domain or locally
defined aliases or systems.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: oberman1@llnl.gov		(510) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.