Closed Bug 365982 Opened 18 years ago Closed 10 years ago

Filter action "Download message body" prevents notification of new message

Categories

(MailNews Core :: Filters, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mcow, Unassigned)

References

(Blocks 1 open bug)

Details

I have a POP account set up which I've had set for "Download headers only" for along time.  I also have a message filter set up on the same account to auto-recognize certain regular senders, to automatically download the body of messages from those people.

The problem -- which I've seen for a long time, but only recently figured the cause -- is that when these messages arrive, I get no notification.  Since I frequently have the account collapsed, I don't even notice the boldface Inbox, so I can miss new mail for several days.  (Fortunately, that's not really a problem with this account.)

Steps to reproduce:
1) Set up a POP account for "Download headers only"
2) Create a filter for the account to automatically download message body on some criterion.
3) Send a message that matches that criterion to the account.
4) Await message arrival.

Actual results:
4) When new message arrives, no notification; no New flag on the account

Expected results:
4) Notification (icon, plus alert or bell if so configured), and New flag on the account
So if the filter doesn't force the message to get downloaded, everything works as expected - you get a notification and the new flag?
Yes, that's right.  I think it's (at least in part) because the original bodyless message item is marked read prior to deletion, which turns off notification.
yeah, that's a good possibility.
This has started working for me with recent builds; I noticed it first with 2b2-0207, and I've just tested 0210 builds with trunk and branch.  David, do you know of any related changes?
Product: Core → MailNews Core
WFM per comment 4
Blocks: biff
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.