Closed Bug 378020 Opened 18 years ago Closed 18 years ago

Upgrading from 1.5.0.8 to 2.0.0.0 makes IMAP email deletion impossible for certain IMAP servers

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 377900

People

(Reporter: boyerspam, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Build Identifier: version 2.0.0.0 (20070326) I use Tuffmail.com for my IMAP email (really awesome IMAP service) and upon upgrading to TB 2.0.0.0, when I browse the message-list pane the delete button on the toolbar is greyed out; also the delete key on the keyboard does nothing (no error box, no typical "i deleted this IMAP-style" strikethrough on an individual email). Connecting to an alternate IMAP service (work) seems to work perfectly fine. Also, moving messages between folders on the tuffmail account generates the proper strikethrough-deleted copies in the source folder, and the compact button will clean those up, but I still can't use the delete key to 'undelete'. Reproducible: Always Steps to Reproduce: 1. The delete button is just always greyed out in the interface for Tuffmail IMAP accounts, but it didn't used to be. Actual Results: Deleting messages is pretty much impossible, unless I resort to the non-IMAP-way of deleting and _manually_ drag-n-dropping messages into the Trash folder. Expected Results: If the button were available, the delete key would let me mark messages as IMAP-deleted. I am using an upgraded-profile as a result of just upgrading TB to 2.0.0.0 from 1.5.0.8. I have not tried renaming my $HOME/.thunderbird/ folder and starting fresh yet.
Sounds DUP of Bug 377900. See Bug 377900 and get NSPR log for imap:5, and compare ACL related responses in your log and one in Bug 377900.
Blocks: 378635
Status: UNCONFIRMED → NEW
Ever confirmed: true
I've landed fixes for bug 377900 on the trunk and 2.0 branch, so a 2.0 nightly build from tomorrow should have the fix. If it works with tomorrow's build, then this is a dup of bug 377900.
If this does not work in tomorrow's 2.0 nightly build, please re-open this.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.