On Monday 27 July 2009 18:07:51 ghe wrote:
> On 7/27/09 1:45 PM, /dev/rob0 wrote:
> > [1] Strictly speaking, it's $smtp_helo_name which should resolve, but
> > the default value for smtp_helo_name is $myhostname, and I would
> > not generally recommend setting smtp_helo_name without good reason.
>
> My MTA is on the DMZ with an FQDN and IP on a 1918 network. That IP gets
> NAT'ed on its way out to one that resolves to a218.slsware.com. So I set
> the helo name to what is seen by the universe.
>
> Is that a good enough reason?
It's yours ... that's plenty reason to do what you like. :) However,
being that the NAT is probably bidirectional, if it was mine, I'd set
"myhostname = a218.slsware.com" and be done with it. I'd also have the
name a218.slsware.com resolve to the RFC 1918 IP address for internal
clients.
If you'll pardon an unrequested observation: some spam measurements
consider having any quad of the IP address in the hostname as a
possible sign of spamminess. I would give it a real name, unless
there's some sort of emotional attachment to "a218". :)
What I would consider "good reason" would be a special clone of the
smtp transport for some non-default interface on a multi-homed host.
And there, smtp_helo_name would go in master.cf, not main.cf.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
