Thank you Sir.

I've used Pegasus ever since I started 'netting back in 199#, never had any problem, and don't want to change (especially to any prog that doesn't let you review and delete mail on the server).  So well has the prog functioned that I until now I never had the need to look for assistance, so didn't realise (or expect that) this amazing forum existed.

Last year my Pegasus began timing out on any message with an attachment: even if only 10kb or less.  I tried reinstalling without success, and concluded that there was some file in the Mailbox which was corrupted.  When I recently (effectively) reinstalled Windows XP (sp3), I reinstalled Pegasus (v4.01) and set up a new empty folder for the mailbox,  All seemed well, but now the new installion is doing the same thing. The 'failed delivery' message is *** TCP/IP error while processing job ***. I've increased my timeout to 300s to no effect, tried disabling my firewall, and observed that Outlook Express is able to send (large) attachments.....

I've reviewed a number of the postings here on the subject, and it looks to me (without verifying this comprehensively) that this attachments glitch seems to be a 2008 issue.

What I want to do is save my email messages with a view to importing them into a fresh install of Pegasus 4.51, and have archived them according to John Navas' instructions at http://community.pmail.com/forums/thread/78.aspx 'How do I archive mail folders?'.  There he writers "If and when you want to access those archives, you can reconnect Pegasus Mail to the directory and you'll see all the folders in the Folders window."  I can't see how to 'reconnect', and my searches here and Googling have discovered no advice.

Soooo.... bearing in mind that my field is html, css, with some javascript and php i.e. no programming etc., I was hoping someone could tell me how to 'reconnect' that archived mailbox, and maybe point out any updated solutions to the attachment glitch.

 Thanks in advance for any pointers, guidance or tech tips!

> Last year my Pegasus began timing out on any message with an attachment:
> even if only 10kb or less.  I tried reinstalling without success, and
> concluded that there was some file in the Mailbox which was corrupted.
> When I recently (effectively) reinstalled Windows XP (sp3), I reinstalled
> Pegasus (v4.01) and set up a new empty folder for the mailbox,  All seemed
> well, but now the new installion is doing the same thing. The 'failed
> delivery' message is *** TCP/IP error while processing job ***. I've
> increased my timeout to 300s to no effect, tried disabling my firewall,
> and observed that Outlook Express is able to send (large) attachments.....

This sounds like a packet fragmentation problem.  The 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 that I find quite handy.  http://www.speedguide.net/downloads.php  This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers.  If will also make it easy to adjust the MTU.  

And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard?  If so, many other have had this exact problem, and it turned out to be an optimization setting for the built in NIC which caused the problems with packet fragmentation. Disabling the advanced optimization capability called "checksum offload" made all the problems of sending SMTP mail via WinPMail disappear.

You also might want to try doing blocking sockets.  That is what OE is doing for it's transfer.  The -z 1024 commandline option will force the use of blocking sockets.

Well, I'd seen your other posts to much the same effect, which I thought was specific to the other people with this sort of prob.

But apparently it was.that 'simple'. I tried it, not at all confident it'd do the trick, but it did. I've just tested it with a 2.8Mb file, and it looks like Pegasus is back in business again, which is going to save me a whole load of fuss.

The mobo does indeed have a NVidia NForce 4 chipset. I'll check out the "checksum offload", but since things are apparently working I'll probably not tinker with things beyond my ken.

Just one q. "Blocking sockets"... "-z 1024" commandline... This means next to 0 to me.  Is this appended to the shortcut (currently ""C:\Program Files\Pegasus\winpm-32.exe" -A")?

Well done that man. Thanks.

(I think it's best to ask my 'reconnect' q in specific thread - or look out for John Navas.)

Just one q. "Blocking sockets"... "-z 1024" commandline... This means

next to 0 to me.  Is this appended to the shortcut (currently

""C:\Program Files\Pegasus\winpm-32.exe" -A")?