This is usually routing issue. Check the usual suspects with your fav
route tracing tool. If nothing stands out try giving fetchmail the a
record. I doubt it has anything to do with that though. Probably
just an overloaded server/connection/device on there end if the trace
is ok. Which is what you mentioned. But here is some vindication.
Have a good one, sourpuss :)
On Wed, Apr 15, 2009 at 6:29 PM, Ron Johnson <ron.l.johnson@cox.net> wrote:
> Hi,
>
> I'm seeing a lot of errors like this is my syslog, and it started about a
> week ago. Since I've been on the same fetchmail version (6.3.9~rc2-4 from
> Debian Sid) since before the new year, I'm thinking it's a change on Cox's
> end. Maybe their mail servers are too burdened?
>
> fetchmail[2103]: reading message ron.l.johnson@pop.east.cox.net:5 of 50
> (5537 octets) (log message incomplete)
>
> fetchmail[2103]: socket error while fetching from
> ron.l.johnson@pop.east.cox.net
>
> fetchmail[2103]: 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/15/09
This archive was generated by hypermail 2.2.0 : 08/06/09 EDT