Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23944 - [courier-mta] IMAP over TLS totally unusable
Attached to Project:
Community Packages
Opened by Andrej Podzimek (andrej) - Tuesday, 26 April 2011, 11:35 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 April 2011, 20:13 GMT
Opened by Andrej Podzimek (andrej) - Tuesday, 26 April 2011, 11:35 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 27 April 2011, 20:13 GMT
|
DetailsDescription:
After upgrading Courier-MTA from 0.62 to 0.66, the IMAP TLS extension became unusable. Thunderbird says: ssl_error_rx_record_too_long KMail sometimes (randomly) connects to the IMAP server, but fails in roughly 99% of cases. (Yes, I made really many attempts.) The logs don't say anything useful, they just report lots of short connections: Apr 26 13:27:57 charon imapd: Connection, ip=[::ffff:***.***.***.***] Apr 26 13:28:06 charon imapd: Disconnected, ip=[::ffff:***.***.***.***], time=9 The situation is exactly the same --with-gnutls and --without-gnutls. Steps to reproduce: Try to connect to a Courier IMAP server through TLS. Perhaps this is an upstream bug, but I have no idea how to figure it out. |
This task depends upon
Closed by Eric Belanger (Snowman)
Wednesday, 27 April 2011, 20:13 GMT
Reason for closing: Not a bug
Additional comments about closing: Reason for request: Sorry, this was caused by: 1) A small change in the order of config file parsing used by Courier (which clobbered the path to the certificate file) 2) PEBKAC, I should have used Wireshark right away... A big fat piece of plain text error messages came in response to STARTTLS, which all mail clients hid from my sight.
Wednesday, 27 April 2011, 20:13 GMT
Reason for closing: Not a bug
Additional comments about closing: Reason for request: Sorry, this was caused by: 1) A small change in the order of config file parsing used by Courier (which clobbered the path to the certificate file) 2) PEBKAC, I should have used Wireshark right away... A big fat piece of plain text error messages came in response to STARTTLS, which all mail clients hid from my sight.