Closed
Bug 190356
Opened 23 years ago
Closed 23 years ago
[junk] - IMAP only, messages flagged as Junk then moved to the Junk folder lose the Junk flag with the Junk folder
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 180857
People
(Reporter: esther, Assigned: sspitzer)
Details
Using trunk build 20030121 on winxp and linux, with Junk Control on and a Junk
folder that is marked as Special with IMAP accounts only, if you mark some Inbox
messages as Junk, wait a few minutes for the updating to index then move them,
using menu item or drag n drop, to the designated Junk folder the Junk status is
removed from the mail messages. This happens when moving one or a group of
messages. Exiting and relaunching doesn't change the status. I tried moving the
messages that have not been flagged as junk to see if the action alone would
flag them, that did not work either.
Note, this works in POP accounts but not in IMAP accounts.
1. Launch app and open profile that and IMAP account with Junk controls on and
log in.
2. Mark a message as Junk, wait a minute, then drag the message to the
designated Junk folder.
3. Select a message that is not marked as Junk and drag it to the designated
Junk folder.
4. Open the Junk folder
Result: the messages you just dragged into that folder that had junk status and
the ones that did not have the junk status flag are both missing the junk status
flag.
Expected: Messages with existing flag should still have it, messages not flagged
should be flagged by the process of moving them into the special folder.
nominating, I believe this can confuse the user if the status is missing even if
the message has been added to the junk mail database.
Keywords: nsbeta1
Summary: [junk] - IMAP only, messages flagged as Junk then moved to the Junk folder lose the Junk flag with the Junk folder → [junk] - IMAP only, messages flagged as Junk then moved to the Junk folder lose the Junk flag with the Junk folder
related bug 180857
I will recheck this with the 1-27 trunk build to see if fix to 180857 fixed this.
QA Contact: laurel → esther
*** This bug has been marked as a duplicate of 180857 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•