Stopping POP transfer functionality broken or missing



12 years ago
10 years ago


(Reporter: stephen, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: closeme 2008-11-06)



12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv: Gecko/20070219 Firefox/
Build Identifier: version (20070221)

After mail is fetching the 'STOP' button is available. Pressing STOP and then fetching again, the STOP button is dim (disabled). At this point, a fetch can only be stopped by quitting application.

Also, STOPing transfer does not appear to delete the messages from server (yes, I have checked settings).

My situation is that I have a mailbox with 90,000 messages in it. After downloading 30,000 and cancelling transfer, 90,000 remain at mailbox. Sadly, I had to resort to using Outlook to solve my dilemma--they have a stop button which, when pressed, not only stops downloading POP but resolves those downloaded, deleting them from the server.

Looking at the status bar at the bottom and transfer activity log it doesn't appear that Thunderbird is doing any post-processing. I'm guessing that commanding server to delete messages mirrors Outlooks function of doing so once they are in the inbox and verified.

Reproducible: Always

Steps to Reproduce:
1. Download big chunk of POP mail
2. Press Stop, disabling the button
3. Re-request POP download
4. Observe Stop button remains disabled
5. Observe no post-processing appears to be happening to downloaded messages

Expected Results:  
Dialogue box and application processing which removes messages downloaded so-far from the server
Assignee: mscott → nobody
Reporter, does this issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now
Whiteboard: closeme 2008-11-06
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to the bug with your reasons why.
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.