I tested Send Later today (7_13 Linux build). I found that I had to "Send Unsent Messages" twice before my Unsent messages were sent. Then it worked, but, thereafter, it failed to continue to work for that session: when I had unsent messages in my outbox later that session and I selected "Send Unsent Messages" from the menu, I didn't see "sending [subject]" in the console window, and the X-Mozilla-Status of the messages in the inbox remained at 0801. Test case: 1. Start apprunner -mail. 2. Click New Msg. Compose a new mail message. 3. Select "Send Message Later" (menu). 4. Select "Send Unsent Messages" 5. Watch console window; check X-Mozilla-Statuses in Outbox. No success. 6. Select "Send Unsent Messages" 7. Watch console window; check X-Mozilla-Statuses in Outbox. Success. 8. Repeat steps 2-5. Keep repeating steps 4-5 until you get bored. I'm leaving this as [pp] for now because I'm running through a Linux functional test and haven't tested this on other platforms yet.

Using 19990712 on win98 and win95 Send Unsent Messages doesn work. I can't get them to send no matter how many times I try. Mac also doesn't send unsent messages. Removing the [PP], changing to all

(Note: I had to create an Outbox first...I thought that might be required in the same way that a Sent folder currently is for sent copies to work.)

Also note: For windows and Mac. If you Send Later a message, then click Send Unsent Messages (the messages are not sent as stated in this bug), then you close Messenger, and Browser apprunner never closes. You have to close it manually.

More update: I'm finding on my win32 systems that a single pop account does send later OK. It's my multiple accounts prefs50.js that can't send unsent messages. I have to check Mac and linux to see it this is true for those platforms too.

Going to write up a new bug for the apprunner console window not closing when sending later (see my comments 7/13/99 14:33).

(I had multiple accounts set up in my prefs when it worked as reported above: POP, IMAP, IMAP, NNTP.)

I think I know whats going on here....we are hiding a window...not closing it because I think we are listening for a different event....so there is a window hanging around. - rhp

fyi. Ninoschka asked me to post my results. On the PPC Commercial Seamonkey build 1999-07-13-09, I see the following behavior: a) On a single profile, the send later command works but in order to see the message in the Unsent Message folder, you must quit and restart apprunner. Closing and openning the Messenge window does not work around problem. b) On a single profile, the send unsent message command works only if the message displays in Unsent Message folder. If there is no "visible" message in this folder, the send unsend message command will fail. If there is a "visible" message, then that message get sent. c) On a multiple profile, the send later command works but in order to see the message in the Unsent Message folder, you must quit and restart apprunner. Closing and openning the Messenge window does not work around problem. d) On a multiple profile, the send unsent message command fails in all cases. I can not get it to work. Note: Due to performance problems on the Mac, it is very difficult and painful to even do simple selection or open folder operations.

The separate bug number for apprunner console not closing is 9791. rhp is the comment above for the console not closing bug? This bug is for Send Unsent Messages not working when you have messages in your Unsent Messages folder of your 1st pop account, you have multiple accounts, and you do nothing else but select Send Unsent Messages from the File menu. (Note: my multiple accounts included 1 pop, 1 imap, 1 news.)

Yes, my comment was about the console not closing...bascially, the app isn't exiting. - rhp

Linux (1999-07-14-16 m8) I try to do Send Later 5 times, none works in multiple profiles ( 1 pop, 1 imap, 1 news). This includes quit and restart apprunner.

Linux (1999-07-14-16 m8) On a single pop account, Send Message Later works without the need to exit and re-launch apprunner.

Jeff, Can you take a look at this when you have time. What it looks like to me is that the index isn't being build correctly on some copy operations. What I did to see this was: - start messenger - compose a message - select send later - select send unsent messages Don't display any of the folders. Just do the above steps. I was seeing messages that looked like what I get when the indexes aren't correct on a folder. Let me know what you see. - rhp

Jeff, Can you take a look at this when you have time. What it looks like to me is that the index isn't being build correctly on some copy operations. What I did to see this was: - start messenger - compose a message - select send later - select send unsent messages Don't display any of the folders. Just do the above steps. I was seeing messages that looked like what I get when the indexes aren't correct on a folder. Let me know what you see. - rhp

Jeff, Can you take a look at this when you have time. What it looks like to me is that the index isn't being build correctly on some copy operations. What I did to see this was: - start messenger - compose a message - select send later - select send unsent messages Don't display any of the folders. Just do the above steps. I was seeing messages that looked like what I get when the indexes aren't correct on a folder. Let me know what you see. - rhp

I just finished my build. The Send Later seems failed on me. I didn't get anything added to my Unsent Messages folder.

Looks like a copy problem...jeff will take over at this point. - rhp

Reassign back to rhp... I am not convinced that there are problems with copy service. I have done as much debug as possible. From the debugger, send later code successfully access the message header, for example the subject of the message. For some reason the send failed. Another proof of the copy service does the right thing is if you have the folder open the newly copied message is correctly added to the thread pane. There is something wrong with the send later, it may have something to do with the asynchronous send operation or something to do with the editor. Ref counting problem may be. I got crashes in the editor each time I did a send later operation.

Ok, I've fixed the problem that made this feature somewhat random. It was actually sending every other message if you were deleting them after sending. There is another bug (Bug #10344) assigned to Scott Putterman that has to do with failure to read messages from the unsent folder after doing an initial send later operation. - rhp

Linux and Mac 91999-08-16-08 M9), Win_nt 4.0 (1999-08-16-09 M9) POP: Sent later works fine now.