232810 - Send Unsent dialog could show what it proposes to send, offer to not appear again

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Frank Burleigh]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040131

Mail now shows, at start, a dialog asking whether to send unsent messages.  I
think the dialog is a good idea but could be improved in these ways:

1. show me the messages that are unsent.  from my point of view, i have no
unsent messages, but it has its own definition.  i use my Drafts folder to hold
mail i'm working on; i send them when i'm ready.
2. it presents in the upper left of my large screen, far from my normal attention
3. it might be nice to include a checkbox "don't show this again."


Reproducible: Always
Steps to Reproduce:

Comment 1

[Felix Miata]

I open & close mailnews several times a day, while items in unsent for me are
like the reporter's, liable to remain for days or weeks at a time. Another
option would simply a checkbox in mail server prefs whether to remind at startup.

Comment 2

[David :Bienvenu]

Have you looked in your local folders | Unsent messages folder? It's possible
you do have unsent message(s)...

Comment 3

[Frank Burleigh]

Hey.  I have a "Drafts" folder (on Exchange which I access via imap).  I've
assumed this is what Moz wants to tackle.  Thing is, I don't want it too--or I
want to know what Moz thinks is unsent so I can choose.  Some mail is complex to
write, so I leave them in Drafts until I'm done, when I open then send them.

It could be I have other unsent items for newsgroups (I guess they'd sit in a
local folder).  I had a long newsgroup post a few days ago when Moz crashed, I
assumed it was gone but maybe there's more saving than I think.  My point here
is that, without searching them out manually, I don't know what's there.  So if
this new dialog showed me the accounts/folders with unsent--or even better, let
me see the mail/news posts it sees as unsent--that would be a great help.

Comment 4

[David :Bienvenu]

Frank, you might be making it more complicated than it is - there is only one
Unsent Messages folder for your whole profile - it's always in Local Folders |
Unsent Messages and we don't let you choose (at least through the UI). I could
put that information in the dialog, but it would always say the same thing.

This has nothing to do with Drafts, though I can see why you might think that.

Comment 5

[Frank Burleigh]

If Drafts isn't involved then I think you are right.  Should I close this or
leave it for consideration of the UI points (don't show again, don't show in the
upper left corner of really big displays ;-)?

Comment 6

[David :Bienvenu]

let's leave it open for the UI points. I may not have any control over where the
window appears -  the toolkit decides that. If it were up to me, it would be in
the center of the screen. But we have other requests to optionally turn off this
warning, from people who use the Unsent Messages as a draft folder, from what I
can tell.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420