User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 Not wanting to look at each Junk folder under each of my 5 mail accounts, I created one Junk folder under Local Folders and set up each account to move junk mail to Local Folders/Junk. Although the mail is marked as junk, it does not get moved. Reproducible: Always Steps to Reproduce: 1. 2. 3.

Is this incoming junk mail or old junk mail? I believe u have to manual move junk mail that isn't caught on download.

It's new mail. Just now I got the latest messages. 18 were marked as junk, 17 were moved to the Local Folders/Junk, one was left in the Inbox. It's not consistant, I'm still trying to find a pattern.

Another example, I have a message in the Inbox, marked as Junk, the log says the file was moved to Local Folders/Junk. but it wasn't. The message was not in the Junk folder, Just the Inbox. I GZIP'd/TAR'd the entire directory, but it is over 5 meg. Anybody interested in the file, I could "split" it into smaller pieces. There seems to be a 300KB limit on posting attachments.

Mandrake 8.2, Moz 1.3b. In desperation, I changed the permissions on all mail files to world: chmod 777 -R * Now Moz moves newly identified junk automatically to the junk folder. It therefore appears to be a file permissions problem, but which files exactly I cannot tell.

See 196732 This appears to be a file permissions problem. If I change the permissions on all mail files to world, then it works.

Without changing permissions, it works sometimes. It's just not consistant. Prior to changing permissions, did any files get moved to the junk folder?

Prior to changing permissions, nothing ever moved. The log file said it did, but it didn't really. That lead me to try changing the permissions.

I turned off junk mail controls for the one account having the problem, exited out of Mozilla, came back in, re-enabled junk mail controls, set up to send to the folder again - and it worked! I have since upgraded to the 1.3 release - and it is still working!

=>WorksForMe, based on reporter's comment 8; but see also bug 196732.