Implement an auto-archive option

NEW
Unassigned

Status

enhancement
10 years ago
a month ago

People

(Reporter: brad, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091220 Lightning/1.0b2pre Shredder/3.0.1pre ThunderBrowse/3.2.6.8

TB puts all archived messages under the same year (2009, 2008, etc) folder.  The year folder is a great idea, but the original folder structure should be created under Archives/yyyy. As an example, if there was a folder under Local Folders called Friends/Ron, then if a message from Dec 2008 should be archived under Archives/2008/Friends/Ron.  Dumping everything under one folder does not work well.

Also, an auto-archive option needs yo be implemented under the properties/retention tab for all folders, as well as a default system-wide archive policy.  This is a serious issue for commercial clients.

Reproducible: Always

Steps to Reproduce:
1. Archive a message. Archive a second message from a different folder received the same year as the first archived message. Both messages will be in the Archive folder under the same year folder.
2. Try to set auto-archive preferences.  Unable to find any.
Component: General → Mail Window Front End
QA Contact: general → front-end
Whiteboard: dupeme

Comment 1

10 years ago
Me too. First bit of this is Dupe of Bug 533815.
(In reply to comment #1)
> Me too. First bit of this is Dupe of Bug 533815.

Let's keep the second part then ;-) Thanks for finding the dup Daniel.
Summary: Need Archive Enhancements → Implement an auto-archive option
Whiteboard: dupeme

Comment 3

10 years ago
I would appreciate a lot this feature, too.

Comment 4

9 years ago
I'm missing this feature.

Updated

9 years ago
Duplicate of this bug: 583529

Comment 6

9 years ago
> Also, an auto-archive option needs yo be implemented under the
> properties/retention tab for all folders, as well as a default system-wide
> archive policy.  This is a serious issue for commercial clients.

Confirming as a valid enhancement request. Note that this is different from
the existing bug 93094 as the bug there is asking for an off-profile archive functionality, whereas this RFE merely requests moving messages to Archives.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 7

9 years ago
My request (583529) has been marked as a duplicate of this. IT ISN'T! It seems close to 93094.

That said, this is as good a place as any to put it.

Firstly, I archive stuff by MONTH, so simply recreating my folder structure under /archive/year is NOT what I want.

And secondly, why should Thunderbird *force* me to put it under archive? What I want is, under properties/retention, to be able to say "move all emails over one month old to folder X" where it's MY choice of X, not Thunderbird's.

Cheers,
Wol

Comment 8

9 years ago
This bug here has been retargeted for the second part per comment #2, hence it appeared identical to what you proposed. Bug 93094 started off with archiving
to some external media, and got a bit confusing on a second read with similar requests to archive into a folder within Thunderbird, so that one eventually may be a catch-all bug (which is probably a bad idea as these are two distinct functions). Anyway, someone else feel free to dupe all to 93094 if you think it's the right thing to do.
Duplicate of this bug: 597445
Totally agree with the second part, an auto archive feature is sorely needed and would be so awesome.

What I've done in the meantime is set up a message filter to copy all messages to a separate folder in my Local Folders "folder", and the filter is set to apply whenever checking for mail (automatically and manually). But the problem with this is, message filters aren't run on sent items, so only received e-mails are getting copied to the separate folder and archived.
You need to log in before you can comment on or make changes to this bug.