96932 - UW IMAP : Sending mail -> SUBSCRIBE failed for mailbox Sent

Status: RESOLVED DUPLICATE of bug 90064

(MailNews Core :: Networking: IMAP, defect)

Description

[Alex Stewart]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010808
BuildID:    2001080814

I have my mail account configured for an IMAP server, with the (default) setting
to store copies of sent mail in the "Sent" folder on my IMAP server (which I was
happy to see was the default, btw, very convenient)

A couple of times now when sending mail, after sending the message off to the
SMTP server, it has failed in the process of saving a copy to the "Sent" folder
with the following message:

  The current command did not succeed.  The mail server responded: SUBSCRIBE
failed: Already subscribed to mailbox Sent

After displaying this message, the send process gets perpetually stuck  on
"Copying message to Sent folder...", and never completes.  The mail is never
saved in the Sent folder.

This appears to happen when I attempt to send a message without having
previously (in the Mozilla session) logged into my IMAP server.  Mozilla sends
the message, starts to save it in the "Sent" folder, realizes it isn't logged
in, asks me for my IMAP password, logs in, and then tries to subscribe to the
already-subscribed "Sent" folder, and falls down.


Reproducible: Sometimes
Steps to Reproduce:
1. Configure Mozilla to save sent mail in an IMAP folder.  Do not configure it
to remember the IMAP password.
2. Start a fresh instance of Mozilla
3. Send a mail message
4. Enter IMAP password when prompted.

Actual Results:  (as detailed in "Description")

Expected Results:  Save the message in the "Sent" folder and close the mail
composition window.

Using UW IMAP server v 2000.281 with stunnel 3.4a2 SSL wrapper.  Mozilla is
configured for IMAP over SSL.

Comment 1

[Graeme Humphries]

I am experiencing the same bug on Windows 0.9.4 release. 

Comment 2

[Derek R. Price]

I experience this same problem using Mozilla 0.9.3, but every time, even when
logged into the IMAP server already.  I can reproduce the subscribe error
message, without the failed copy and the process dialog that won't go away, by
opening the subscribe dialog and attempting to subscribe to any folder.

My IMAP server reports the following version:  IMAP4rev1 v11.237

Comment 3

[Karen Huang]

UW IMAP server v 2000.281 -> Adding interop on the keywords.
I couldn't reproduce this problem by sending the mail or subscribe folders from 
our internal UW IMAP account, I used UW IMAP 12.25.....

Comment 4

[Karen Huang]

Can you try on the latest build? There was bug 102816 logged recently, but 
I still cannot reproduce both scenarios.....

Comment 5

[Derek R. Price]

I couldn't duplicate this with last night's build due to a bug that was
preventing me from sending at all.  I assume that the failed send stopped the
chain of events that led to the copy to sent-mail because the mail did not
appear in my sent-mail box.  The bug that prevented the send claimed that it
couldn't connect to the SMTP server (localhost:21103 on my machine - an SSH
tunnel).  The tunnel was still up because I could switch back to the 0.9.3 build
and send mail.

Interestingly enough, I had switched to using a Sent mailbox in the local
mailbox as a workaround since just after I first annotated this bug report. 
After using the 0.9.4+ build to switch it back to the "sent-mail" box on my IMAP
server and failing the test send, the 0.9.3 build began copying to the
"sent-mail" box properly.  Could this point to a problem with the import of
config data from Netscape?  That's where my original config came from.  I just
double-checked and 0.9.3 can set up the "sent-mail" box properly too.

I also double checked subscribes in 0.9.3 after the sends began working again
and they still cause the "The current command did not succeed.  The mail server
responded: SUBSCRIBE failed: Can't create subscription database." message.

Comment 6

[Derek R. Price]

Guess it wasn't just the import causing the problem.  I'm still experiencing
this problem intermittantly.  Last time I simply quit Mozilla and restarted and
it went away.

Comment 7

[Keyser Sose]

Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:

1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again

If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.

Comment 8

[Christopher Hoess (gone)]

reopening

Comment 9

[steve farrell]

Still experiencing this (perhaps even more) with 0.9.6.  It used to only happen
when sending a link (File/Send Link...), but not it seems to happen even when
using compose.

Comment 10

[steve farrell]

*** Bug 105282 has been marked as a duplicate of this bug. ***

Comment 11

[Felix Andrews]

The error [
  The current command did not succeed.
  The mail server responded: SUBSCRIBE failed:
  Already subscribed to mailbox Sent.
]
occurs when I send a message without first loading the folder list. If you go
into the main (pane-based) mail window, then send a message, it is fine. Once
the first message's copy to "Sent" fails, the next message succeeds. (Reset by
quitting and reopening Mozilla).

I am using Mozilla 0.9.6 on Redhat 7.1 and Moz 0.9.6 on MacOS 9.1.
My IMAP server identifies itself as "IMAP4rev1 2000.287rh" (comes with Redhat 7.1).

Comment 12

[Peter Janes]

Sounds like bug 90064, where Christopher Blizzard has a reproducible case for
the subscription failing that's very similar to the reporter's.

Comment 13

[Alex Stewart]

Ah, good eye..  Speaking as the original submitter of this bug, yes, this does
appear to be an exact duplicate of bug 90064, where it appears Chris has also
managed to identify the specific code path responsible for this problem.

(I'm not gonna mark this as a duplicate myself because I'm not familiar enough
with the procedures for this bugzilla system and whether other things should be
done as well, but if somebody more familiar with things wants to do that it's
fine by me)

Comment 14

[Jan Carpenter]

*** Bug 123441 has been marked as a duplicate of this bug. ***

Comment 15

[Andy Lyttle]

Annoying as hell, and yes it's a dupe. :-)

Comment 16

[Gregg Meehan]

*** This bug has been marked as a duplicate of 90064 ***