[GH-ISSUE #2357] trap: thunderbird using default-profile + archiving mails to external folder/device does delete them finally #1570

New issue

Closed

opened 2026-05-05 08:13:53 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 08:13:53 -06:00

Owner

Originally created by @orcus-de on GitHub (Jan 20, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2357

yes I'm aware (after running into the issue) that one can adjust the configuration to personal needs ...

Using a default-profile with thunderbird does hide a nasty trap if being used with an existing thunderbird-installation setup to archive mails from an imap account to a custom local folder.
Archiving mails will delete them form the imap-server and store them at the (previously defined) external folder/storage (which is not covered by the default thunderbird-profile). Closing thunderbird does free the (unhandled) external folder/storage - thus deleting the mails finally.

Besides that is easy to recognize afterwards - it's just too late for the affected mails.

Chances are high other people/companies will get hit by that too, if they do archive older email after some perdiod to be "safe" and start using firjail at some later time.

At least some comment inside the default-profile might be a helpful warning to remind people.

Originally created by @orcus-de on GitHub (Jan 20, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2357 yes I'm aware (after running into the issue) that one can adjust the configuration to personal needs ... Using a default-profile with thunderbird does hide a nasty trap if being used with an existing thunderbird-installation setup to **archive mails** from an imap account to a **custom local folder**. Archiving mails will delete them form the imap-server and store them at the (previously defined) external folder/storage (which is not covered by the default thunderbird-profile). Closing thunderbird does free the (unhandled) external folder/storage - thus deleting the mails finally. Besides that is easy to recognize afterwards - it's just too late for the affected mails. Chances are high other people/companies will get hit by that too, if they do archive older email after some perdiod to be "safe" and start using firjail at some later time. At least some comment inside the default-profile might be a helpful warning to remind people.

gitea-mirror closed this issue

2026-05-05 08:13:54 -06:00

gitea-mirror commented

2026-05-05 08:13:56 -06:00

Author

Owner

@Fred-Barclay commented on GitHub (Jan 21, 2019):

Thanks - I've added a note. 👍

@Fred-Barclay commented on GitHub (Jan 21, 2019): Thanks - I've added a note. :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1570

No description provided.

Rows
Columns