I checked my timeout setting and it was already set for 300 seconds. Didn't do a troubleshoot log. The timeout screen that pops up telling me my message wasn't sent DOES say something about "mail was undeliverable due to SMTP error" and that no tracking information is available. This times out at 20 seconds.

 Does this information help in any way? Thanks again for your time & help!

This just started. I write an email and hit "send" - messages get sent. Write email and hit "send" and message(s) go to "Queued Mail". I then hit "send queued mail" and message(s) get sent. I have the "send messages immediately DO NOT place in que" checked. I enabled all options I could find to send messages at once (like I've always done) but the mail going to que before sending keeps happening intermittently.

 Any ideas for stopping this from happening? It worked for years but just started this. Thanks for any ideas!

Multiple identies?  The settings you refer to are identity specific.

[quote user="Brian Fluet"]

Multiple identies?  The settings you refer to are identity specific.

 [/quote]

Nope, just me that uses this computer and only under one (this one) name. I've used this for a while and never saw this before. After outgoing message goes to "queued mail" if I hit "send now" it does! No problem. Just doesn't send everytime I hit "send mail" these days. Some other setting I should change?

Are you on Windows 10? The same has been happening here intermittently over the past few weeks and I have not been able to determine why.

I doubt that it is a Pmail issue. I suspected it was something to do with Windows 10 and connectivity, hence the question.

Nope, sorry Windows 7. I, too, feel it's not the actual computer because I've used Pegasus on this machine for 4 years or so and on XP and W98 before that. Never an issue like this.

I assume the message is ending up in the queue as a result of a failed send but I don't know that for certain. 

Is there any indication that a send was attempted? 

Have you tried to capture a session log?

[quote user="Brian Fluet"]

I assume the message is ending up in the queue as a result of a failed send but I don't know that for certain. 

Is there any indication that a send was attempted? 

Have you tried to capture a session log?[/quote]

 I type my message and hit "send." A window pops up telling me the message didn't send. It says something about a message failure. I go to the "check queued mail" in the top header. Box opens and my message is in the box. I hit "send now" and it gets sent. Now, this doesn't happen 100% of the time. Sometimes the mail gets sent. Other times it goes to the "queued" folder/box. It's a crapshoot. If it goes to the "queued mail" box, I hit send and sometimes the "message failed" box pops up like in the original, Pegasus "send mail" command after first attempt. I hit send again and it sends from the queued box. And no, I haven't done a session capture log.

Am I making sense? Sometimes I worry that I'm not using the correct terminology to make your task easier. Thank you for your time and patience!

You are making perfect sense.  I believe that each time you see the popup about the message not sending is the result of a failed connection to the SMTP server.  A session log of one of these failures would identify the cause.  It doesn't take much technical expertise to look at a log file and identify the point of failure.  Don't post the entire content of a log file because it contains your login credentials in an easily decodable form.

One thing to immediately check is the timeout setting in your SMTP host configuration.  I use120 but have set some as high as 300.  If you are at less than 120 increase it to 120 and see if that improves connection reliability.

[quote user="Brian Fluet"]

You are making perfect sense.  I believe that each time you see the popup about the message not sending is the result of a failed connection to the SMTP server.  A session log of one of these failures would identify the cause.  It doesn't take much technical expertise to look at a log file and identify the point of failure.  Don't post the entire content of a log file because it contains your login credentials in an easily decodable form.

One thing to immediately check is the timeout setting in your SMTP host configuration.  I use120 but have set some as high as 300.  If you are at less than 120 increase it to 120 and see if that improves connection reliability.[/quote]

OK, thanks for that. I'll increase the timeout setting and retrieve a log file just in case....

 Thanks again, Brian, for your time and help.