Thanks for the suggestions Thomas. I'm afraid I don't understand most of them, but I'll have my husband look at them and see if we can make this work.
Bev
I've recently bought a new computer adn have managed to get Pegasus reset up, but I'm having real problems anytime I try to send a message which is larger
than 1 mg. Even messages with smaller attachments don't always go if they are queud behind a message with a larger attachment. I receive a message such as the following:
Delivery has failed on the enclosed message for the following
reasons reported either by the mail delivery system on the mail
relay host or by the local TCP/IP transport module:
*** TCP/IP error while processing job ***
A network error has occurred while WinPMail attempted to send
your message. This error could be caused by many conditions,
including the following:
* The remote host may have gone down.
* Your network may have been broken or gone down.
* You may have a configuration problem in your WINSOCK.DLL.
* If running on a SLIP line, you may have experienced a
timeout (increase the value in WinPMail's Network Config.
Dialog), or the phone line may have gone down or suffered
from excessive line noise.
WinPMail will requeue your message and try again later.
Sometimes even with the delivery failure notice, people are receiving the message 3 or 4 times. Other times it doesn't get through at all.
I have gone into my network configuration and set the default timeout for 180 seconds, but it doesn't appear to have made a difference. I get the failure message well before 180 seconds has gone by.
My local tech support people have been unable to offer any ideas, but I much prefer Pegasus to other mailers and don't want to switch. Any suggestions would be very much appreciated.
Bev
Try increasing the timeout setting in File | Network configuration | (Sending) SMTP setup to 120-180 seconds. If this does not fix the problem then it's probably 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.
