Erroneously flagged "sorta junk" mail, keeps reverting to junk status after manual marking



16 years ago
11 years ago


(Reporter: gobbel, Assigned: sspitzer)


Windows XP

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925

I use IMAP for all of my accounts, and I have "move to junk folder" checked,
both for automatically-recognized junk mail and for mail manually marked as
junk.  I occasionally see messages that are marked as junk, but which remain in
my inbox.  Most of the time, these are messages that should not have been marked
as junk.  If I manually mark them as not-junk, the junk mail flag reappears
after about a minute or so, but they are still not moved to the junk folder. 
After about 5 or 6 cycles of seeing the message marked junk, and manually
marking as not-junk, the message will finally stay as not-junk.  This does not
seem to be related to the type of IMAP server, since I see it in one account
that uses the UW server, and another that uses dovecot.

Reproducible: Always

Steps to Reproduce:
1. Set Junk Mail controls to "move to junk folder".
2. Observe messages erroneously marked as Junk, but which do not get moved to
the Junk folder.
3. Try to manually mark as non-junk.
4. Wait a couple of minutes, observe the Junk flag reappearing (but the message
stays in the inbox).
5. Mark as non-junk again.
6. Repeat until message stays as non-junk

Actual Results:  
Message is repeatedly marked as junk, but not moved to Junk folder.

Expected Results:  
When I manually mark a message as non-junk, it should stay that way.  On the
other hand, when a message is marked as junk, it should also move to the Junk

Restarting doesn't seem to help.  This bug has been around for as long as the
junk mail controls have been available.

Here is the full source of a message that is, right now, flipping to "Junk",
even though I keep marking it non-junk:

Received: from ([])
	by with esmtp (Exim 4.20)
	id 1A4fev-0008E4-4F
	for; Wed, 01 Oct 2003 05:00:45 -0700
Received: from ([])
        by (ACM Email Forwarding Service) with ESMTP id CRY73883
        for <>; Wed, 01 Oct 2003 08:00:14 -0400
Received: from (localhost [])
	by (Postfix) with ESMTP id 26719ABB6A
	for <>; Wed,  1 Oct 2003 05:00:13 -0700 (PDT)
Date: Wed, 01 Oct 2003 05:00:13 -0700
Message-ID: <>
Subject: mailing list memberships reminder
X-No-Archive: yes
X-Ack: no
X-Mailman-Version: 2.0.13
Precedence: bulk

This is a reminder, sent out once a month, about your mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to  Thanks!

Passwords for

List                                     Password // URL
----                                     --------                          xxxxxxx
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.