[SoCoSA/discuss] exim TLS cert problem

[Sean]

First I want to thank everyone for your suggestions and ideas.

What I've determined to far is that the problems happens to BOTH
Windows and Linux clients (I verified this over the weekend), and that
exim is configured to hand out the correct cert (mail.domain.com) when
using TLS.

I confirmed that the connections are actually connecting using TLS,
and that if the user accepts the incorrect cert the transaction takes
place.

I used the openssl command to view the contents of the certs, so I
know I have the cert files are named correctly and that exim is
configured to use the correct file. I can find no reason why exim is
using the www cert instad of the mail cert. Does anyone have any
further thoughts? If not I'll take this to an exim forum.


Sean


On Fri, Aug 28, 2009 at 12:28 PM, Andrew<argonaut at gmx.co.uk> wrote:
> Kevan Benson wrote on Fri, 28 Aug 2009 09:39:26 -0700:
>
>> I know a lot of mail clients still support it (with less
>> trouble than some of the other standards), so I think it's
>> still fairly widely deployed, for user facing systems, at
>> least.
>
> Port 25 vs. 465 vs 587 in depth:
>
> http://www.nabble.com/port-587-td14854468.html
>
> Personally, I think it's kind of f***ed to step on the official
> port assignee's toes simply because of a few popular MUAs that
> can't get things right.
>
> A.
>
> _______________________________________________
> SoCoSA discuss mailing list
> discuss at socosa.org
> Your address: seanvanco at gmail.com
> http://socosa.org/mailman/listinfo/discuss
> http://socosa.org/mailman/options/discuss/seanvanco%40gmail.com
>