All done. Things went so smoothly I'm wondering why I was nervous.  Then again, I'm always nervous upgrading Pegasus.  There are so many things which can go wrong, some real and some imaginary.  But, it worked like a charm when I followed your instructions.  Thank you, sir.  [:D]

I've had an smtp error for the past two days.  My Pegasus (v 4.63) is unable to send mail.  It will do everything else it normally does without problems, but it will not send mail.  Receiving mail, no problem.  Sending mail, no way.

Description of the error:  "A network error occurred during connection to the host."

 I did not change any settings to cause this.  Pegasus worked beautifully, until it didn't two days ago.

 Please, ask me whatever you need in order to help.  

A session log should provide an indication where the problem is occurring in the communication process.  To enable session logging go to Tools > Internet Options and tick the "Create internet session logs.." option at the bottom of the General tab.  While in there, open the help file and read about session logging.  It explains what gets logged.  Be careful not to post the entire log because access credentials are logged.  They're encoded but can easily be decoded. 

Don't forget to turn logging off when done troubleshooting.

It took me a while to find the session logs, and I'm not absolutely sure I found what I need, since I've never ventured into this area before.  I'll paste in what I found for a send failure.  I don't believe there is anything here falling into the "guarded information" section.

 --- Mon, 11 Jul 2016 07:44:17 ---
Connect to 'smtp.comcast.net' port 465, timeout 180.
07:44:17.510 [*] Connection established to 96.114.157.81
07:44:17.581 22: Error -32 activating SSL session (locus 6014, type 4, 'Bad server key agreement parameter signature\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC\FFFFFFCC')
07:44:17.581 --- Connection closed normally at Mon, 11 Jul 2016 07:44:17. ---\0A\0A

Now, what is Pegasus trying to tell me?

What version of Pegasus Mail are you using?

[quote user="Brian Fluet"]What version of Pegasus Mail are you using?
[/quote]

v 4.63

The port is unusual, I believe, but is the result of a previous problem a number of years ago.  I think that problem was resolved here on this forum, if memory serves.

See this thread:

http://community.pmail.com/forums/7/37507/ShowThread.aspx

If you read all the way to the end you will find that v4.70 solved the problem.

Here's the long of it...

A new implementation of SSL (OpenSSL) was included in v4.70 to address the issue of mail servers no longer accepting communication from the SSLv3 in v4.63 and prior. The upgrading of SSL in mail servers has been gradual so many folks do not have a problem running v4.63, until they do.  I think you just did.  An upgrade to v4.7x (current version is v4.72) should solve the problem but I suggest researching Comcast's current SMTP configuration requirements as well.

Make a complete backup of Pegasus Mail including the mailbox root directory and all subdirectories before upgrading just in case.

Thank you, sir.  I'll get on this later today. 

I'll report back if I find anything interesting or have further trouble.

I spoke today with the Comcast internet tech support people, trying to determine which SSL version they require that I use.  They were of absolutely no help, had no idea.  I had the feeling the woman had no idea what SSL is, didn't seem to recognize the term.  In their opening recorded message they said that they support all mail clients, but when it came down to it, the woman said she had no idea about Pegasus, that it is not on their list.  Tech support strikes out again.

So, I've decided on a plan of action.  I've been slowly getting another tower ready for use.  It's old, but a bit newer than my current tower.  It runs Windows 7, as opposed to my current XP.  I have no desire to go to Windows 8 or 10.  I put a new hard drive in that tower after Christmas, and the new RAM arrived today.  That tower will be in use by the weekend.  It will have Pegasus 4.72 in a fresh download.

 Mr Fluet, you have stated, when talking about upgrading to Pegasus 4.63 from 4.41, that 4.63 could be installed over the top of 4.41, or that 4.63 could be installed fresh and 4.41 installed over the top of it in order to retain all the settings and mail.  Either could be added on top of the other, as long as the pathways were identical.  Is that true of 4.63 and 4.72 as well?  Can I put either one on the new drive and run the other over the top of it, as long as the pathways are identical?  I will be downloading 4.72, and transferring 4.63 on a thumbdrive.  Is one preferable over the other to use as a base, as the initial program?

My current issue of Pegasus:

C:\PMAIL

      \MAIL

            \ADMIN

      \PROGRAMS

            \DEFAULTS

            \ IERenderer

            \PNG

            \RESOURCE

Sorry about the double spacing.  The computer seems to like that when I hit 'ENTER' in this forum.

The fact that you are using the default installation location of C:\PMAIL makes moving to a different machine and upgrading very easy.  Simply copy the entire C:\PMAIL directory from the old machine to C:\PMAIL on the new machine.  Run it once which will create a registry entry that records is location.  Now install v4.72.  It will check the registry and see the path to the existing version.

If you have any issues with v4.63 other than this SSL one consider a new install of v4.72 followed by copying only the mail data from the old mailbox.

BTW, the double spacing that follows the enter key in the forum annoys me too.  I sometimes create content in Notepad and then paste it into a post as a workaround to the double space issue.