Closed Bug 483995 Opened 16 years ago Closed 15 years ago

[RFE] Inform user that all mails get deleted per default setting after fetching them from the server / allow user to configure this in 'New Account' dialogue

Categories

(Thunderbird :: Account Manager, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 231541

People

(Reporter: Tobbi, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 (.NET CLR 3.5.30729) Build Identifier: Version 2.0.0.19 (20081209) Some users might have a problem with the mails getting deleted after downloading them via POP3 (per default setting). I think it should be possible to set this behaviour directly in the account manager (as the messages are being downloaded right after a new account is set) or at least the user should be alerted about that all messages are getting deleted from the server Reproducible: Always Actual Results: TB downloads all messages from the server and deletes them. Expected Results: Ask the user whether to keep the messages on the server (in the New Account dialogue)
Summary: [RFE] Inform user that all mails get deleted per default setting after fetching them from the server / allow user to configure this in account manager → [RFE] Inform user that all mails get deleted per default setting after fetching them from the server / allow user to configure this in 'New Account' dialogue
Whiteboard: DUPEME
Kind of fixed for tb3 - bug 231541.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Unfortunately, "kind of fixed" is exactly true, as this is not really fixed. We are still deleting messages (with a 14 days delay), and we're not informing the user about it, and we don't allow the user to configure it during assisted (quick) account setup. I'm an advanced user, and I had dataloss on server because of this.
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.