Re: [fetchmail-users] [fetchmail-announce] fetchmail 6.3.6-rc4 release candidate

[Jakob H. <jh...@pl...>]

Quoting Matthias Andree:

It worked here:

> fetchmail: 6.3.6-rc3 querying pop.guru.de (protocol POP3) at Mon, 27 Nov 2006 10:58:09 +0100 (CET): poll started
> Trying to connect to 212.11.227.194/110...connected.
> fetchmail: POP3< +OK b1gPOP3 2-1.22 Linux (guru.de) ready
> fetchmail: POP3> USER xx...@gu...
> fetchmail: POP3< +OK Need password for xx...@gu...
> fetchmail: POP3> PASS *
> fetchmail: POP3< +OK Logged in, you have 0 message(s) in your mailbox (0 octets)
...

but not anymore...

> fetchmail: 6.3.6-rc4 querying pop.guru.de (protocol POP3) at Mon, 27 Nov 2006 10:59:54 +0100 (CET): poll started
> Trying to connect to 212.11.227.194/110...connected.
> fetchmail: POP3< +OK b1gPOP3 2-1.22 Linux (guru.de) ready
> fetchmail: POP3> CAPA
> fetchmail: POP3< -ERR Unknown command (in this session state): "CAPA"
> fetchmail: Unknown command (in this session state): "CAPA"
> fetchmail: Authorization failure on xx...@gu...@pop.guru.de
> fetchmail: POP3> QUIT
> fetchmail: POP3< +OK Bye
> fetchmail: 6.3.6-rc4 querying pop.guru.de (protocol POP3) at Mon, 27 Nov 2006 10:59:54 +0100 (CET): poll completed
> fetchmail: Query status=3 (AUTHFAIL)
> fetchmail: normal termination, status 3

with

defaults
  proto pop3
...

and

poll pop.guru.de auth password user xx...@gu... pass yyyyyy fetchall to
"guru"

There should be no CAPA at all (or at least used to be), but fetchmail
should not stumble on that, I guess.