Closed Bug 505672 Opened 16 years ago Closed 16 years ago

"Send unsent messages" command doesn't work

Categories

(SeaMonkey :: MailNews: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0b2

People

(Reporter: wcdproject, Assigned: standard8)

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 whenever I queue a message in a POP3 Outbox folder (with CTRL+SHIFT+RETURN) and then try to use "send unsent messages" from the menu bar of from the context menu, SM simply sits there without doing nothing. The SMTP server correctly works, because if I set SM to go offline and again online, I'm asked to send the queued message and it is finally sent. Reproducible: Always Steps to Reproduce: 1. Create a new email account; 2. write a new message; 3. queue the message (CTRL+SHIFT+RETURN) so that it is displayed in the Outbox folder; 4. try to send the queued message by using the main menu or context menu "Send unsent messages" command. Actual Results: Seamonkey does nothing. No error message and no sending of the email that stays in the outbox folder. Expected Results: The queued message should be correctly sent. I can reproduce this bug with different type of account (POP3, News) and on several SM build before and after Beta 2.
Same behaviour occurring in nightly moz-central build:- Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090721 Lightning/1.0pre SeaMonkey/2.1a1pre ID:20090721001048
Flags: blocking1.9.2?
Flags: blocking1.9.2? → blocking-seamonkey2?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-seamonkey2.0b2?
Version: unspecified → Trunk
Keywords: regression
OS: Windows Vista → All
Hardware: x86 → All
> Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1.2pre) Gecko/20090721 SeaMonkey/2.0b2pre (1) Send Later Five next error in Error Console. > Error: [Exception... "'JavaScript component does not have a method named: > "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: > "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no] (2) Restart Mail&News, Cancel reply to dialog of "send or not main in outbox". Send unsent messages => Nothing happened. No error in Error Console. (3) Restart Mail&News, OK reply to dialog of "send or not main in outbox". => Mail was sent normlly.
Attached patch The fixSplinter Review
I wondered if it was me that broke this - Small typo fix - msgSendlater versus msgSendLater. The TB version doesn't have the case error, but I'll sync the capitalisation in a patch on a later bug.
Assignee: nobody → bugzilla
Status: NEW → ASSIGNED
Attachment #392491 - Flags: superreview?(neil)
Attachment #392491 - Flags: review?(neil)
Attachment #392491 - Flags: superreview?(neil)
Attachment #392491 - Flags: superreview+
Attachment #392491 - Flags: review?(neil)
Attachment #392491 - Flags: review+
Comment on attachment 392491 [details] [diff] [review] The fix This certainly fixes a bug, although I don't think it relates to the error given in this bug's description.
(In reply to comment #4) > (From update of attachment 392491 [details] [diff] [review]) > This certainly fixes a bug, although I don't think it relates to the error > given in this bug's description. Maybe I should have explained a bit more. On a debug build I see: An error occurred executing the cmd_sendUnsentMsgs command [Exception... "'[JavaScript Error: "msgSendLater is not defined" {file: "chrome://messenger/content/mail3PaneWindowCommands.js" line: 861}]' when calling method: [nsIController::isCommandEnabled]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: chrome://global/content/globalOverlay.js :: goDoCommand :: line 80" data: yes] In globalOverlay.js goDoCommand first calls isCommandEnabled and then calls doCommand... as the function IsSendUnsentMsgsEnabled throws an exception in this case, doCommand doesn't get a chance to run.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: blocking-seamonkey2?
Flags: blocking-seamonkey2.0b2?
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0b2
Workaround to send unsent messages is to close the mail facade and reopen it. When reopened, SM will ask to send unsent messages in popup and perform the action after pressing "OK" button Tested Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: