Re: [fetchmail-users] query state=2 (SOCKET)

[Rob M. <rob...@gm...>]

On 9/11/06, Roberto Meyer <rob...@gm...> wrote:
> Hi,
>
> I translated the error message in the subject of this mail from
> spanish, I don't know if it shows exactly like this in other systems.
>
> I'm running processes for each user from crontabs. I get error
> messages, not always, not always from the same user's cron job. I'm
> running Debian Sarge with fetchmail: 6.2.5.

Please update to 6.3 (though it probably won't help this particular case).

> I'm stuck. I've tried IMAP and POP3 and didn't find much difference.
> Fetchmail is connecting to Courier-IMAP or/and Courier-POP.

The error relates to fetchmail being unable to communicate with the
remote server.  This is almost always a network issue.

> fetchmail: 6.2.5 interrogando a mail.mydomain.com (protocolo POP3) en lun 11 s
>  iniciada
> fetchmail: error `socket' recibiendo de mail.mydomain.com
> fetchmail: 6.2.5 interrogando mail.mydomain.com (protocolo POP3) en lun 11 sep
> erminada
> fetchmail: Estado de la consulta=2 (SOCKET)
> fetchmail: terminación normal, estado 2
<---SNIP--->
> I'll appreciate any help. TIA,

One test you can try is to see if "telnet mail.mydomain.com 110" works
consistently.  You may find that you've got a number of remote
mailservers and one of them is causing this problem.

Without real domain names for the ISP it's hard to say more.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche