|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: tls_per_site
From: Victor Duchovni (Victor.Duchovni
MorganStanley.com)
Date: Fri Dec 02 2005 - 11:03:46 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Dec 02, 2005 at 12:21:16PM +0000, Laurence Moughan wrote:
> Hello All,
>
> i have
>
> smtp_tls_per_site = dbm:/etc/postfix/tls_per_site
> and
> transport_maps = dbm:/etc/postfix/transport
>
> with
>
> tls_per_site
>
> tu-cottbus.de MUST_NOPEERMATCH
> hertz.com MUST_NOPEERMATCH
>
The lookup keys for the tls_per_site table are the specific MX host
and if that is not found, the nexthop domain. If your transport
table overrides the nexthop domain, use the nexthop from the
transport table. For example.
transport:
example.com smtp:[tls.example.com]
tls_per_site:
tls.example.com MUST
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo
postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]