Bugzilla

TB is creating the folder called Junk. It thinks it needs it since it's not respecting that the existing folder  called "spam" on your server is marked as a special ```\Junk``` folder. I think the bug that Magnus above worked on causes "spam" to get shown as "Junk" on TB so you get two Junk folders.

Here's what you can do to work-around the problem while I debug the root problem:

1. Delete the extra Junk folder (like you always have been doing). Empty it from Trash (optionally).
2. Go into Junk Settings for your account.
3. Enable the "Move new junk messages to" checkbox so you can adjust the setting below it, i.e., un-gray them.
4. Choose radio button "Other:" and set it to "Junk on <your account>"
5. Click "Global Junk Preferences..."
6. Uncheck "When messages are marked as junk". I'm not 100% sure this is needed but I think it is.
7. Restart TB and see if you only see one Junk folder.

I can't figure why your log is coming out empty. But I can duplicate the problem here so log probably not really needed, but thanks for trying.

TB is creating the folder called Junk. It thinks it needs it since it's not respecting that the existing folder  called "spam" on your server is marked as a special ```\Junk``` folder. I think the bug that Magnus above worked on causes "spam" to get shown as "Junk" on TB so you get two Junk folders.

Here's what you can do to work-around the problem while I debug the root problem:

1. Delete the extra Junk folder (like you always have been doing). Empty it from Trash (optionally).
2. Go into Junk Settings for your account.
3. Enable the "Move new junk messages to" checkbox so you can adjust the setting below it, i.e., un-gray them.
4. Choose radio button "Other:" and set it to "Junk on <your account>"
5. **NOT NEEDED:** Click "Global Junk Preferences..." 
6.  **NOT NEEDED:** Uncheck "When messages are marked as junk". I'm not 100% sure this is needed but I think it is.
7. Restart TB and see if you only see one Junk folder.

I can't figure why your log is coming out empty. But I can duplicate the problem here so log probably not really needed, but thanks for trying.