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 665056 - Deleted IMAP emails come back; won't go away unless they are deleted twice
Deleted IMAP emails come back; won't go away unless they are deleted twice
Status: RESOLVED DUPLICATE of bug 721286
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-11-28 15:15 UTC by Máirín Duffy
Modified: 2014-01-30 07:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Máirín Duffy 2011-11-28 15:15:02 UTC
Hi,

I'm running evolution-3.2.1-2.fc16.x86_64.

I've noticed since upgrading to Fedora 16 / GNOME 3.2 that when I delete a mail in Evolution, and browse to another folder, when I come back the deleted mail comes back. It doesn't have the cross-out mark as if it was deleted and hasn't been expunged... it really comes back. If I delete it a second time, then it goes away for good.

This is the case both for my corporate email account that I access via IMAP as well as my personal dreamhost.com-hosted accounts that I also access via IMAP.

If there's any additional information I can provide to try to pinpoint the problem please let me kjnow.
Comment 1 Ciaran Gultnieks 2011-12-12 19:09:40 UTC
I encountered the same problem running 2.32.2.

Following advice from prahal2 on IRC, I disabled offline syncing for all the affected accounts, and the problem went away, so that is a temporary workaround.

I see this happening with dovecot IMAP servers (with almost the standard supplied Debian config) and also with an Exchange server via IMAP.

I think it's probably relevant that I'm using a real folder for 'Trash' on all accounts, rather than the virtual wastebasket thingy.

See also here: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/772386
Comment 2 Ciaran Gultnieks 2011-12-13 08:46:23 UTC
Actually, for the sake of accuracy, it seems that this happens *much* less frequently with the above workaround of turning off the offline syncing, but it doesn't go away completely.
Comment 3 Milan Crha 2012-03-15 15:27:35 UTC
Máirín, do you use real trash folder too?
Comment 4 Máirín Duffy 2012-03-15 15:37:43 UTC
Hi Milan, how do I know if my trash folder is real or not? (I didn't know you could have a... fake?... one?)
Comment 5 Milan Crha 2012-03-15 17:36:05 UTC
I suppose you have a virtual trash then :) You can change in preferences of the account, where your Sent mails and Draft mails are supposed to be saved, same you can set your Trash and Junk folder, instead of using the virtual folder. This is rather IMAP specific and I do not want to come too much into details.
Comment 6 Milan Crha 2012-03-16 10:00:58 UTC
I see something similar. My mails are not reincarnate, but I see that the web interface of my mail server shows different folder content than the one shown in my evolution. It's best visible with unread messages. My evolution shows none unread, while the web interface shows couple unread messages. Tagging messages unread and read in evolution fixes the issue. This is the same as double-delete for you.

I guess this is caused by cancelling the sync operation before it's done, but I cannot reproduce this when trying. But maybe it's reproducible only with newly downloaded messages, which would explain the second try working.
Comment 7 Milan Crha 2012-11-01 13:40:49 UTC
Hmm, I cannot reproduce it now, with my locally installed dovecot server. I guess the steps are very specific. Is anybody of you able to reproduce this in current stable, which is 3.6.x, please? There had been done quite many changes in the code for 3.6.x, which may or may not influence this too.
Comment 8 Milan Crha 2014-01-30 07:52:18 UTC
This might be fixed for IMAPx within bug #721286, thus I mark this as a duplicate of it.

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