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 266912 - if IMAP server SSL cert is renewed, almost impossible to debug.
if IMAP server SSL cert is renewed, almost impossible to debug.
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 680205 (view as bug list)
Depends on:
Blocks: 327508 327510
 
 
Reported: 2004-09-27 16:57 UTC by nocturne
Modified: 2012-09-06 10:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nocturne 2004-09-27 16:57:37 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.

Comment 1 André Klapper 2005-09-25 01:43:42 UTC
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.
Comment 2 André Klapper 2005-11-08 14:47:47 UTC
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.
Comment 3 André Klapper 2012-06-16 21:18:31 UTC
I wonder how to get a testcase for this.
Comment 4 Milan Crha 2012-08-31 16:34:39 UTC
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+.
Comment 5 Milan Crha 2012-09-06 10:39:45 UTC
*** Bug 680205 has been marked as a duplicate of this bug. ***