> Connection established to 76.96.62.119
> >> 0016 +OK POP3 ready
> << 0016 USER dthomsen8
> >> 0005 +OK
> << 0016 PASS XXXXXXXXX
> 8: Socket read timeout.
>
> This is what I get after about 20 seconds every time I try to
> receive mail as user DAVID. I can get mail as any of my three other
> identities just fine, and I can send mail from DAVID. I have sixty
> (60) messages waiting for download from COMCAST.NET, which I know
> from the web access to the mail. These messages have accumulated
> while I was traveling abroad, and is highly unusual for me. Many of
> these messages have attachments, which I need.
>
> I have used the General tab to change the network timeout to 999,
> but that makes no difference in what happens. What can I do now?
What is the timeout setting in the POP3 setup? If it is not blank then it overrides the general tab timeout setting.
FWIW, when I tried to ping 76.96.62.119 it times out, however I'm having troubles with the internet right now with some routes to host.
You may also be having problems with the the packet size. 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.
<p>&gt; Connection established to 76.96.62.119
&gt; &gt;&gt; 0016 +OK POP3 ready
&gt; &lt;&lt; 0016 USER dthomsen8
&gt; &gt;&gt; 0005 +OK
&gt; &lt;&lt; 0016 PASS XXXXXXXXX
&gt; 8: Socket read timeout.
&gt;
&gt; This is what I get after about 20 seconds every time I try to
&gt; receive mail as user DAVID.&nbsp; I can get mail as any of my three other
&gt; identities just fine, and I can send mail from DAVID.&nbsp; I have sixty
&gt; (60) messages waiting for download from COMCAST.NET, which I know
&gt; from the web access to the mail.&nbsp; These messages have accumulated
&gt; while I was traveling abroad, and is highly unusual for me.&nbsp; Many of
&gt; these messages have attachments, which I need.
&gt;
&gt; I have used the General tab to change the network timeout to 999,
&gt; but that makes no difference in what happens.&nbsp; What can I do now?
What is the timeout setting in the POP3 setup?&nbsp; If it is not blank then it overrides the general tab timeout setting. &nbsp;
FWIW, when I tried to ping 76.96.62.119 it times out, however I'm having troubles with the internet right now with some routes to host.
You may also be having problems with the the packet size.&nbsp;&nbsp; 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 mail via WinPMail disappear.</p><p>&nbsp;</p>