Closed Bug 218711 Opened 22 years ago Closed 21 years ago

Marking messages as junk does not move them to Junk folder even when option is set

Categories

(MailNews Core :: Filters, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ben, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 I go to Junk Mail controls, Enable junk mail controls, set it to move messages marked as junk to the Junk folder, and set it so that messages that I set as junk should get moved to the Junk folder. I exit, and event restart Mozilla. When I come back, the settings are as I set them, but when I mark an email as junk, it does not get moved to the Junk folder. As a matter of fact, no emails ever get moved to the Junk folder. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Ben: Please retry with a more recent build of Mozilla. Also, check the comments in bug 206427. Thanks. Also, as you say that no emails ever get moved to the Junk folder: can you move messages to Junk manually?
Mail is getting marked as spam in my Inbox. It just isn't being moved into my Junk folder. I can move mail manually into the Junk folder, it just doesn't do it automatically even though under Junk Mail Controls I have "Move incoming messages determined to be junk mail to:" "Junk" folder on: Peikes (my main account). I haven't tried the newest build yet.
Switched to using the "Other: Junk on Peikes" under Junk Mail Controls and now everything is working. Haven't tried switching back to "Junk" folder on: Peikes. Will try later.
Ben Peikes, have you tried retesting this bug, as you said you would in comment 3?
No response from reporter; =>WFM Ben Peikes, feel free to reopen if in fact the problem still exists.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.