Ipswitch mail server returns two -ERR messages after an
authentication error, which then throws AUTH=any into turmoil.
DEBUG: fetchmail: 5.9.13 querying mail.mepps.com (protocol POP3) at
Thu Jul 31 20:28:11 2003: poll started
DEBUG: fetchmail: POP3< +OK X1 NT-POP3 Server imail.innerhost.com
(IMail 7.14 577995-5)
DEBUG: fetchmail: POP3> CAPA
DEBUG: fetchmail: POP3< +OK Capability list follows
DEBUG: fetchmail: POP3< TOP
DEBUG: fetchmail: POP3< USER
DEBUG: xxx POP3< SASL LOGIN PLAIN CRAM-MD5
DEBUG: fetchmail: POP3< RESP-CODES
DEBUG: fetchmail: POP3< LOGIN-DELAY 120
DEBUG: fetchmail: POP3< PIPELINING
DEBUG: fetchmail: POP3< EXPIRE 30 USER
DEBUG: fetchmail: POP3< UIDL
DEBUG: fetchmail: POP3< IMPLEMENTATION Ipswitch_IMail_6.0
DEBUG: fetchmail: POP3< .
DEBUG: fetchmail: POP3> AUTH CRAM-MD5
DEBUG: fetchmail: POP3< + PDE5ODU2LjYzMDEwMzczNEBJTUFJTD4=
DEBUG: fetchmail: POP3> dGVzdCBkY2IyMmQyMmMwYWE0MWI1MDk4NDg5YTQwZDA1YzBmYg==
DEBUG: fetchmail: POP3< -ERR authentication exchange failed
DEBUG: fetchmail: POP3> USER xxx
DEBUG: fetchmail: POP3< -ERR illegal command
DEBUG: fetchmail: POP3> PASS
DEBUG: fetchmail: POP3< +OK send your password
DEBUG: fetchmail: POP3> STAT
DEBUG: fetchmail: POP3< -ERR illegal command
DEBUG: fetchmail: POP3> QUIT
DEBUG: fetchmail: POP3< -ERR Invalid userid/password
DEBUG: fetchmail: 5.9.13 querying mail.mepps.com (protocol POP3) at
Thu Jul 31 20:28:14 2003: poll completed
DEBUG: fetchmail: normal termination, status 4
Any ideas on how to deal with this? It's not super critical, but it
would be nice to return the right error. It seems to me we'd have to
peek ahead and see if there's another server response waiting for us.
--
Kee Hinckley
http://www.messagefire.com/ Anti-Spam Service for your POP Account
http://commons.somewhere.com/buzz/ Writings on Technology and Society
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.