310841 - imap expunge called on connect by default

Status: RESOLVED INVALID

(Thunderbird :: General, defect)

Description

[Jørgen H]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 1.0.7

Your mailclient called expunge with default installation and configuration of 
a new imap account just after connecting to the imapserver. I suggest that 
expunge like this is never called without the users knowledge.

Reproducible: Didn't try

Steps to Reproduce:
1. Install thunderbird
2. Create new imap account by filling in mailserver and username
3. Connect to mailserver

Actual Results:  
everything worked fine except for the expunge command being called

Expected Results:  
that expunge was not called

Comment 1

[Ray Booysen]

Reporter, how are you able to file this bug without experiencing the problem
yourself.  How are you sure that expunge is called?

Comment 2

[Jørgen H]

15:32 PDT -------
>Reporter, how are you able to file this bug without experiencing the 
>problem
yourself.  How are you sure that expunge is called?

I did in fact experience it myself.
I am the author of jimap and I noticed that mozilla called expunge at connect 
when I was testing Thunderbird with my imap server. As I had around 1000 
emails marked as deleted I thought it was a good idea to ask the user first 
before expunging by default.

Note that the reason for my testing with Thunderbird was that it was not 
working with jimap (I fixed jimap, it is nothing wrong with Thunderbird). The 
expunge command could have been triggered by some code in Thunderbird that 
didn’t understand the imap server. All I know is that I never clicked the 
expunge-button, nor did I explicitly tell Thunderbird to expunge my email in 
the settings. 

Cheers,
Joergen

Comment 3

[Ray Booysen]

Could you reproduce the bug if you tried on a test account and attached a trace
from jimap?

Comment 4

[David :Bienvenu]

if you set the imap delete model to be imap delete, then we won't issue
expunges, because implicit in using the imap delete model is that you want to
manage your expunged messages (in the imap delete model, we show you your
deleted messages with a big red x). If you use the trash folder model, or the
delete immediately model, we manage expunging your messages for you.

So it requires a little user sophistication (going into account settings and
configuring your delete model), but most users want us to automatically expunge
and complain when we don't expunge on every delete, etc...