After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 677102 - Backends try to connect to port 143 even if SSL encryption is configured
Backends try to connect to port 143 even if SSL encryption is configured
Status: RESOLVED FIXED
Product: evolution-kolab
Classification: Other
Component: configuration
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Christian Hilberg
Evolution Kolab maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-05-30 14:49 UTC by Christian Hilberg
Modified: 2012-06-04 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Hilberg 2012-05-30 14:49:23 UTC 
Got this via evolution-kolab-devel-list:

---8<---
I have troubles with configuring Addressbook/Calendar/Notes using SSL.  
Even if I set "Encryption method" to "SSL encryption" the client tries  
to connect to port 143 and obviously gives an error: "Could not  
connect to my.host.name: TCP connection reset by peer". Though SSL  
works fine if I use "Kolab" account for email instead of IMAP/IMAP+.  
I'd appreciate if somebody would point me to the right direction or  
give any tips.
---8<---
Comment 1 Christian Hilberg 2012-05-30 14:51:16 UTC 
Confirmed.

The backends try to connect to port 143, where they should try port 993 when configured for SSL encryption.
Comment 2 Christian Hilberg 2012-06-04 15:14:44 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. The fix will also be available in the next major software release.

Please note that for the 3.4 line, it is not possible to specify a port number for the PIM backends to use. Only the default ports are being used. This issue will be resolved in the next major software release (a config option for port numbers will be provided).