110083 - unread mail filed into inbox gets filtered

Status: RESOLVED FIXED

(MailNews Core :: Filters, defect)

Description

[Jon Granrose]

I'm not sure if this is a bug or a feature.

In 6.2 RTM builds, unread mail filed into the inbox gets filtered and sent to
different folders based on whatever filter rules you have.  This is a nice
workaround to not being able to apply filters on mail already received, but I'd
rather be able to file mail (read or unread) in my inbox without it being
filtered.  Most often what happens is I have a few dozen filters and the last
one is a spam filter that files any unfiltered mail not addressed to me into a
SPAM folder.  Occasionally I get real mail that I want to send back to my inbox.
 Filing it in my inbox while it's still unread makes it go back to my SPAM folder.

Workaround is to mark the mail as read and then file it in the inbox and it
won't be filtered.  I haven't tried this in trunk builds since the trunk has
been so funky lately.

Comment 1

[scottputterman]

I just reproduced this on the 12/29 build. It still exists.

Comment 2

[David :Bienvenu]

imap or pop3? My guess is you're talking about imap, in which case, I'm not
surprised.

Comment 3

[Andreas Troschka]

If I have rightly understud your request you have only to use fantasy, and you
can find various ways to solve your problem without requesting any enh to the
guys already engaged in more energy consuming bugs.

An example:

Add a filter before the "Put into SPAM folder" using a label as flag to signal
that the e-mail has been already filtered.
Than put a condition in the other filters (inbox) that checks this flag.
If it is set, the e-mail has been already filtered, so do nothing and your 
e-mail remains into the inbox.
If the flag is not set, go thurther with processing the other rules of the filter.

I hope this will help you.
     

Comment 4

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 5

[guanxi]

Fixed on Moz 1.5 final on WinXP Pro.

I don't know when or how it was fixed; I just happened across this bug.