Nuno Paquete wrote:
> I don't touch on postfix configuration for a while, but I think you
> should only use IP addresses between [ ], like:
> > relayhost = [192.168.1.25]
> When you are using dns names you should avoid [ ], like:
> > relayhost = mail

It is okay to use names there.  Here is a pointer to the postfix
documentation for relayhost.

  http://www.postfix.org/postconf.5.html#relayhost

  On an intranet, specify the organizational domain name. If your
  internal DNS uses no MX records, specify the name of the intranet
  gateway host instead.

  In the case of SMTP, specify a domain name, hostname, hostname:port,
  [hostname]:port, [hostaddress] or [hostaddress]:port. The form
  [hostname] turns off MX lookups.

  Examples:
  relayhost = $mydomain
  relayhost = [gateway.example.com]
  relayhost = uucphost
  relayhost = [an.ip.add.ress]

Two of the examples specifically list hostnames in brackets to turn
off MX record lookups.

The real question is whether domain search is supported or not.
Previously simple host names without a domain part were allowed there.
The documentation in that section doesn't say as to whether this is or
is not allowed.  It might say elsewhere as a more general statement
however.  Frankly I wasn't sure where to look and didn't find it after
a search.

I am okay if short host names are no longer supported there.  But this
is the type of subtle change that can slip in unexpectedly.  If it is
intentional then having been found it would be good to add a NEWS
entry and I would be happy to write a NEWS entry addition suggestion.
But I am still thinking this is an unintentional and undesired change
and so holding out.  :-)

> And you must be sure that "mail" is correctly resolved. It's better
> to use complete dns name, like mail.mydomain.local

Yes "mail" is correctly resolved as I showed in my message with the
following information:

> >  $ host -t a mail
> >  mail.proulx.com has address 192.168.9.3

As you can see it was found successfully and resolved to an IP
address.

Thank you for looking at this issue.

Bob



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to