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 498302 - Evolution does not sync IMAP when GNOME is being shutdown
Evolution does not sync IMAP when GNOME is being shutdown
Status: RESOLVED DUPLICATE of bug 219197
Product: evolution
Classification: Applications
Component: Mailer
2.12.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on: 219197
Blocks:
 
 
Reported: 2007-11-19 20:11 UTC by Martin Jürgens
Modified: 2011-10-13 08:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Martin Jürgens 2007-11-19 20:11:52 UTC 
Please describe the problem:
For Evolution to sync the things that have been done locally with the IMAP server, you have to close it cleanly.

When shutting down or logging out, you are not closing Evolution cleanly and thus, the changes you have done to your mailbox are not on the IMAP server which is bad.

Steps to reproduce:
1. Delete mails in your IMAP mailbox 
2. Do not close Evo, shut down GNOME instead


Actual results:
When you open Evolution again, the deleted message is still there.

Expected results:
The message should be really deleted.

Does this happen every time?
Yes

Other information:
Comment 1 Akhil Laddha 2011-10-13 06:37:44 UTC 
Milan, can we close this bug in favor of bug 219197 ?
Comment 2 Milan Crha 2011-10-13 08:22:32 UTC 
Yup, I suppose so. There were slightly more changes around, but 3.0.3 or 3.2.0 should work as expected.
Comment 3 Akhil Laddha 2011-10-13 08:26:09 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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