I appear to have solved the problem by adding the command line parameters -Z 1024 to the shortcut, as suggested by Thomas Nimmersqern in this thread.  Thank you Thomas!  Both laptop and desktop are now receiving normally.

Now to try and install it on a new Vista laptop...

(I am still suspicious of Flashplayer upgrade...)

I recently installed Pmail 4.41 under Windows XP. No matter how I try to configure it to connect to my dial-up ISP, I always get the error msg - "5:Connect Failed 2726".

I've tried closing all security/anti-virus programs, canceling firewall protection, etc, etc. - all with the same results.

Any words of wisdom from those who have had similar problems?

Thanks!  

[quote user="LSteele"]I recently installed Pmail 4.41 under Windows XP. No matter how I try to configure it to connect to my dial-up ISP, I always get the error msg - "5:Connect Failed 2726".

I've tried closing all security/anti-virus programs, canceling firewall protection, etc, etc. - all with the same results.

Any words of wisdom from those who have had similar problems?

Thanks!  
[/quote]

I assume that the system is doing a dialup when you make this request.  My only guess is that there is still some firewall blocking the access to the outside world on ports 110 & 25.  Can you telnet into these ports?

No dialup upon request - dialup connection already established and online.  Hate to be dumb, but I don't know what "telnet" is.  As for some other firewall . . .

I disabled the firewall within Windows security section, I stopped Norton's email scanning (just in case) and disabled Norton's auto-protect, closed/stopped Webroot Spy sweeper (again, just in case) - and the error msg is all I can get.  I just don't know what else to look for that may be interfering? No idea what else I could disable.

[quote user="LSteele"]

No dialup upon request - dialup connection already established and online.  Hate to be dumb, but I don't know what "telnet" is.  As for some other firewall . . .

Try Start | Run telnet <your host name> 25  This should connect to your SMTP host to send mail.  If you get a connection enter ehlo <your email doman name> and you should see something like the following.  I munged the server name since it's not one of mine.

I disabled the firewall within Windows security section, I stopped Norton's email scanning (just in case) and disabled Norton's auto-protect, closed/stopped Webroot Spy sweeper (again, just in case) - and the error msg is all I can get.  I just don't know what else to look for that may be interfering? No idea what else I could disable.

Turning off Norton may or may not get it out of the path.  The first thing I do with any system I'm asked to fix is to remove all traces of Norton.  It's been nothing but trouble since Peter Norton sold it to Symantec.
 

Hello!

Myself, I have never seen this, so I can only guess what has happened.
I googled for similar reports, and I found three workarounds: changing the settings for a certain chipset of your motherboard; adjusting the MTU value in your Windows installation; adding a certain command line option for Pegasus Mail.

(a) *** Motherboard ***
Similar problems have been reported if the motherboard has an nVidia chipset.
The workaround seems to be to disable the advanced optimization capability called "checksum offload". The setting can be found in the BIOS setup.
I found that piece of information in a newsgroup posting that you can read here.

(b) *** MTU ***
If you want to know what "MTU" means, you may read the Wikipedia explanation about it.

Some time ago, I read the following advice concerning how to adjust the MTU settings:
[quote]A POP3/SMTP-transmissions may fail if the MTU packet size is so large that a packet is fragmented.

In many cases, the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery". These oversize packets are not accepted and so are resent. This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process.
You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492. You might simply want to turn off the MTU Discovery operation.
You might want to get a copy of SG TCP Optimizer (at <http://www.speedguide.net/downloads.php>). This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers. It will also make it easy to adjust the MTU.[/quote]
(c) *** commandline option ***
I also read that the commandline option "-Z 1024" may help to get rid of that problem.
For example, if your current commandline (to start Pegasus Mail) is "c:\pmail\winpm-32.exe -MS", you simply add the "-Z 1024"-flag to it, so the commandline would be "c:\pmail\winpm-32.exe -MS -Z 1024".
The helpfile says that that flag "Use blocking sockets [and] may be needed for some defective WINSOCK implementations" (on the helpfile titled "Command-line options").
(I found that idea at <http://www.webservertalk.com/archive205-2006-3-1424938.html>).


As said above, I am only guessing. I cannot promise that these suggestions will work for you (because I have never had to use them myself), but I hope it helps.

I have a laptop and desktop, both operating Pmail 4.41 with identical settings.  2 days ago the desktop suddenly gave me the Connect failed 2726 message and has refused to send or receive since.  Today the laptop suddenly did the same.  Clearly some external program is messing things up!

I did notice when I rebooted the laptop just before seeing Pmail fail that a new version of Flash player was being installed.  Could this be the culprit?

I ran tcpspy on both systems and got the identical results: