Closed Bug 24715 Opened 24 years ago Closed 24 years ago

Shouldn't get error after sending mail or save as draft/template from Cyrus

Categories

(MailNews Core :: Networking, defect, P3)

Product:
MailNews Core
Component:
Networking
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: huang, Assigned: jefft)

Details

WinNT 2000-01-21-09-M13 commercial build:

Cannot send mail/message from Cyrus IMAP

1) Login to Cyrus IMAP mail account
2) Compose mail and send.
3) Actual Results: Got an error: The command did not succeed. The mail server
responded: Mailbox does not exist.

Expected Results: Should send msgs successfully without this error.

Addtinal Info: I tried on 4.7, I got an error from 4.7, too. 
But the msgs still send out and msgs had been received. 
The error from 4.7 is : The command did not succeed. The mail server responded:
Permission denied.
Change QA contact to me, Cc: Lisa.
QA Contact: lchiang → huang
Sorry. I don't know why it's so slow....
I got the send msg from 5.0 after the error msg, too. 
But it shouldn't get error after sending mail/message from Cyrus IMAP.
Updating this summary.
Summary: Cannot send mail/message from Cyrus IMAP → Shouldn't get error after sending mail/message from Cyrus IMAP
I got the same error when I trying to save as draft & save as template from the
compose window. Thought this might be the similar problem....
If after I define the Namespace on Cyrus Inbox from 4.7, and I won't get any 
error message when sending msgs from 4.7.
But 5.0 still get the "The command did not succeed. The mail server
responded: Mailbox does not exist" error....
Karen, I don't understand. don't we already have CYRUS bugs about this mailbox 
does not exist? Maybe I'm missing something but this sounds like dups of 22349 
or 19229


I don't think this is dup. bug of bug#19229 -- since bug#19229 only dealing with 
general subfolders. But this bug is concerning about the default subfolders.....
And, I am not sure whether it's dup of bug#22349, but I knew that there was 
bug#24667.

Feel free to mark as dup bugs of them since I am not quite sure whether they are 
dup bugs or not?
Summary: Shouldn't get error after sending mail/message from Cyrus IMAP → Shouldn't get error after sending mail or save as draft/template from Cyrus IMAP
Release Notes for M13

Actually, this problem not only occurred on Cyrus, it occurred on Netscape 
Messaging Server 4.1 server, too. Updating the summary to add Messaging server.
Summary: Shouldn't get error after sending mail or save as draft/template from Cyrus IMAP → Shouldn't get error after sending mail or save as draft/template from Cyrus & NMS IMAP
But, there was no problem for sending msg from messaging server 4.1.
Problem only occurred on save as draft/save as template for Messaging (NMS) 
server.

Jefft said he'd look at this for me. Jeff, I'm pretty sure this is a duplicate
of the FCC folder bug I just assigned to you for CYRUS servers.
Assignee: mscott → jefft
Status: NEW → ASSIGNED
Target Milestone: M14
I log bug#25146 for keep tracking on initiating draft/template problem for NMS 
IMAP server -- so I take out the "NMS IMAP" from this summary, and let this bug 
to specify on Cyrus only.
But, I don't know this bug should be dup of bug#22349 or bug#24667?
Jeff, you may go ahead to mark as duplicate if you want. Thanks.
Summary: Shouldn't get error after sending mail or save as draft/template from Cyrus & NMS IMAP → Shouldn't get error after sending mail or save as draft/template from Cyrus
Sounds like another downstream symptom of not having IMAP namespaces? WOuld like
to have this fixed for B1.

This bug strikes me as odd, because my first trial with mail on Moz was with M13

(Win95 OSR2.1+USB), and it was against two accounts -- one on an IMAP-UW server,

and another on a Cyrus 1.6.22 server.  It worked flawlessly for me.  In

addition, I used Cyrus 1.5.? with Messenger 4.6 (WinNT 4.0 Wks+SP4) in

production for months; saving sent, drafts, and templates to the IMAP server,

and never received the error in question.



I'm currently using Messenger 4.7 (Red Hat 6.0) against Cyrus 1.6.22 without

saving sent, drafts, or templates to the IMAP server, simply because I haven't

gotten around to it yet.  I'm something of a Cyrus nut, though not much of a

coder... so I'll be happy to help troubleshoot in any way I can; but first I

wonder if the configuration in question is saving sent, drafts, and templates to

the IMAP server, and also what the cyradm lam (listaclmailbox, I think) output

is for the folders in question.


I have a fix for bug 24667, bug 22349, bug 23588, & bug 24715. I'll check in 
once I got a review. To test you need to remove the following namespace entries 
for your Cyrus server:

user_pref("mail.server.server5.namespace.other_users", "");
user_pref("mail.server.server5.namespace.public", "");

and add/modify the following entry:

user_pref("mail.server.server5.namespace.personal", "Inbox.");

Unfortunately, we don't have UI for it now.

Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Jeff,
Should I need to correct the following line as well?
user_pref("mail.imap.server.buggy.mcom.com.namespace.personal", "Inbox.");
Yes.
Jeff, 

The message can be sent, but I still got the error dialog?
I also removed the following two lines as well, but still not useful.
Any else workaround?

user_pref("mail.imap.server.buggy.mcom.com.namespace.other_users", "");
user_pref("mail.imap.server.buggy.mcom.com.namespace.public", "");
What's dialog said?
The same error:
The command did not succeed. The mail server
responded: Mailbox does not exist.
And also after click "OK" from this error dialog, will back to compose window 
(compose window opened)...but after close the compose window and check the 
received msg...it's there. But cannot find the sent msgs from Sent folder.

I am using 02-03-10-M14 Windows mozilla build....
Fix is in this build?
Did you set your Sent, Drafts & Templates folder correctly in your Account 
Setups?
By the way, I logged bug#26439 for the Personal Namespace "Inbox." for the 
preference UI problem...
I used the existing profile from 4.7 and migrated to 5.0...
I check my 4.7 with the Sent folder initially. And it send without problem from 
4.7, msgs also store correctly in Sent folder.

I check the account setup from 5.0. It displayed the Sent folder correctly...
Is this migration problem that all the field display on Account setup but not 
bringing correct info from 4.7 to 5.0? Same as bug#26439?
Actually why don't you just added from account setup | Advance... pop up menu. I 
think it works although not pretty. Or add as the following in your pref.

user_pref("mail.server.server5.namespace.personal", "\"Inbox.\"");
I have removed the four lines (see above comments)and modified the "\"Inbox.\"" 
from prefs.js...I also change the personal namespace of account setup Advance 
dialog from "Inbox." to "\"Inbox.\"".....It is still not working.
I also tried to verify from the new profile, but I have no idea whether I need 
to remove & add the same thing from the new profile's prefs.js???...It seemed 
that the prefs.js of the new profile for Cyrus is not ready yet!! Can you tell 
me others' work around? Or tell how to workaroung from new profile? 
Yes. After talked to Jaff on the phone,
There was workaround, send msg can be implemented by using the work 
around...sounds like another bug for either account setup or migration...
I need to investigate this problem with Jeff and log another bug tomorrow....
I will verify the draft & template tomorrow, too.....
Used 02-04-10-M14 WinNT commercial build:
Passed by using new profile.
There were problems for migration & "default" draft/template folder problem for 
Cyrus.I Will investigate that & log bug later.....Marking as verified!!
Status: RESOLVED → VERIFIED
After investigation and logging a new bug, if applicable, pls put the new bug 
number into this bug report as a reference. Thanks.
Already logged Bug#27002 for IMAP Cyrus migration problems for default folders.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.