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 663693 - Mails fetched using POP3 are not expunged when connection dies
Mails fetched using POP3 are not expunged when connection dies
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[pop]
Depends on:
Blocks:
 
 
Reported: 2011-11-09 13:20 UTC by Christoph Wickert
Modified: 2021-05-19 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christoph Wickert 2011-11-09 13:20:37 UTC
When you fetch a lot of mails over a flaky internet connection, it can easily happen that the connection dies before evo finished fetching all mails and expunges them. The next time you connect evo again fetches all mails and you end up with a lot of duplicates.

Would it be possible to expunge mails one by one *directly* after fetching them instead of at the end of the process? I'm afraid this will slow things down.

$ rpm -q evolution evolution-data-server
evolution-3.0.3-1.fc15.x86_64
evolution-data-server-3.0.3-1.fc15.x86_64
Comment 1 Milan Bouchet-Valat 2011-11-09 13:47:18 UTC
Maybe it's worth making it clear we're talking about POP3 here.

I think messages have a unique ID that could easily be used to check whether they have already been downloaded. That's what happens AFAIK when you choose to keep the messages on the server: the mail client has a way to know which messages are new.
Comment 2 Milan Crha 2012-03-01 17:32:46 UTC
There were done some fixes and improvements in the POP3 code recently, which will be available in 3.4.0. It'll be good to try with that version, also because 3.0.x is unsupported by upstream these days.
Comment 3 Christoph Wickert 2012-04-11 09:56:08 UTC
I still see this in 3.4.0. An easy way to test this is a flaky 3G connection or a disconnect of a router. As long as evolution-networkmanager doesn't see the connection loss the problem still occurs.
Comment 4 André Klapper 2021-05-19 12:13:14 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.