Closed
Bug 52705
Opened 24 years ago
Closed 24 years ago
Pop3 -- deleting messages right after downloaded in case of connection broke
Categories
(MailNews Core :: Networking: POP, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
Future
People
(Reporter: jefft, Assigned: naving)
References
Details
Subject:
POP server mail deleting
Date:
Mon, 11 Sep 2000 14:51:40 +0200
From:
Henning Schnoor <henning.schnoor@gmx.net>
Organization:
Another Netscape Collabra Server User
Newsgroups:
netscape.public.mozilla.mail-news
Hi,
Yesterday I fetched my mail (about 500 emails) from a POP server (using
M17), and the connetcion broke after about 200 mails. When I restarted
downloading, there were still 500 mails.
I think the mail client should delete every mail directly after
downloading, so you don't have to download all of them again. This
*does* happen quite often, it's not just a thepretical problem.
What do you think?
See you,
Henning
--
http://schnoor.debox.de
No data loss, just duplicates. Future...
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 3•24 years ago
|
||
reassigning jefft's bugs to naving
Assignee: jefft → naving
Status: ASSIGNED → NEW
same behavior here when you press stop during the download. it's a very
unpleasant behavior
Comment 5•24 years ago
|
||
I suppose that's not bug in mozilla. POP3 protocol deletes mail from server when
and only when QUIT is issued. All messages, marked as deleted reset to normal
state, if current pop connection is dropped without QUIT command (safety
measure, to prevent loss of data). Only possible workaroud for mozilla is to
'remember' alredy downloaded mails and then to delete complete maildrop on server
this functionality was present in Netscape 4.x
it's very annoying because when there's a network or server problem in the
middle of a donwload of one thousand mails, you can end up with lots of
duplicate mails.
on the pop side, it's just a matter of download mail number x, then delete mail
number x (ie command DELE x) (easy and completely doable)
on the mozilla side, it seems pop is implemented as a state machine.
so the fix would be to set the machine to delete after each mail is downloaded
and then going to donwload the next mail
at this moment the state is not changed to delete until all mails are downloaded
which is not the good solution.
Note to whoever works on this one--This behavior also occurs if the user has
marked Leave messages on server. The fix for this should also include the
situation where messages are marked as "Read" or whatever the official POP term
is for messages that once downloaded, remain on the server but will not be
downloaded in the future.
Assignee | ||
Comment 10•24 years ago
|
||
This bug should now be fixed. I have added code to save the POP download
state, no matter what your preferences are ?
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 11•24 years ago
|
||
works now for me with build 2001041610 on linux (using pop and not leaving
messages on server)
Assignee | ||
Comment 12•24 years ago
|
||
verified based on the previous comments
Status: RESOLVED → VERIFIED
Comment 13•24 years ago
|
||
Sorry, this still does not work.
I'm using build 2001041804 on Win32, and did the following:
I started downloading mails from a POP account, there were 157. During the
download (after downloading about 100 mails), I killed Mozilla with the Windows
Task Manager to "simulate" a crash.
I restarted Mozilla, and restarted the download. I expected Mozilla to download
the ~50 mails which were left, but instead all 157 mails were downloaded again.
Does this fix not appear in the Win32 builds yet?
Assignee | ||
Comment 14•24 years ago
|
||
killing an app like that, will be an abrupt end and will not allow any code to
be executed at all. I don't think much can be done about it in the POP3 code.
Assignee | ||
Comment 15•24 years ago
|
||
Also this bug is about connection broke. I am pretty sure it would work if
you killed your internet connection.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•