269675 - Changing "Sent Mail" folder to INBOX creates INBOX subfolder, loses sent mail

Status: RESOLVED EXPIRED

(MailNews Core :: Backend, defect)

Description

[phil]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5

Because most of the mail I send is part of a thread, I constantly find myself
moving sent mail from "Sent" back to the INBOX, so I can see the whole thread
instead of just one side of it.  Because both folders are on a remote IMAP
server, this is slow and annoying.

I changed the "save a copy" setting to the INBOX folder itself, and now no sent
mail is saved anywhere.  Yay data loss!

Changing it back to "Sent" starts keeping mail again.


Reproducible: Always
Steps to Reproduce:
1. In "Copies & Folders" change the folder to INBOX (not one of its subfolders).
2. Send some mail.
3. Try to find the sent copy.  Fail.  Weep for lost data.

Actual Results:  
The little progress dialog that pops up during mail transmission finishes with
"saving a copy in the INBOX folder," so the change is taking effect and it's
getting the name right.  The actual message is nowhere to be found.


Expected Results:  
Kept a copy!  Somewhere!  Preferably where I asked it to, but failing that,
anywhere else.  :-)


I am not the IMAP administrator (and know nothing about IMAP myself), but I can
ask for logs or whatnot if you tell me precisely what to ask for.

Comment 1

[phil]

Oh, wow.  Even better:

After changing back to the normal "Sent" folder, and happening to restart my
computer for unrelated reasons, I reconnect to the IMAP server and the folder
tree now looks like this:

-- Inbox
 |--INBOX
 |--Sent
 |....

Even though I had selected "choose this folder" in the Copies & Folders window,
it's created a /new/ subfolder named INBOX, instead of storing mail into the
ctual inbox.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.