Bug#426013: exim4-daemon-heavy Base64 decoding error

[Simon Josefsson]

Mark Adams <mark at campbell-lange.net> writes:

>> 
>> Excellent, thank you.  Could you also cut'n'paste your current exim
>> (MAIN_TLS_*) configuration?
>> 
>> Which exim version are you using?  Still 4.63-17?  It would help if you
>> could post a short snippet of an updated error message, with the new
>> filenames and so on.
>> 
>> When do the problem actually happen?  Does it happen on all TLS
>> sessions, or just some?
>> 
>> /Simon
>
> All, This is now working as desired. I am using exactly the same
> configuration as I detailed in my first post (it was commented, I
> uncommented it.)
>
> MAIN_TLS_ENABLE = yes
> MAIN_TLS_PRIVATEKEY = /etc/exim4/certificates/newserver_co_uk.pem
> MAIN_TLS_CERTIFICATE = /etc/exim4/certificates/newserver_co_uk.crt
>
> Does anyone know if any recent updates could have corrected this
> problem?
>
> Regardless, I am very happy this is now working. Thanks to everyone that
> has looked in to this for me and provided help.

Great.  Thanks for discussing the problem.

I am not aware of any change in this area in a long time, but I may have
missed something that may not seem related.

For what it's worth, what is consistent with the error messages you got
was if you mixed up the private key filename and the certificate
filename in the configuration.  That's why I asked so many times about
filename consistency and double-checks.

/Simon