Author: Renaud Allard Date: To: Florian Weimer CC: exim-users Subject: Re: [exim] TLS interaction problem with Communigate Pro 4.1.6
Florian Weimer wrote: > Communigate Pro (at least in some versions) does not cope very well
> with TLS advertisements. If this server software tries to submit a
> message to one of our hosts (which advertises STARTTLS during EHLO),
> it aborts the delivery attempt during the TLS handshake. The nasty
> part: it immediately retries, at the same MX, leading to the same
> failure, probably until the message has expired from the queue.
>
> Is there some sort of configuration hack that could help to address
> this problem? I don't want to fall back to SSL 3.0 globally (hich
> would solve this particular problem), and sender-specific
> configuration is only a last resort.
sslv2 is deprecated (in 2006, all major browsers dropped support for
it). Most applications still understand them, but it is not recommended
for use anymore. So sticking with ssl3 still looks like the best and
easiest approach.
>
> The messages the remote hosts are trying to deliver aren't important,
> I guess. It's probably just backscatter.
> Then why bother that much?
