Open Bug 540015 Opened 15 years ago Updated 3 years ago

New mail notification mentions original account, not final one (after filters applied)

Categories

(SeaMonkey :: MailNews: General, defect)

SeaMonkey 2.0 Branch
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: mjulier, Unassigned)

Details

(Whiteboard: [DUPEME])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2

I have several POP3 accounts configured, with different checking frequency.

The new mail notification (small pop-up window arising from bottom right of the screen) often pretends that some account has a new message when it is actually another account.

I have the impression that when I click on "Get new mail for all accounts" this problem does not appear. Otherwise it seems to be random but frequent. Since it always appears when you are not concentrated on it, it is difficult to say.

Reproducible: Sometimes

Steps to Reproduce:
1.Get several POP3 accounts with different configuration (checking frequency, messages transfered to a folder of first account or not,...), enable junk mail filtering
2.Receive some mail
3.When Seamonkey automatically retrieves the mail, observe that the notification might say that the mail arrives in another account.
Actual Results:  
Notification "new mail for junkaddress@someprovider.fr"

Expected Results:  
Notification "new mail for mymainaddress@myprovider.fr"
Can you reproduce with Thunderbird v3.0.1?
Version: unspecified → SeaMonkey 2.0 Branch
Difficult to try: this does not happen at all time.
I can notice no problem during one day, and a problem for each new mail on another day.

Further, I do not really with to transfer my accounts to thunderbird 3.0.1 just for testing, I am too afraid not to be able to switch back to Seamonkey afterwards.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3   

WorksForMe.

Can you try and reproduce with SeaMonkey v2.0.3 ?
Yes, it still exists in SeaMonkey 2.0.3

I think I have a sort of explanation, and it probably comes from my configuration.

I have several mailboxes that are checked by SeaMonkey.
Let's say:
  A = main mailbox
  B = another mailbox
  C = yet another mailbox

I prefer to see them as folders in my main mailbox, like that:

Mailbox A:
  * inbox to A
  * outbox from A
  * other folders
  * inbox to B
  * inbox to C

So I define a filter, for each mailbox, with condition "size > 0" and effect "move to folder 'inbox to B' or 'inbox to C'".

When I receive a first message in mailbox B, it appears as a new message for the mailbox B, and it is moved to the folder "inbox to B". So I open that folder and the message is now read in the folder.

BUT the mailbox B is still signaled as "with new mail", and will stay like that because I have no reason to open it. I mean: there is a small green arrow on its icon.

Suppose I now receive a message in mailbox C, which is listed AFTER mailbox B. 

Seamonkey immediately copies the message to the folder "inbox to C", good.
And it wants to display a notification.
So it wonders: "which mailbox has unread mail". Mailbox B and C are signaled as "with unread mail": mailbox C because a mail has just arrived, mailbox B because the mail for it was moved away without me opening the mailbox.

So Seamonkey will display a notification for the first mailbox supposingly marked as "with unread mail", here mailbox B. This is the conclusion: I receive a message in mailbox C and I see "new mail in mailbox B".
Yes, SM only reports for the accounts that originally contained the new message(s). I think for the foreseeable future that's unlikely to change, but it might still be considered a bug.

Confirming, though I'm pretty sure we already have other bugs on the same topic (e.g. that the number of messages reported may be different from the final one after filters having been applied).

Also slightly adapted the summary.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: New mail notification does not mention correct account → New mail notification mentions original account, not final one (after filters applied)
Whiteboard: [DUPEME]
OS: Linux → All
Hardware: x86 → All
The new title does not describe precisely the behavior for this bug.

I receive some new mail on account A, and I have a rule that copies any mail from account A's inbox into some folder F. At this time, the notification says "1 new message for A". Now the folder F is "with 1 unread message". And the icon for account A is "with new mail" (small green arrow). It will stay so until I open account A's inbox, but I never open it so it stays "with new mail" until the end of the session.

I read the new mail in folder F: now, there is no unread mail, but account A is still "with new mail".

Then, I receive for instance 2 new messages on account B, but the notification says "2 new messages for A".

So the problem is not that the original account is mentionned. The problem is that when a new message arrives, Seamonkey displays a notification with the new message assigned to any account that is flagged as "with new mail", even though this message did not come through this account.
You need to log in before you can comment on or make changes to this bug.