Closed Bug 352163 Opened 19 years ago Closed 19 years ago

spam not moved to Junk folder automatically

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 351545

People

(Reporter: bob.lord, Assigned: mscott)

Details

(Keywords: regression)

When I launched TB this morning, it flagged a number of messages as being spam, but did not move them automatically to the Junk folder. My junk settings are set to move junk message to "Junk" folder on my IMAP server, and there is no other spam in the Junk folder. I also got a strange error about there being too many connections to the IMAP server even though I have no other IMAP clients running. That *might* be a clue, but I should know more in the next day as more spam comes in. There are no errors on the error console. (Shouldn't there be since I got that IMAP error?) I was running Saturday's build, and I just upgraded to today's build: version 2 alpha 1 (20060911) Running on Linux.
I just got a new spam email with today's build. TB correctly recognized it as spam, but did not move it to the Junk folder. It remained in my Inbox.
Note that I only started to see these problems when I started from scratch with a new profile. Is that perhaps a clue? Maybe something changed in the prefs code?
You have to explicitly tell Thunderbird to move mail marked as Junk to the Junk folder in Account Settings. Did you do this?
(In reply to comment #4) > You have to explicitly tell Thunderbird to move mail marked as Junk to the Junk > folder in Account Settings. Did you do this? Yes, but it has no affect, even after restarting the app.
Do you actually have a Junk folder created? (xref bug 352225) Otherwise, see bug 196732 comment 60 -- this bug may be dupe of that bug or one of the bugs mentioned in that comment.
(In reply to comment #1) > I just got a new spam email with today's build. TB correctly recognized it as > spam, but did not move it to the Junk folder. It remained in my Inbox. > (In reply to comment #1) > I just got a new spam email with today's build. TB correctly recognized it as > spam, but did not move it to the Junk folder. It remained in my Inbox. > I could have written everything you said here myself. My situation is identical.
(In reply to comment #0) > When I launched TB this morning, it flagged a number of messages as being spam, > but did not move them automatically to the Junk folder. > > My junk settings are set to move junk message to "Junk" folder on my IMAP > server, and there is no other spam in the Junk folder. > > I also got a strange error about there being too many connections to the IMAP > server even though I have no other IMAP clients running. That *might* be a > clue, but I should know more in the next day as more spam comes in. > > There are no errors on the error console. (Shouldn't there be since I got that > IMAP error?) > > I was running Saturday's build, and I just upgraded to today's build: > version 2 alpha 1 (20060911) > > Running on Linux. > Save for the build you used (I'm running 2 alpha 1 (20060724) my problem is idential. I could have written exactly what you did here.
Oddly, it seems to be working now. For a while I had manually selected the folder into which TB should move the spam. Then I set it back to the generic "Move new junk messages to Junk folder on <server>". Now it seems to be working. I'm worried that this is a bug that only shows up with new profiles. I had to blow away my profile and start from scratch (another bug), but I think most testers just keep upgrading and may not see this bug.
(In reply to comment #9) > I'm worried that this is a bug that only shows up with new profiles. I had > to blow away my profile and start from scratch (another bug), but I think > most testers just keep upgrading and may not see this bug. I think you are correct that this is a new-profile issue; see bug 351545.
Mike, did you think Bug 351545 might fix this to or that it's just related?
Flags: blocking-thunderbird2+
(In reply to comment #11) > Mike, did you think Bug 351545 might fix this to or that it's just related? I suspect it's a dupe, since Bob said he saw this problem with new profiles and recent builds. However, I'm not sure if that bug or its fix applies for IMAP accounts (it's filed as "Local Folders" and I don't have a convenient IMAP account to test with). But, that fix *is* in place. Bob Lord, can you retest with a current build and see if you're still seeing the same problem?
(In reply to comment #12) > (In reply to comment #11) > > Mike, did you think Bug 351545 might fix this to or that it's just related? > > I suspect it's a dupe, since Bob said he saw this problem with new profiles and > recent builds. However, I'm not sure if that bug or its fix applies for IMAP > accounts (it's filed as "Local Folders" and I don't have a convenient IMAP > account to test with). But, that fix *is* in place. Bob Lord, can you retest > with a current build and see if you're still seeing the same problem? > I had to rebuild my profile again today (details in bug 356030). So I should be able to tell if it's fixed for new profiles in the next day or so.
(In reply to comment #13) > I had to rebuild my profile again today (details in bug 356030). So I should > be able to tell if it's fixed for new profiles in the next day or so. ... and ...?
Bob Lord, it's been over a month since you said you'd check if the fix for bug 351545 fixed your problem as well.
For some reason I had my pref set to move spam to the Junk folder specified, rather than to the generic Junk folder. I made that change and will see if it works now. Sorry for the delay in reporting back.
I have one data point suggesting that this works now. However, given that I've had problems when I created a profile from scratch, others might want to test that use case.
There was testing already for the new profile case. If you find later that this problem is not solved to your satisfaction, feel free to reopen this bug. *** This bug has been marked as a duplicate of 351545 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
I uninstalled Thunderbird, saved my profile's e-mail to another folder, deleted my profile, and then installed the 20061122 1.8 nightly. (I.e. "version 2 beta 1 (20061122)") I manually copied my local mail folders from my saved stash into my new profile's Mail/Local Folders. I did not copy the .msf files, and I did not copy the Junk folder. I have three mail accounts with a single global Inbox. And...this bug still happens. I don't see a button for reopening this bug. How do I do that?
(In reply to comment #19) > I don't see a button for reopening this bug. How do I do that? It isn't clear to me you should reopen the bug. The fix that is in place does the following: the 'spamActionXxx' prefs are set for the account and, when necessary, the folder is created, when the 'Move messages' option is checked and the changes are accepted. If you are in fact experiencing the problem at bug 351545, when you use the new software, you need to turn the Move messages option off, then back on. The fix really is only useful for the creation of new accounts, since even the older software could be worked around by explicitly setting the Junk folder. If neither of those user actions fixes your problem of junk not getting moved, then you have a different problem; see comment 6. (I'm not 100% percent sure that this bug is in fact a dupe, but Bob Lord's reports at this bug and at bug 351811 are consistent with that other bug's symptom.)
Mike, your suggestion worked! Thank you! You ROCK!
Flags: blocking-thunderbird2+
You need to log in before you can comment on or make changes to this bug.