Closed
Bug 263879
Opened 20 years ago
Closed 17 years ago
Cannot select Inbox of another IMAP account as folder to move mail from a filter
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: brandtwr-j, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Thunderbird version 0.8 (20040913) With two IMAP accounts, Thunderbird's mail filters will not allow selecting the Inbox of the other account as the folder for moving mail to. It complains that you need to select a folder under Inbox. Reproducible: Always Steps to Reproduce: 1. Setup two IMAP email accounts (one is an MS Exchange account) 2. Build a filter to move mail from one sender out of the MS Exchange Inbox to the Inbox on the other IMAP server. 3. Actual Results: Inbox cannot be selected. / Dialog box will produce an error and not allow a submit. Expected Results: Allowed you to select the Inbox.
Comment 1•19 years ago
|
||
I also have this problem. Running Cyrus 2.1 as the IMAP server, and the user in question (foo, for the sake of this mail) is subscribed to their own folders (i.e. user.foo.*). The user is also subscribed to another users folders (bar, for the sake of this mail). User "bar" has several subfolders, and is just a shared account - set up under the user hierarchy as I need sieve functionality of mail sent to it. In Thunderbird, when the user sends mail from the main identity, the message is stored in "user.foo.Sent", and all works as expected. However, when mail is sent from the second configured identity, it is supposed to be copied to "user.bar". This isn't happening - thunderbird just hangs at this point trying to copy the sent message to the configured folder. A protocol trace shows that it's doing completely the wrong thing:- 16 OK Completed 17 list "" "INBOX^^user^bar" 17 OK Completed (0.000 secs 1 calls) 18 create "INBOX^^user^bar" 18 NO Invalid mailbox name 19 IDLE + idling Obviously the reference to "INBOX" in the mailbox path it's using is completely wrong.
Comment 2•19 years ago
|
||
Mike, what version of Thunderbird are you using? I thought this was fixed a long time ago, in time for thunderbird 1.0. Also, your problem is completely different from the originally reported problem. Your problem looks a lot like bug 248080
Comment 3•19 years ago
|
||
I encountered this problem when we rolled out new desktops, and switched the user in question from Netscape 7 (where it worked as we wanted) to Thunderbird 1.0.2. I haven't yet retested with newer versions of Thunderbird. The user in question has multiple sender identities set up, and one of the identities is set to store send mail in the inbox of another (fake) users account on the IMAP server, so several people can have access to the same mailboxes. I've not been able to make it correctly store the sent message anywhere other that under the real user's folders. Another small point to not - the UI message is wrong when the problem crops up. TB pops a dialog that tells the user the message has not been sent, when in fact is has already been sent, but the copy of the sent message has failed.
Comment 4•19 years ago
|
||
(In reply to comment #0) > Build Identifier: Thunderbird version 0.8 (20040913) > > With two IMAP accounts, Thunderbird's mail filters will not allow selecting the > Inbox of the other account as the folder for moving mail to. It complains that > you need to select a folder under Inbox. > > Reproducible: Always > Steps to Reproduce: > 1. Setup two IMAP email accounts (one is an MS Exchange account) Bill, does this happen with Exchange? WFM with two accounts on same (non-exchange) server and version 3 alpha 1 (20060418)
Comment 5•19 years ago
|
||
Bill, your response would help move the bug along.
Updated•18 years ago
|
QA Contact: front-end
Comment 6•17 years ago
|
||
=> incomplete - perhaps bill is gone
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•