Closed Bug 209264 Opened 22 years ago Closed 20 years ago

manual marking mail junk results in buggy display

Categories

(MailNews Core :: Filters, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529 I configured to automatically delete mails when I manually mark them junk. If I do so the mail is immediately moved, but the entry in the list still remains. Obviously there's a refresh missing. The problem is: the next mail entry moved up but is not visible. If you now try to un-junk-mark the visible but moved mail, you unintentionally mark another mail. Fortunately undo works ;-) Reproducible: Always Steps to Reproduce: 1. configure Junk controls to delete/move when manually makred 2. mark a mail junk
I have a similar problem, however I have noticed that it only affects mail that is marked as UNREAD. If a mail has been marked READ and is manually flagged as junk, it will move and refresh correctly.
I am not able to reproduce this symptom, with read or unread mail, in 1.4 Final, Win2K. Which mechanism are you using to mark the message as junk: context menu, junk-flag column, junk button on toolbar, or Message menu? Is the message in question at the beginning or end of the list, or somewhere in the middle?
The error is still there with 1.4 release, which I just installed. You should be able to reprodruce it this way: Set the option in the Junk mail controlls "when I manually mark messages as Junk -> move them to the Junk folder" I use the windows layout with the long folder overview on the left side, but I do not know if this is essential. Then turn the display of the Junk Status column in the mail list frame top right on. Supposed you received four messages which are now unread in your inbox like this: 1 No Junk 2 Junk 3 Junk 4 No Junk If you mark the mail 2 as junk by clicking into the Junk Status column, a tray icon is displayed. But as I configured the mail was immediately moved to the junk folder and is not there any more. Line two is now mail 3, although still mail two is displayed in this line. The number of mails, which is displayed with the folder tree to the left, is refreshed correctly, btw. If I now mark mail 3, line 3 is now invisibly inhabited by mail 4 and mail 4 is then moved to the junk folder. Thats pretty bad if it was no junk. One time I was astonished that the mail was not moved. So I tried to repeat the action by un-marking mail 2. However, this line was now not marked mail 3, and instead of unmarking mail 2 I marked mail 3 junk. If I mark a mail junk, then send the mail window to the back or minimize it, the list is displayed correctly when its displayed next time. Also if I select another folder and then go back to this folder. If I select a mail to the bottom of the list, which is then displayed in the message frame, and then mark a junk mail above, even stranger things happen: I did this with a rather full inbox, and scolled up in the list, and the selected entry was not visible any more. Now the misbehaviour was still the same, the junk-moved mail was still displayed, but the vertical position of the list jumped down to display the selected line. I'm sorry my answer took so long, I was on vacation. If you have more questions on details, I'm now back and will respond as fast as possible. I have also made screenshots, which I could send you in a pm.
This is for an IMAP mail account, or POP?
its a pop3 account I have created an IMAP account but I could not reproduce the same errors. It seems to be pop3 specific.
Product: MailNews → Core
Jochen Duckeck, is this bug still an issue for you with current builds (either TB or Mozilla)? If not, please mark this bug: Resolved | WorksForMe
No response from reporter => WFM
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.