On Sun, Apr 22, 2001 at 07:08:16PM +0200, Matthias Scheler wrote:
...
The problem is that "fetchmail" tries to authenticate itself twice:
fetchmail: 5.8.1 querying mail.core.de (protocol POP3) at Sun Apr 22 19:04:48
2001
fetchmail: Issuer Organization: Markus Illenseer
fetchmail: Issuer CommonName: mail.core.de
fetchmail: Server CommonName: mail.core.de
fetchmail: Issuer Organization: Markus Illenseer
fetchmail: Issuer CommonName: mail.core.de
fetchmail: Server CommonName: mail.core.de
fetchmail: POP3< +OK POP3 v2000.70 server ready
<2779(_dot_)3ae30f31(_at_)localhost>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows:
fetchmail: POP3< TOP
fetchmail: POP3< LOGIN-DELAY 180
fetchmail: POP3< UIDL
fetchmail: POP3< STLS
fetchmail: POP3< USER
fetchmail: POP3< SASL CRAM-MD5 LOGIN
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< + PDEwMTA1Ljk4Nzk1OTA5MEBiZWF2ZXIuY29yZS5kZT4=
fetchmail: POP3> dHJvbiA5NmU2NzFlZGM0ZDA3MGIzZTRjMzU5ZGE5NzUxZjRiYw==
fetchmail: POP3< +OK Mailbox open, 0 messages
fetchmail: POP3> USER tron
fetchmail: POP3< -ERR Unknown TRANSACTION state command
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR Unknown TRANSACTION state command
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Sayonara
fetchmail: Query status=3 (AUTHFAIL)
fetchmail: normal termination, status 3
Here is the entry in ".fetchmailrc":
poll mail.core.de proto pop3 user tron password ********** ssl
If I add an "auth passwd" everything works fine. If I add "auth cram-md5"
"fetchmail" uses plain password authentification but is able to log in.
It looks like there is a serious bug in the handling of the configure
authentification scheme.
I have the same problem :
(client = fetchmail 5.8.1 on FreeBSD 4.3, server unknown beside what it prints,
see below)
rguyom(_at_)diabolo ~ fetchmail -v pop.waika9.com
fetchmail: 5.8.1 interroge pop.waika9.com (protocole POP3) à Lun 30 avr
14:46:40 2001
fetchmail: POP3< +OK POP3 server ready (5.1.046)
<17D3A23982AAC5706FD878FC66B441CAB0174CF8(_at_)mail(_dot_)servisp(_dot_)9telecom(_dot_)fr>
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< RESP-CODES
fetchmail: POP3< USER
fetchmail: POP3< SASL CRAM-MD5
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION NPLEX-Global-5.1.046
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< +
PEYwRUVFODgxMDIyMTUzNUYwNTk2OTdCQjMwNjBEQzM3QTZEQzUyOUNAbWFpbC5zZXJ2aXNwLjl0ZWxlY29tLmZyPg==
fetchmail: POP3>
b2xpdmllci5jb2xsb3RAd2Fpa2E5LmNvbSBkNjU2MmRkMmNhMmQxYTQ2YmRjODY1MDhkMTg4MzYxYw==
fetchmail: POP3< +OK 0 messages
fetchmail: POP3> USER olivier(_dot_)collot(_at_)waika9(_dot_)com
fetchmail: POP3< -ERR wrong state
fetchmail: wrong state
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR wrong state
fetchmail: wrong state
fetchmail: Authorization failure on
olivier(_dot_)collot(_at_)waika9(_dot_)com@pop.waika9.com
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP3 server closing connection
fetchmail: Query status=3 (AUTHFAIL)
fetchmail: terminaison normale, état 3
rguyom(_at_)diabolo ~ fetchmail -v --auth password pop.waika9.com
fetchmail: 5.8.1 interroge pop.waika9.com (protocole POP3) à Lun 30 avr
14:46:24 2001
fetchmail: POP3< +OK POP3 server ready (5.1.046)
<B494CB89AB493408AE7F70DFC48102E7A568D51D(_at_)mail(_dot_)servisp(_dot_)9telecom(_dot_)fr>
fetchmail: POP3> USER olivier(_dot_)collot(_at_)waika9(_dot_)com
fetchmail: POP3< +OK Password required
fetchmail: POP3> PASS *
fetchmail: POP3< +OK 0 messages
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: Aucun message pour olivier(_dot_)collot(_at_)waika9(_dot_)com dans
pop.waika9.com
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP3 server closing connection
fetchmail: terminaison normale, état 1
--
Rémi