[quote user="Strabo"]I do have web access to them, but this isn't the first (or largest) message its done it with, It seems to be any message with an attachment. the others eventually stopped (I think repeats was the longest before this one) but this one just keeps coming.
I've doubled the timout and its still happening so i've doubled it again (now 1200!) and have deleted it online.
I cant see it being a problem with the mail server cos I connected to that one from my dads machine :S
[/quote]
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/receiving POP3 mail via WinPMail disappear.
<p>[quote user="Strabo"]I do have web access to them, but this isn't the first (or largest) message its done it with, It seems to be any message with an attachment. the others eventually stopped (I think repeats was the longest before this one) but this one just keeps coming.
I've doubled the timout and its still happening so i've doubled it again (now 1200!) and have deleted it online.
I cant see it being a problem with the mail server cos I connected to that one from my dads machine :S
[/quote]
</p><p>The POP3/SMTP transmissions may fail if the MTU packet size is so large that a packet is fragmented.&nbsp; In many cases the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery".&nbsp; These oversize packets are not accepted and so are resent.&nbsp; This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process.&nbsp; You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492.&nbsp; 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.&nbsp; http://www.speedguide.net/downloads.php&nbsp; This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers.&nbsp; If will also make it easy to adjust the MTU.&nbsp;
And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard?&nbsp; 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/receiving POP3 mail via WinPMail disappear.
</p>