Open
Bug 456094
Opened 17 years ago
Updated 3 years ago
save copy of all incoming mail to folder, and mark that folder as read
Categories
(MailNews Core :: Filters, enhancement)
Tracking
(Not tracked)
NEW
People
(Reporter: rfc469, Unassigned)
References
(Depends on 1 open bug)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9) Gecko/2008061711 Minefield/3.0
Build Identifier:
It's a little thing, but there doesn't seem to be any way to save a copy of all incoming mail to a folder and mark the mail *in that folder* as read, automatically.
For example, my very first filter in the chain:
action="Copy to folder"
actionValue="imap://user@imaphost.rhythm.com/ allmail"
condition="ALL"
This saves a copy of all incoming mail to " allmail" but there is no way to mark the saved copy as read. If I add a rule "Mark As Read" that will apply to both the " allmail" copy (which I want) and the original (so all of my mail is marked as read).
Basically I just want a way to save a copy and not be notified about it. One way this could be achieved is to add a rule like "Mark Copy As Read", which would be used after the copy. Thanks.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•17 years ago
|
||
Confirming as RFE
It would be possible to use a second filter for marking as read but that doesn't work because you can not filter based on the folder (bug 294632).
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: General → Filters
Ever confirmed: true
Product: Thunderbird → MailNews Core
QA Contact: general → filters
Comment 2•17 years ago
|
||
I did an implementation of this as a custom filter action in my FiltaQuilla extension - but for some reason that I no longer recall I only enable it for manual actions, not for normal automatic actions.
Updated•14 years ago
|
Depends on: 294632
OS: Linux → All
Summary: no way to save copy of all incoming mail and mark as read → save copy of all incoming mail to folder, and mark that folder as read
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•