Re: [fetchmail-users] fetchmail authorization and socket errors

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

On 11/12/06, Wade Smart <wa...@wa...> wrote:
> 11122006 1156 GMT-6
>
> Rob, I restarted my computer and ran that command again and this is what
> came out:

Overkill, but it works :)

> wadesmart@wadesmart:~$ fetchmail -c --nosyslog -v -v
> fetchmail: Old UID list from mail.wadesmart.com: <empty>
> fetchmail: Old UID list from pop.gmail.com: GmailId10a1ee3e2d493c9f
<---SNIP--->
> fetchmail: Scratch list of UIDs: <empty>
> fetchmail: 6.3.2 querying mail.wadesmart.com (protocol POP3) at Sun 12

Still not 6.3.5 :)

> Nov 2006 11:53:43 AM CST: poll started
> fetchmail: POP3< +OK
> <268...@po...>
> fetchmail: POP3> USER wa...@wa...
> fetchmail: POP3< +OK
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK
> fetchmail: selecting or re-polling default folder

Looks good, no sign of a problem here.

<---SNIP--->
> fetchmail: 6.3.2 querying pop.gmail.com (protocol POP3) at Sun 12 Nov
> 2006 11:53:44 AM CST: poll started
> fetchmail: Issuer Organization: Equifax
> fetchmail: Unknown Issuer CommonName
> fetchmail: Server CommonName: pop.gmail.com
> fetchmail: pop.gmail.com key fingerprint:
> 59:51:61:89:CD:DD:B2:35:94:BB:44:97:A0:39:D5:B4
> fetchmail: POP3< +OK Gpop ready for requests from 69.92.172.113
> g9pf9259914wra
> fetchmail: POP3> USER wad...@gm...
> fetchmail: POP3< +OK send PASS
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK Welcome.

Or here.

Whatever your problems were, they're gone now.  If they re-occur the
best thing you can do is shut down fetchmail, run it with "-v -v
--nosyslog" and post the output to the list.

I would still highly recommend upgrading to 6.3.5 - the developers
will insist on you're confirming the error with the latests problem if
you ever want to report a bug.

-- 
                 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