210708 - messages should be deleted as they're downloaded

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: POP, enhancement)

Description

[Chris Jensen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030411
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030411

When downloading from a POP3 server, it appears that messages are not deleted
until all have been downloaded. If a lot of messages are being retreived, or the
link is very slow, and the download gets interrupted, then mozilla will then
download all the messages that were already retrieved.
Can messages instead be deleted from the server progressively so that a broken
download doesn't then require the same old messages to be downloaded?

Reproducible: Always

Steps to Reproduce:
1.Fetch messages
2.Let downloading progress through a significant number of messages (but not all
of them) and then press stop, or otherwise interrupt the connection to the server
3.Fetch the messages again


Actual Results:  
The messages that were retreived the first time will be retreived again and
duplicated.

Expected Results:  
Messages should have been deleted from the server as they were downloading,
resulting in the second mail download picking up where the last download left off.

Comment 1

[Jo Hermans]

should we reopen bug 52705 ?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[John David Galt]

This appears to be a dup of bug 284526.