Thank you for your help. I found Mercury specified as a UDG (using pcconfig.exe - as you suggested) and deleted it.

I am now able to send out e-mails with Pegasus Mail again.

I would still like to use Mercury Win32 at some later time to facilitate the testing of sending e-mails from a web application I am creating  on my home on which I have the apache server running, so I expect to be back with more posts on this forum.

The last several attemps I have made to send out email messages with Pegasus mail have not worked. I see the messages in the "send to self" folder and I get the "No Queued Mail" box - There are no messages waiting to be sent at present. when I click on the "send all queued mail" button. However none of my e-mails are being sent out.

I checked the SMTP settings with my ISP and they are correct.

How do I begin to resolve this problem? 

 Looking for assistance.

> The last several attemps I have made to send out email messages with
> Pegasus mail have not worked. I see the messages in the "send to self"
> folder and I get the "No Queued Mail" box - There are no messages
> waiting to be sent at present. when I click on the "send all queued
> mail" button. However none of my e-mails are being sent out.
>
> I checked the SMTP settings with my ISP and they are correct.
>
> How do I begin to resolve this problem?

Assuming you have not been installing mercury/32 go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"  

Checking this control tells Pegasus Mail to create special log files that show the entire exchange of information between it and the servers it connects to. Each session will be created in a file called TCPxxxx.WPM in your home mailbox directory (the "xxxx" is replaced by four digits). Creating session logs will slow down the performance of your system somewhat, and you should be aware that any username and password information exchanged between Pegasus Mail and the server will be shown in the log, *even* if you use SSL to secure the connection. Session logs are primarily useful if you need to debug a problem between Pegasus Mail and one of the servers it connects to - you should enable the option only on instructions from a system administrator or from Pegasus Mail technical support. [ Technical note: this control has the same effect as using a "-Z 32" commandline switch when you run Pegasus Mail ]

You can now try again to send/receive the mail and then look at the resulting TCP/IP debug file.  Review of this file will tell you exactly what is going on between WinPMail and the server.
>
>  Looking for assistance.

I do have Mercury Win32 Installed but it was not running at the time I was attempting to send out the e-mails. How does this factor change what I have to do to get my e-mails sent out?

 Thank you for your help.

[quote user="gordonwebs"]

I do have Mercury Win32 Installed but it was not running at the time I was attempting to send out the e-mails. How does this factor change what I have to do to get my e-mails sent out?

If yuo install Mercury/32 and point it at the Pegasus Mail  program it will create a user defined qateway to allows Pegasus Mail to sand mail via the mercury queue.  Try running pconfig.exe from the Pegasus Mail program directory and see if the UDG MERCURY exists.

 Thank you for your help.