On 2008-02-14 10:22:32 -0500, Chris Lewis wrote: > Using FQDN in, say, "helo" isn't an unfortunate linux novelty, it's a > requirement by RFC821/2821. > > The point here really is that I'm trying to build code that is portable, > and possibly quite widely deployed. Futzing around with what hostname > returns on a given OS instance simply isn't an option. The real issue > here is that $self->qp->config(me) is ignoring the config/me file, and > appears to be unconditionally taking hostname. This will mostly be > unnoticable on Linux, where hostname does return the FQDN.
On Linux it depends on the Distribution. Debian defaults to nodename only, Redhat/Fedora defaults to the FQDN. > BTW: On solaris, the only argument hostname takes is if you want to > _set_ the hostname. "hostname -f" sets the hostname to "-f". So, don't > try that on Solaris at home folks ;-) Heh. I thought so, but since it's been 7 or 8 years since I last used Solaris, so I wasn't sure. It's certainly the case on HP-UX: % /bin/hostname -f You must be superuser to set the hostname (And yes, I've had hosts called "-f" or "-s" every now and then because I ran some script I developed on Linux on Solaris or HP-UX as root without checking ...). > I'm not asking how to fudge Solaris config to return the FQDN, or how to > write a function that can return a FQDN (I can figure that out from > /etc/hosts), but how to get qpsmtpd to return the value I'd expect from > config(me). I'm quite sure that used to work (I did override the local hostname with config/me on some hosts). I'll have a look at it. As a workaround you could have a look at my config_me_localaddr plugin, which derives "me" from the local IP address of the SMTP connection. hp -- _ | Peter J. Holzer | It took a genius to create [TeX], |_|_) | Sysadmin WSR | and it takes a genius to maintain it. | | | [EMAIL PROTECTED] | That's not engineering, that's art. __/ | http://www.hjp.at/ | -- David Kastrup in comp.text.tex
signature.asc
Description: Digital signature