Re: [Nolug] Errors fetching mail from cox.net

you, sir are most likely at the mercy of cox at this point. I would
do some tests for you if I was on cox, but i'm on charter ( prob going
to be a cox customer soon I guess ? ) Anyone else here having similar
issues? I just checked the cox hsi LA forum on broadband reports
and I don't really see anything with people complaining. Good luck on
your journey for an answer :) It could take quite a bit of time (
something in very short supply ) to track down the specific cause. I
wonder if the nice people who can fix it are aware of an issue ( also
have you tried something other then fetchmail, as a human sanity
check? ).
On Fri, Apr 17, 2009 at 3:53 PM, Ron Johnson <ron.l.johnson@cox.net> wrote:
> On 2009-04-16 19:19, Ron Johnson wrote:
>>
>> On 2009-04-16 11:47, Dennis J Harrison Jr wrote:
>> [snip]
>>>
>>>> But anyway, wouldn't that problem generate a different error?
>>>
>>> Yes, it certainly SHOULD :)  I am just regurgitating :
>>> http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html#R6
>>>
>>> Which was pointed out to me when I ran into similar problems with
>>> i-55... years ago though.
>>
>> I'll try that...
>
> It seemed to work for a while, but this morning it stuck on a 3.5KB email...
>
> fetchmail[23614]: reading message ron.l.johnson@68.1.17.2:1 of 15 (4562
> octets) flushed
> fetchmail[23614]: reading message ron.l.johnson@68.1.17.2:2 of 15 (1091649
> octets) flushed
> fetchmail[23614]: reading message ron.l.johnson@68.1.17.2:3 of 15 (3488
> octets) (log message incomplete)
> fetchmail[23614]: socket error while fetching from ron.l.johnson@68.1.17.2
> fetchmail[23614]: Query status=2 (SOCKET)
>
> --
> Scooty Puff, Sr
> The Doom-Bringer
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 04/17/09