247096 - new mail notification for deferred pop3 accounts uses the name of the deferred to account, not the original account

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[David :Bienvenu]

E.g., if you use global inbox, when new mail arrives from your pop3 server, the
new mail notification says "3 new messages arrived in Local Folders", which is
technically correct, but maybe we should reword it to indicate what the source
account was. Though, if you have 3 pop3 servers and they all get new mail, I'm
not sure what we want to say - 10 new messages in Local Folders, or 3 new
messages in account1, 3 new messages from account2, and 4 messages from account3?

Comment 1

[David :Bienvenu]

I think I'm going to try to get a separate alert for each server, or try to get
just one alert for the destination folder, whichever seems more doable.

Comment 2

[David :Bienvenu]

the separate alert for each server is turning out to be way too hard - it's easy
enough to get the alert to pop up the first time by poking the root folder for
the deferred account with the number of messages that were retrieved, but it's
very hard to maintain the hasnew state for that root folder in the face of
changes to the messages in the local folders. It's also very hard to incorporate
the junk mail filtering with the individual account biff, because the junk mail
classification stuff only knows its running in the target folder, e.g., the
local folders inbox.

So I think we'll have to end up with new mail indicator for just the global
inbox. Otherwise, I'd need to rewrite too much of the biff code (not that it
couldn't use it!)

Coalescing new mail indications for the global inbox will probably be tricky
enough in the face of junk mail classification...

Comment 3

[David :Bienvenu]

Attachment: abandoned attempt to get deferred accounts to biff.

this was the route I was taking - if I could solve the other problems, like
clearing biff, this might be worth reviving.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420