Comment 5 for bug 671977
Revision history for this message
| Stuart Cianos (scianos-alphavida) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Ok... A strange solution, but seems to work as a temporarily workaround for at least one IMAP server here... Maybe this points to a problem with Evo's socket buffering or some type of timing/race condition???
On the configuration screen for the account with the original IMAP plugin, enable the "Command to connect to server" option. For the command, pipe Evolution's input and output to and from Netcat:
Command:
nc <server name or IP> 143
This has ONLY been tested with TLS auth on my infrastructure here, but has triaged the issue reliably on impacted systems.
+1 on a bug fix being issued, or 2.32 being made available in the backports repo (2.32 fixes this issue, among others).