GNOME Bugzilla – Bug 266912
if IMAP server SSL cert is renewed, almost impossible to debug.
Last modified: 2012-09-06 10:39:45 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.6.1 1.4 Gnome-Distributor: Debian Synopsis: if IMAP server SSL cert is renewed, almost impossible to debug. Bugzilla-Product: Evolution Bugzilla-Component: UI Bugzilla-Version: 1.4 Bugzilla-Keyword: doc Description: The SSL cert on my IMAP server was updated (it was about to expire). The error messages issued by Evolution in this case were not terribly clear about what was wrong; if I hadn't known where to look for the problem via other mechanisms (i.e. tools that will tell me what certs they have), I wouldn't have know what caused the problem. Worse yet, the only way to fix this problem, even after I knew what was wrong, was FAR from obvious to even a reasonably informed user. After digging through the Evolution dialogues at length, the only solution I found was the following not-at-all-obvious technique: Tools --> Settings --> Mail Accounts * select IMAP account and click on "Edit" * select "Receiving Mail" tab; click on "Check for supported types" button. When prompted, accept the new cert. Either this should be clearly documented, or it should be more obvious to the naive user. Unknown reporter: nocturne@mit.edu, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
retargetting from very ancient 2.1 milestones to just ancient 2.3 milestones. it just sucks to click several target milestone values. sorry for the noise.
in order to destroy the UI component (as discussed with jpr, dobey, and nags), changing component and reassigning. adding usability keyword. developers, please reassign appropriately if necessary. punting milestone.
I wonder how to get a testcase for this.
Sort-of test case is in bug #606181, and with 3.6.0, if the server certificate changes, user is asked to accept the new certificate, thus I consider this fixed. Please reopen if you face the issue in 3.6.0+.
*** Bug 680205 has been marked as a duplicate of this bug. ***