Closed Bug 231845 Opened 21 years ago Closed 14 years ago

Not all mail automarked as junk is being moved to junk folder Via IMAP

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: baffoni, Unassigned)

References

Details

Behavior: I have my junk filter set to move all mail (via an IMAP connection)
determined to be junk to the junk folder of my IMAP account.  After the mail
client finishes it's mail analysis, only a portion of the emails marked as junk
are moved.  I have another IMAP account where all mail is not set to
automatically move or delete, but it is set to delete when I manually mark it as
junk.  However in that account, when I mark a bunch of messages manually as
junk, some are left behind marked as junk.  If I then mark some more messages as
junk, both the new messages and the old messages are deleted properly (also
manually deleting the messages works).

The junk process does not appear to correctly do cleanup on the folder after an
automatic move or delete.

Expected behaviour:  All messages that are supposed to be automatically moved or
deleted should be moved or deleted.

This is happening on 1.6final on both Windows XP and 2000 (Mozilla/5.0 (Windows;
U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113).
Clarify this point, please:
> If I then mark some more messages as junk, both the new messages
> and the old messages are deleted properly

Do you mean that when you mark a single item as junk, both it and all the 
previously marked-as-junk messages are deleted right then?


Possible dupe: bug 196732
Possibly related: bug 200594, bug 230499
That is correct but only in the case of the mark-only account setting:  on the
account with messages auto-moved, messages that are left as junk after an
auto-move do not appear to be deleted (or moved for that matter) when I manually
mark other messages as junk which are deleted.
I experience the same behavior with one more wrinkle.  Given an IMAP folder with
several unmoved messages marked JUNK, I select them all and the use MoveToFolder.
The messages move as requested, EXCEPT:  the last (closest to the bottom of the
screen) message routinely does not move and must be re-selected  and moved
separately.

Notice that this bottom message was selected during the original move attempt.
After the failed move, the selection gets cleared, the message stays marked as
JUNK, but it does not move until I move it manually.

Notice, too, that my JunkMail folder is local and not on the IMAP server.
This sometimes happens to me also, on dial-up, IMAP
4rev1 2003.339 on FreeBSD
And I am only marking deleted messages.
My fix is to check for new messages and this then moves and marks junk messages
as deleted, as expected.
This looks really like a dup of bug 196732 !
Product: Browser → Seamonkey
I'm having a similar issue

This is what happens

1 I pull all emails from my pop account
2 90% gets marked as junk and is moved into the junk folder as programmed immediatly
3 10% gets tagged as junk but stays in my emailbox. These emails only disappear
when I untag them as junk and then re-tag them as junk.

The issue has started since I installed 1.8 alpha 5
I'm having a similar issue

This is what happens

1 I pull all emails from my pop account
2 90% gets marked as junk and is moved into the junk folder as programmed immediatly
3 10% gets tagged as junk but stays in my emailbox. These emails only disappear
when I untag them as junk and then re-tag them as junk.

The issue has started since I installed 1.8 alpha 5
I'm on WIn XP+SP2, 
using build Mozilla 1.8a5   Gecko/20041122
The Junk mail is being marked automatically, but remains in my Inbox
the only way it is moved is if I click the Junk icon for each message twice (
deselect and reselect)  
- in which case it is deleted according to the rule ( delete any manually
selected Junk)
Bug 196732 Comment #30 is IMAP & "connection loss during Junk move" case.
(This is different problem from original problem of Bug 196732.)
Can some one get IMAP protocol log and attach log to this bug? 
(Do not paste long log data to this bug)

See http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap for
protocol log.
Don't forget to change "protocol:5" to "IMAP:5" when IMAP.
Please note that log file is overlayed on restart.
Michael Baffoni: are you still experiencing this problem with current builds?
Do you have a POP account which hasn't (or has, for that matter) experienced the 
same symptom?  Why shouldn't this be duped to bug 196732 (other than that bug 
being a big ol' mess of confusing reports)?  

See bug 196732 comment 30-34 for some IMAP-specific discussion, and state here 
whether you think that could be the same problem you've encountered.  As m-wada 
suggests, a protocol log would be helpful in debugging this.

Also, bug 196732 comment 56 claims mentions that manually marking another 
message Junk *does* move the laggards to the Junk folder (also IMAP).

All reading this bug should read bug 196732 comment 60.
Version: Other Branch → 1.7 Branch
Assignee: sspitzer → mail
I think I have a variation of this problem. When I quickly mark several messages as junk in a row, only the first message marked is moved to the IMAP junk folder. The other messages are left behind in the inbox. The workaround is to slowly mark messages, and wait for each msg to be moved before marking the next as junk. This is with TBird 1.5 and WinXP.
Assignee: mail → nobody
QA Contact: esther → message-display
Blocks: 310431
This never happened to me before, but some days ago when I moved my IMAP server from a local network to Google Imap server.
Now some times the messages are moved some times not, but they are always marked as junk.
If I run "Run junk mail controls on folder" command then they are moved.
I'm using TB 3.0.1

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
This was originally written on my Seamonkey client of the time.  I haven't seen this happen with Tbird (currently 3.1.9).  I haven't used Seamonkey in a long time to see if this is a current issue.  Should this be WFM, or do we need a new category "No longer relevant" ;-)?
Still needs someone still using SeaMonkey (preferably 2.1b2) to confirm that this bug is WFM.
(In reply to comment #14)
> Still needs someone still using SeaMonkey (preferably 2.1b2) to confirm that
> this bug is WFM.

The underlying causes should all be mailnews core, so I doubt attempting to get a SM user to confirm will add any value. I suggest closing.

(Stef's address is dead and Galen has moved to TB)
OK Thanks for the clarification.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.