Protocol error sending mail

davidp54

posted Mar 2 '12 at 10:53 pm

Thanks for the suggestion. I think I solved the problem by switching my SMTP server to Godaddy instead of Comcast. Seems to be working now; if I have further problems I will follow your procedure.

davep54

Thanks for the suggestion.&nbsp; I think I solved the problem by switching my SMTP server to Godaddy instead of Comcast.&nbsp; Seems to be working now; if I have further problems I will follow your procedure.&nbsp;davep54

davidp54

posted Mar 2 '12 at 3:17 am

I have not been able to send any email for 2 days... When I do I get the following error message:

15: Peer connect failure (the host has refused the connection).

My smtp connection is through Comcast.

Running Pegasus V4.63 on Windows XP.

Still able to download mail fine.

I have not changed the Internet connection settings.

How do I track this problem down/fix it? Any ideas?

I have not been able to send any email for 2 days... When I do I get the following error message:15: Peer connect failure (the host has refused the connection).My smtp connection is through Comcast.Running&nbsp; Pegasus V4.63 on Windows XP.Still able to download mail fine.I have not changed the Internet connection settings. How do I track this problem down/fix it?&nbsp; Any ideas?

Thomas R. Stephenson

posted Mar 2 '12 at 5:09 pm

> I have not been able to send any email for 2 days... When I do I get the following error message:
>
> 15: Peer connect failure (the host has refused the connection).
>
> My smtp connection is through Comcast.
> Running Pegasus V4.63 on Windows XP.
> Still able to download mail fine.
> I have not changed the Internet connection settings.
>
> How do I track this problem down/fix it? Any ideas?

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 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. You can send us a copy of the session log for analysis if you wish, make sure you munge any password info.

&gt; I have not been able to send any email for 2 days... When I do I get the following error message: &gt; &gt; 15: Peer connect failure (the host has refused the connection). &gt; &gt; My smtp connection is through Comcast. &gt; Running&nbsp; Pegasus V4.63 on Windows XP. &gt; Still able to download mail fine. &gt; I have not changed the Internet connection settings. &gt; &gt; How do I track this problem down/fix it?&nbsp; Any ideas? Go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)" &nbsp; 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 the mail and then look at the resulting TCP/IP debug file.&nbsp; Review of this file will tell you exactly what is going on between WinPMail and the server. You can send us a copy of the session log for analysis if you wish, make sure you munge any password info.

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history