Closed
Bug 486604
Opened 16 years ago
Closed 16 years ago
Shredder not deleteing from trash even though "Empty Trash" was set
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: cory, Unassigned)
References
(Depends on 1 open bug)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032711 Ubuntu/8.10 (intrepid) Firefox/3.0.8 (.NET CLR 3.5.30729) Mnenhy/0.7.6.666
Build Identifier: Shredder 3.0b3pre
I have the "Empty Trash on Exit" set on an IMAP account. This IMAP server does folders-in-folders and there were two Trash folders - one a child of the Inbox folder, created when the account was set up and first accessed through SquirrelMail, and one a sibling of the Inbox made when I added the account to my Thunderbird/Shredder profile.
Deleted email was going to the child-Trash and was not being deleted when Shredder was exiting. Maybe Shredder was checking the sibling-Trash to delete on exit?
Reproducible: Always
Steps to Reproduce:
1. Get an email account on a system using squirrel mail & postfix (imap server type unknown) that provides a trash folders as a child of the Inbox
2. Add this account to Shredder so Shredder creates it's own Trash folder as a sibling of the Inbox (as seen in Thunderbird's folders pane)
3. Set "Empty Trash on Exit" and go through several normal days of deleting emails from the Inbox, exiting and restarting Shredder.
4. Deleted emails get moved to the child-Trash folder but never get deleted upon exit.
5. Manually move trash to the sibling-Trash folder and it will get deleted.
Actual Results:
Deleted email will get moved to the child-Trash folder but never get deleted upon exit. If you move the unexpunged trash to the sibling-Trash folder, it will get deleted on exit.
Expected Results:
Trash should be deleted, regardless of where the Trash folder is.
Comment 1•16 years ago
|
||
If both Trash and Inbox/Trash exists, problem of Bug 479226 occurs.
"Moved to Inbox/Trash instead of Trash" part is DUP of Bug 479226.
Because Tb misuses Inbox/Trash as trash folder due to the bug, and Tb issues expunge to Inbox/Trash(child-Trash) instead of Trash(sibling-Trash) upon exit.
Unable to reproduce phenomena you explained, except "delete operation moved mail to Inbox/Trash,child-Trash instead of Trash,sibling-Trash".
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4pre) Gecko/20090331 Shredder/3.0b3pre
- "Move to Trash" model is used.
- Tb's trash setting is root level Trash(sibling-Trash)
- Trash already exists. After creation of Inbox/Trash, Tb is restarted.
- Tested with Gmail IMAP (namespace="")
Deleted mail was moved to Inbox/Trash(child-Trash) upon delete of mails.
Tb issued store \Deleted to Inbox/Trash.
When move to Trash(sibling-Trash), Tb didn't issue store \Deleted to Trash.
Upon termination, Tb issued store \Delete & expunge to Inbox/Trash only (child-Trash).
Which build do you use?
What is set in following entry in prefs.js? No entry is defined?
> user_pref("mail.server.serverX.trash_folder_name", "Trash");
Depends on IMAP server? namespace of Inbox/(or Inbox.) is used by server?
Get IMAP log, and check IMAP level flow first, please.
Comment 2•16 years ago
|
||
FYI.
Bug 484445 exists. It may affect Tb's behavior on expunge for non-trash folder.
Comment 3•16 years ago
|
||
Additional observation.
When "Empty Trash" in context menu of Trash (sibling-Trash) was executed, Tb trunk deleted mail in Inbox/Trash (child-Trash), and didn't delete mail in Trash (sibling-Trash).
I believe it's also a phenomenon by Bug 479226.
Comment 4•16 years ago
|
||
Cory the way to get imap logs is described at https://wiki.mozilla.org/MailNews:Logging.
Comment 5•16 years ago
|
||
There is Bug 471115. If SSL is used, Tb currently closes socket immediately without logout command when receives OK response to expunge command by "Empty on Exit". It may produce "connection error during expunge process" at IMAP server. This is possibly the reason why child-Trash was not expunged by shutdown of Tb in your case.
Updated•16 years ago
|
Comment 6•16 years ago
|
||
Cory is your situation improved with the landing of bug 484445 (using 2009-04-04 or newer build)?
Comment 7•16 years ago
|
||
Cory, We'd very much like to address the problem with your assistance. For now, without more feedback this is incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•