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 383213 - Changing imap server encryption type requires unexpected restart
Changing imap server encryption type requires unexpected restart
Status: RESOLVED DUPLICATE of bug 207481
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 604463 671161 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-07 00:30 UTC by Jules
Modified: 2012-04-11 16:22 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Jules 2006-12-07 00:30:47 UTC
Please describe the problem:
When you edit the type of encryption used by an imap server in the accounts list, the change has no effect unless you restart evolution.  Nothing in the UI suggests this will be the case however, which causes much confusion to an unitiated user.

Steps to reproduce:
1. Add a new account, naming an IMAP server for which TLS does not work, but choosing TLS as the encryption.
2. Note that the connection does not work.
3. Change the encryption from TLS to either SSL or "No ecryption" (whichever will work for your server)
4. Note that the connection still does not work.
5. Restart evolution
6. The connection should now work


Actual results:
Connection does not work at step 4, but does at step 6.  No user interface appears that explains that this will happen.

Expected results:
Either the connection should work at step 4, or a dialog should appear to indicate that evolution must be restarted for the change to take effect.

Does this happen every time?
Yes

Other information:
I'm using the Windows port of Evolution.  Not sure if this is relevant.
Comment 1 Akhil Laddha 2011-06-15 06:43:44 UTC
*** Bug 604463 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2012-03-02 05:13:42 UTC
*** Bug 671161 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2012-03-02 05:15:07 UTC
last duplicate in 3.2.x
Comment 4 Sam Morris 2012-03-02 11:30:38 UTC
NB, I didn't change the encryption type but the authentication type. The connection was always configured using TLS. Of course, both behaviours may be caused by the same bug or not. :)
Comment 5 Milan Crha 2012-04-11 16:22:11 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 207481 ***