Bugzilla

Unfortunately, comment 3 does not help to find a solution for this bug, apart from pointing out the obvious: different people = different needs. That's the equation that calls for customization UI, or transparency at least.

And can we please refrain from that noise about POP3 not being the right protocol to leave mails on server, talking longer etc. While technically true, from a user's POV that's completely irrelevant. Millions of users have no idea about the technical difference, and millions of users deliberately DO keep their mail in their pop inbox, and not just 14 days.

Also, there seem to be misunderstandings in comment 3 about what this bug is about. It's NOT about an "Are you sure?" warning when the user deliberately changes "leave on server" setting. It might also help to know the default settings before adversely commenting on a bug that is based on default settings.

Furthermore, in view of the tons of discussion where people complained about dataloss in TB2, I don't understand how anyone could NOT be glad that we at least no longer destroy messages *immediately* after account setup (now only after a 14 days delay).

Finally, arguments starting with "if" followed by a condition that doesn't apply to a potentially large no of users are'nt useful for supporting problematic default settings.

FTR: POP3 default settings for quick account setup are:
[x] Leave messages on server
    [x] for at most 14 days
    [x] until I delete them

These settings are destructive (on purpose), and we don't communicate them in any way during the setup. And, we don't warn the first time we automatically delete messages from server after 14 days. The perfect recipe for dataloss. No wise talk in the world will make this problem go away.

Unfortunately, comment 3 does not help to find a solution for this bug, apart from pointing out the obvious: different people = different needs. That's the equation that calls for customization UI, or transparency at least.

And can we please refrain from that noise about POP3 not being the right protocol to leave mails on server, taking longer etc. While technically true, from a user's POV that's completely irrelevant. Millions of users have no idea about the technical difference, and millions of users deliberately DO keep their mail in their pop inbox, and not just 14 days.

Also, there seem to be misunderstandings in comment 3 about what this bug is about. It's NOT about an "Are you sure?" warning when the user deliberately changes "leave on server" setting. It might also help to know the default settings before adversely commenting on a bug that is based on default settings.

Furthermore, in view of the tons of discussion where people complained about dataloss in TB2, I don't understand how anyone could NOT be glad that we at least no longer destroy messages *immediately* after account setup (now only after a 14 days delay).

Finally, arguments starting with "if" followed by a condition that doesn't apply to a potentially large no of users are'nt useful for supporting problematic default settings.

FTR: POP3 default settings for quick account setup are:
[x] Leave messages on server
    [x] for at most 14 days
    [x] until I delete them

These settings are destructive (on purpose), and we don't communicate them in any way during the setup. And, we don't warn the first time we automatically delete messages from server after 14 days. The perfect recipe for dataloss. No wise talk in the world will make this problem go away.