> I'm getting "8: Socket read timeout." errors again. I'm getting them from home and from external places
>
> Here's the trace; hopefully I have tried to remove the identifying names, numbers, and addresses from the trace (which, I hope, doesn't
> impede assistance)
>
> All the 999 stuff is really just GoDaddy's machine, I'm going through two (or sometimes three) different local ISPs to get there. (I'm in 3
> different places during the day.)
>
> The symptoms are: works sometimes, fails other times.  Each different ISP will-then-won't work, then will again, then won't again; and so
> on. There is no real pattern to the behavior. Seems to happen on at least two of them.
>
> I'm trying to send someone an 81 KB PDF file attached to an Ascii text message of about 1740 bytes total; if I'm counting properly.
>
> I'm running Pegasus off a 4GB thumb drive.

May or may not be a problem but it should not cause a TCP/IP timeout.

> Do I have a problem ? Or is it the local ISPs all out to get me ?
> Answers that work will result in big thanks.

Hard to say why you are getting the timeout since this does not show the timeout setting but if you are always going through 2-3 servers then I would expect that the timeout setting may be the problem.  Can't really tell from this but if you were to provide a session log showing the failure it would help.

In any case I would go to the POP3 and SMTP setups and set the TCP/IP timeout to no less than 180 seconds and I use 300 seconds.  

>
>
> ------------------------------------------------
>
> Connection established to 999.999.999.999
> >> 0053 220 p3plsmtpa06-09.prod.phx3.nineninenine.net ESMTP
> << 0022 EHLO  [192.168.1.100]
> >> 0047 250-p3plsmtpa06-09.prod.phx3.nineninenine.net
> >> 0022 250-AUTH LOGIN PLAIN
> >> 0014 250-8BITMIME
> >> 0016 250 PIPELINING
> << 0012 AUTH LOGIN
> >> 0018 334 VXNlcm5hbWU6
> << 0034 N3AxbjNAY2xpbnRkYW5idXJ5LmNvbQ==
> >> 0018 334 UGFzc3dvcmQ6
> << 0014 UVdFUlRZNw==

These are the things you have to munge since the username and password  can be easily read through the use of a Base64 decoder.

> >> 0031 235 Authentication succeeded.
> << 0041 MAIL FROM:<Original_1@The_Domain_1.com>
> >> 0022 250 Sender accepted.
> << 0036 RCPT TO:<her-e-mail@HerCompany.com>
> >> 0025 250 Recipient accepted.
> << 0006 DATA
> >> 0037 354 End your message with a period.
> 8: Socket read timeout.

I'm getting "8: Socket read timeout." errors again.

I'm getting them from home and from external places

Here's the trace. I have tried to remove the identifying names, numbers, and addresses from the trace (which, I hope, doesn't impede assistance) 

All the 999 stuff is really just GoDaddy's machine, I'm going through two (or sometimes three) different local ISPs to get there. (I'm in 3 different places during the day.)

The symptoms are: works sometimes, fails other times.  Each different ISP will-then-won't work, then will again, then won't again; and so on. There is no real pattern to the behavior. Seems to happen on at least two of them.

I'm trying to send someone an 81 KB PDF file attached to an Ascii text message of about 1740 bytes total; if I'm counting properly.

I'm running Pegasus off a 4GB thumb drive.

Do I have a problem ? Or is it the local ISPs all out to get me ?

Answers that work will result in big thanks.

------------------------------------------------

[*] Connection established to 999.999.999.999
>> 0053 220 p3plsmtpa06-09.prod.phx3.nineninenine.net ESMTP
<< 0022 EHLO [192.168.1.100]
>> 0047 250-p3plsmtpa06-09.prod.phx3.nineninenine.net
>> 0022 250-AUTH LOGIN PLAIN
>> 0014 250-8BITMIME
>> 0016 250 PIPELINING
<< 0012 AUTH LOGIN
>> 0018 334 VXNlcm5hbWU6
<< 0034 N3AxbjNAY2xpbnRkYW5idXJ5LmNvbQ==
>> 0018 334 UGFzc3dvcmQ6
<< 0014 UVdFUlRZNw==
>> 0031 235 Authentication succeeded.
<< 0041 MAIL FROM:<Original_1@The_Domain_1.com>
>> 0022 250 Sender accepted.
<< 0036 RCPT TO:<her-e-mail@HerCompany.com>
>> 0025 250 Recipient accepted.
<< 0006 DATA
>> 0037 354 End your message with a period.
8: Socket read timeout.