245879 - Unable to save copy of sent message to inbox on IMAP account

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: SMTP, defect)

Description

[Carl D. Zukas, Jr.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040607
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040607

Setting "Place a copy in:" to INBOX in "Mail & Newsgroup Accout Settings -
Copies and Folders" does not save a copy to the INBOX.  The dialog box that
says: "Copying message to INBOX folder..." stays on the screen for an as long as
I let it.  Setting this to other folders works fine.  This is happening with my
work account.  It looks like they are using qmail as the mail server.  A
different IMAP account that I have seems to work fine with this setting.

Reproducible: Always
Steps to Reproduce:
1. Set "Place a copy in:" to INBOX in "Mail & Newsgroup Accout Settings - Copies
and Folders"
2. Compose and send an email from that account

Actual Results:  
Application will send the email but the dialog box and compose window do not
close until the cancel button is hit on the "Copying message to INBOX folder..."
dialog box.


Expected Results:  
This dialog box should have displayed and then dispeared automatically after the
message had been saved to the INBOX.

This worked in earlier version of Mozilla (pre 1.7).

Comment 1

[Hannes]

Confirmed!
It worked fine on 1.6 but 1.7 is having problems.

The entry in prefs.js is exactly the same as it was in 1.6:

user_pref("mail.identity.id1.fcc_folder",
"imap://[e-mail]/INBOX");

which looks good.

Also the way it is presented in The account manager is wrong after saving. It
does not say "Inbox on USW" But "USW"

BTW I am Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Gecko/20040910

The Mailserver is COURIER.

PS.: I think that this Bug is not correctly filed under Networking: SMTP

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.