Open Bug 481185 Opened 16 years ago Updated 2 years ago

Remove all attachment when Archiving

Categories

(Thunderbird :: General, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: cedric, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) Build Identifier: version 3.0b2 I'd like to use Archive to keep old messages with no attachment. It would be great if I have a way to set up Archive folder just to keep message and automatically remove any attachments. Reproducible: Always
Confirming RFE.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Summary: Remove all attachment in Archive → Remove all attachment when Archiving
This may be a good idea only if the suppressed attachments are saved to a previously defined folder else you loose data. Presently I detach manually the attachments before back-up.
Detaching manually is an annoying step, especially if you work with a company where you get a lot of meaningless attachments (like logos in signatures). I'd suggest that a suitable UI would offer choices. * Archive normally (like now) * Strip all attachments * Strip attachments on messages you have sent. The latter is useful, because if I SEND an email, then I've already got the attachment elsewhere on my disk, for example I've sent about 100 copies of a handout which is 10Mb, so its taking up 1Gb of archive space. This adds up quick, even more so if that 1Gb is being stuck on the TImeMachine backup every time it backs up. So even better would be if TB could figure out how to archive only one copy of an attachment (e.g. by doing an MD5 checksum on it, and saving a reference to that checksum).
I propose a 4th option : * Strip attachments on messages you have received by "detaching" them to a special previously defined (e.g. default) folder so you do not loose data. Your proposal will probably use the "detach all" or "delete all" functionality, it should be checked that using twice (before and after archiving) detach/delete does not cause any problem.
Depends on: 709183
No longer depends on: 709183
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.