5.0.13 breaks external IMAP SSL account

[Mike Scholes]

The upgrade from 5.0.10 seemed to go OK but my external account is broken, Even if I delete and recreate the account when I click Test I get the following error;

Error: d2:CN21:mail.theraileng.co.uk1:O35:The Railway Engineering Company Ltd2:OU35:The Railway Engineering Company Ltd6:accept4:true5:alias38:mail.theraileng.co.uk:C D1FEDC255CFE8094:fromi1178723472000e4:host21:mail. theraileng.co.uk3:icn21:mail.theraileng.co.uk2:io3 5:The Railway Engineering Company Ltd3:iou35:The Railway Engineering Company Ltd3:md532:41D35AB432CCC8AF39FFD8C20FE597E78:misma tch5:false1:s16:CD1FEDC255CFE8094:sha140:788C8DCAC E5789376F1D895DA23450CF3FC531A72:toi1494083472000e e

The external account runs Dovecot IMAP server and has been running fine until the upgrade.

[dweate]

I'm seeing the same thing since I upgraded to 5.0.13 under similar circumstances (external server is running Dovecot).

Has anyone else seen this? Any ideas on a solution?

Thanks.

[mmorse]

zmlocalconfig -e data_source_trust_self_signed_certs = true

(Or import into the keystore if it's a one time thing.)

Bug 35441 - external data sources with self-signed/expired certs no longer work requesting a bypass prompt / data_source_trust_self_signed_certs_override_ allowed attribute (or we could re-use ssl_allow_accept_untrusted_certs) was closed as wontfix (I tried - your welcome to comment / vote for it) in favor of Bug 35892 - clean up error dialog for external data sources (just cleanup to fit / making that a better error message such as: "Self-signed or mismatched certs are currently not allowed - please contact your admin for further options").

[dweate]

That did the trick.

Thanks, Mike.

[Mike Scholes]

Didn't fix it here...

"Error: argument 'data_source_trust_self_signed_certs' not in key=value form"

[Mike Scholes]

It's OK just removed the spaces either side of the "=" and restarted, load remote email now.