Closed Bug 23637 Opened 25 years ago Closed 24 years ago

Saving mails as draft or template with no draft/template folder specified generates two error messages

Categories

(MailNews Core :: Composition, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: bugzilla, Assigned: bugzilla)

Details

I created a new account and didn't specify my draft or template folder.
If I then compose a new mail and select "Save as (Draft)" or "Save as
(Template)" I'm getting two errors saying that "Unable so save your
message......"

Build 2000011008
QA Contact: lchiang → pmock
There is another bug report filed to have a default draft/template folder.

Once that is fixed, another way to get this problem may be to delete the draft
and template folders and then try to save a draft.
Status: NEW → ASSIGNED
Target Milestone: M14
Adding myself and sspitzer to the cc list because this may happen easily in
migration of (IMAP) account where user has never used Drafts or Templates and so
there is no drafts/templates folder upon migration (although the prefs for
storage path are indeed migrated).  When user tries to use drafts/templates in
5.0, the folders are not currently created on the fly, and the error message is
not real clear to user.
*** Bug 25146 has been marked as a duplicate of this bug. ***
There are really two issues in this bug, one suggested by the original
description and one (implied) by lisa's suggested testcase of removing the
special folders before saving draft/template.

I kind of piggybacked my issue on this (creating the special folders on the
fly). Let me know if I should separate them or just reword summary or whatever
you suggest.
Summary of issue:  need to create folders on the fly if not there for special 
folder prefs (Drafts in this case).

Decision would apply to other special folders.
I'm sorry the last comment was more leaning towards bug #25146.  
For this bug, when user saves Draft or Template without a folder specified in 
pref (outside cases), we need to make any error message we decide to display 
clearer and/or go ahead and set to default and file the draft/template.
Gang, are we going to be able to make drafts/templates work for beta1, or should
we just push them off to beta2 now?
I would rather say B2 but keept what is already working. rhp, jefft, any 
comment?
I thought drafts were working...this is just a multiple error bug...pretty 
minor I would say.

- rhp
that's right, we made good improvement on draft recently. But we still have bugs 
and therefore I would rather say draft/template are low priority for B1 as I 
have already too much to do. That why I said draft/template for B2. That doesn't 
mean no draft/template support for B1 but just no extra work on it for B1. We 
can also say the the current support of draft/template is enough good for B1.
I don't see anymore two errors. Therefore I mark it as works for me
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Have we solved the problem of saving Drafts/Templates with no default
Drafts/Stationery folder problem setting up first? If the Drafts/Templates
folder does not exist at the time of the saving we should prompt user for
setting up such folders. If we failed to save Draft/Template and no error
message then that's a problem. New account set up should also set the default
Drafts/Stationery folder. For Pop3 we should create the Drafts/Stationery folder
as by default. For Imap, we should create the Drafts/Stationery folder lazily
when user does the save.
Jeff, this issue is not solved yet. Do we have another bug number for it? if no 
we should file a new bug.
There was Bug#25146 logged. Please refer above issue to bug#25146...
Verified as works for me on win32, linux, and macos using the following builds:
 win32 commercial seamonkey build 2000-091312-m18 installed on P500 Win98
 linux commercial seamonkey build 2000-091408-m18 installed on P200 RedHat 6.2
 macos commercial seamonkey build 2000-091312-m18 installed on G3/400 OS 9.04

Template and Draft folder are created on the fly for IMAP.

Found another corner case ... when you remove the destination from the prefs.js,
you receive a similar message.  I will log a separate bug b/c by default, we
automately assign a default.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.