On 2014-12-03 17:52, Viktor Dukhovni wrote:
On Wed, Dec 03, 2014 at 04:55:47PM +0000, Viktor Dukhovni wrote:
On Wed, Dec 03, 2014 at 04:36:12PM +0000, James Bailey wrote:

> is it possible to use a non fully qualified host name as relayhost?

Not by default.  And it is generally not a good idea to change this.

However, if you replace the relayhost setting with:

    # Default empty value
    # relayhost =
    default_transport = nondns:[relayhost]

Oh, and if relay_domains is not empty, also:

    relay_transport = nondns:[relayhost]

Keep in mind that the default value of "relay_domains" is
"$mydestination", and that by default "parent_domain_matches_subdomains" includes "relay_domains". The upshot of which is that all sub-domains
of domains listed in $mydestination are implicitly relay_domains.

I generally recommend:

    # Empty, or otherwise explicit list of domains.
    #
    relay_domains =

    # Only access(5) maps use "dot-less" parent-domain matching
    #
    parent_domain_matches_subdomains = smtpd_access_maps

Many thanks Victor,


The problem is non trivial with the hosts named $host.hosts.example.com but the working CNAMES are smtp_relay.$dc.$env.$division.example.com normally I would manage main.cf with Puppet and an ENC, unfortunately the client a large financial software client doesn't yet use such tools and since it is also a PCI/DSS environment, such a tools is unlikely to be approved in the few months I am here. The files are deployed by Perl scripts, so I guess it time to roll back some of the changes I made there and add a few new ones

Regards Jim

Reply via email to