Victor Duchovni wrote:
>
>>> The policy table lookup key does not match the destination nexthop, or
>>>
>
>
>
> That's exactly the problem.
>
>
> I think you should be able to figure this out, even without reading the
> below, but if you are in a hurry try the documentation:
>
> ht
On Wed, Feb 25, 2009 at 05:50:07PM -0800, J Sloan wrote:
> Victor Duchovni wrote:
> > On Wed, Feb 25, 2009 at 04:50:49PM -0800, J Sloan wrote:
> >
> >
> >> We have just started doing business with a firm that uses an ironport
> >> device, and discovered that postfix will not issue a STARTTLS to
Victor Duchovni wrote:
> On Wed, Feb 25, 2009 at 04:50:49PM -0800, J Sloan wrote:
>
>
>> We have just started doing business with a firm that uses an ironport
>> device, and discovered that postfix will not issue a STARTTLS to that
>> host, whether it's listed in tls_policy_maps with "may"
>> or
On Wed, Feb 25, 2009 at 04:50:49PM -0800, J Sloan wrote:
> We have just started doing business with a firm that uses an ironport
> device, and discovered that postfix will not issue a STARTTLS to that
> host, whether it's listed in tls_policy_maps with "may"
> or "encrypt protocols=TLSv1"
The pol
We're seeing an odd problem with postfix TLS only when talking to an
ironport device. We configured smtp_tls_security_level = none and used
smtp_tls_policy_maps to set per site tls policy, rather than doing tls
by default.
This had worked perfectly for over months and many thousands of smtp
sessio
