Closed Bug 288233 Opened 20 years ago Closed 20 years ago

Incoming mail is coming into junk folder on local folders not inbox

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Steve, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319

Version 1.7.6
All my mail is coming into my Junk folder on the Local Folder group, instead of
the Inbox.

This started AFTER I activated Junk controls in version 1.7.6. Before that
everything worked as it should.  After I activated junk controls Mozilla would
mark messages as junk even if they were in my address book.  I deactivated junk
and the messages all began to show up in the junk folder on the Local Folder group.

I reactivated and deactivated but the messages continue to go into my Junk folder.

I've reinstalled 1.7.6.  This did not happen in 1.7.5.  Is it safe to go back to
1.7.5?

Reproducible: Always

Steps to Reproduce:
1. open mail


Actual Results:  
Mail gets "deposited" into my Junk folder on the Local Folder group, instead of
the Inbox.

Expected Results:  
I'd like the incoming messages put into the inbox.  Messages from people in my
address book should be placed there, and suspected junk should be put into the
junk folder on the local folder group as my preferences dictate.

Using Modern theme
I had a filter on incoming looking for a string.  If found, it was supposed to
put the message into the JUNK folder.  

Apparently there was something wacky with the filter, and it was thinking every
message met the criteria and therefore sent everything to the JUNK folder.

When I removed the filter, the messages started going back into the INBOX.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Component: MailNews: Notification → MailNews: Message Display
QA Contact: search
You need to log in before you can comment on or make changes to this bug.