353622 - Junk mail copied while TB automatically define it as a junk

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[pazi]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060915 Firefox/1.5.0.7 (tete009 G7 SSE2)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060915 Firefox/1.5.0.7 (tete009 G7 SSE2)

In my settings, TB would move the junk mail to a certain folder named "Autotrash". But if the mail is defined by TB automatically, it will be moved to "Autotrash" folder twice. Two identical emails will be in that folder. I receive only one email indeed. However everything is fine when I mark the email as junk manually.

Reproducible: Always

Steps to Reproduce:
1.create a email account based on IMAP protocol.
2.open the junk control
3.

Actual Results:  
when a message that would be marked junk by TB arrives, two identical emails would appear in the junk folder.

Expected Results:  
If a message is marked as junk manually, only itself would be moved to junk folder.

Comment 1

[pazi]

Sorry, I forgot to give the version of my thunderbird. 
Thunderbird version 2 beta 1 (20060920)
Actually the problem occurs in every TB 2.0 beta version, while it is fine in TB 1.5.0.*

Comment 2

[u63580]

This is WFM in version 2 beta 1 (20060920), on IMAP using the default junk-mail folder name ("Junk").

Comment 3

[pazi]

(In reply to comment #2)
> This is WFM in version 2 beta 1 (20060920), on IMAP using the default junk-mail
> folder name ("Junk").
> 
I tried, but no use. The junk mail would not be moved to this folder even after I created the folder manually. 

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does this still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.17)

Comment 5

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.