Subject: Re: bin/12876: NetBSD's INET6 patches to Postfix break non-INET6 features!
To: None <firstname.lastname@example.org, netbsd-bugs@NetBSD.ORG>
From: Greg A. Woods <email@example.com>
Date: 05/08/2001 23:41:14
[ On Tuesday, May 8, 2001 at 20:37:28 (-0700), Jason R Thorpe wrote: ]
> Subject: Re: bin/12876: NetBSD's INET6 patches to Postfix break non-INET6 features!
> Indeed -- I have almost never tied NIS domain to DNS domain. In many
> environments I've worked in, a single DNS domain or sub-domain might
> have had 3 or 4 NIS domains.
Some do, some don't. I've personally never seen an environment where it
wasn't the same, or at least related, but hen I've only seen a few NIS
Note too that in private environments I've seen where NIS is used the
internal mail routing uses the NIS domain anyway, and since Postfix uses
just gethostbyname()/gethostbyaddr() (or getnameinfo()/getaddrinfo())
it'll use NIS for hostnames too.
In other words my fix to default $mydomain to domainname(2) is in fact
correct for *all* environments I've ever seen personally, with or
In any case it simply cannot lose. Either it will make the default
right and thus make Postfix work transparently without any local
configuration changes, or it will leave it as wrong (not empty, but
still wrong) and the admin will still be required to manually set
$myname and $mydomain.
Greg A. Woods
+1 416 218-0098 VE3TCP <firstname.lastname@example.org> <email@example.com>
Planix, Inc. <firstname.lastname@example.org>; Secrets of the Weird <email@example.com>