138109 - Alert: pop only: clicking on animated alert takes you to inbox first not first folder w/new mail

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[grylchan]

Spun off bug 135753 as that bug fixed it for imap accounts only.

If a filtered mesg arrives in your pop account, if you click on
the link in the alert, it takes you to the inbox instead of
filtered mesg folder.

The count on new mesgs for a filtered pop folder is correct
in the alert. So no problems there.

Steps to reproduce
1.Create a pop mai account
2.Add a new folder
3.add a filter for that new folder
4.Set you biff setting for 1 min
  also set your pref to auto download any new mesgs.
5.Quit/restart/login to pop mail
6.Compose a mesg that will be filtered
7.Send it
8.Click on your account name or on Local folders in
  3 pane window
9.Wait 1 min
10.When the alert appears, click on the link

result: takes you to the inbox
expected: take you to the filtered folder

Comment 1

[grylchan]

taking olga off qa and adding myself.

Note was Using commercial trunk 2002-04-16-06-trunk (2002041603) on
NT, 2k, xp, and win98

Comment 2

[Scott MacGregor]

Gary, for your pop account is biff configured to download the new message or
just to tell you, you have new mail? i.e. have the messages been downloaded and
we still take you to the wrong folder?

Comment 3

[grylchan]

Scott,
When I ran this test I had the following settings:
 These were checked: 
  Check for new mesgs every 1 min
  Automatically download any new mesgs
  leave mesgs on server

 everything else unchecked.

I created a filter, sent myself a mesg that would be filterd
and waited for biff to go off. When I saw the alert I clicked on
the link and it took me to the inbox and not the filterd folder
(which showed that I have new mesgs).

Comment 4

[Michael Buckland]

Discussed at mail news bug meeting.  Decided to minus this bug.  

Comment 5

[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 6

[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