Summary | POP3 empty maillist + can login with wrong password or username |
Queue | IMP |
Queue Version | 5.0.10 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | slusarz (at) horde (dot) org |
Requester | netwalker (at) lanparty-nrw (dot) de |
Created | 08/22/2011 (5069 days ago) |
Due | |
Updated | 08/24/2011 (5067 days ago) |
Assigned | 08/22/2011 (5069 days ago) |
Resolved | 08/23/2011 (5068 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
I create a new Ticket for the Login Bug with some information about my
configuration and additional Log details:
http://bugs.horde.org/ticket/10453
State ⇒ Resolved
can login with wrong password too.
I the IMP i get the following Error Message:
Lesen der Ordnerliste fehlgeschlagen: Server search not supported on
POP3 server.
Bug #10424.authentication failed.
Bug #10450: Fix POP3 regression3 files changed, 9 insertions(+), 5 deletions(-)
http://git.horde.org/horde-git/-/commit/a91b4a3847c2263aff6bb2f8e60799b6afbe5ee5
Assigned to Michael Slusarz
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ POP3 empty maillist + can login with wrong password or username
Due ⇒ 08/30/2011
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Ticket: 10417andTicket 10424i install the current releaseupgrade ok: channel://pear.horde.org/Horde_Imap_Client-1.0.12
upgrade ok: channel://pear.horde.org/turba-3.0.7
upgrade ok: channel://pear.horde.org/imp-5.0.10
Now i cannot see any mail in the folder after the pop3 connect and i
can login with wrong password too.
I the IMP i get the following Error Message:
Lesen der Ordnerliste fehlgeschlagen: Server search not supported on
POP3 server.
empty list:
S (1314020185,85): +OK Hello there.
C (1314020185,85): CAPA
S (1314020185,87): +OK Here's what I can do:
S (1314020185,87): SASL PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256
S (1314020185,87): TOP
S (1314020185,87): USER
S (1314020185,87): LOGIN-DELAY 10
S (1314020185,87): PIPELINING
S (1314020185,87): UIDL
S (1314020185,87): IMPLEMENTATION Courier Mail Server
S (1314020185,87): .
C (1314020185,87): [AUTH PLAIN Command - username: test@example.com]
S (1314020185,89): +OK logged in.
C (1314020185,92): QUIT
S (1314020185,94): +OK Bye-bye.
------------------------------
S (1314020186,94): +OK Hello there.
C (1314020186,94): [AUTH PLAIN Command - username: test@example.com]
S (1314020186,96): +OK logged in.
C (1314020186,97): STAT
S (1314020186,98): +OK 3 402642
C (1314020187,07): QUIT
------------------------------
S (1314020187,12): +OK Hello there.
C (1314020187,12): [AUTH PLAIN Command - username: test@example.com]
S (1314020187,14): +OK logged in.
C (1314020187,15): QUIT
S (1314020187,16): +OK Bye-bye.
S (1314020187,17): +OK Bye-bye.
wrong username but can login:
------------------------------
S (1314020367,47): +OK Hello there.
C (1314020367,47): CAPA
S (1314020367,5): +OK Here's what I can do:
S (1314020367,5): SASL PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256
S (1314020367,5): TOP
S (1314020367,5): USER
S (1314020367,5): LOGIN-DELAY 10
S (1314020367,5): PIPELINING
S (1314020367,5): UIDL
S (1314020367,5): IMPLEMENTATION Courier Mail Server
S (1314020367,5): .
C (1314020367,51): [AUTH PLAIN Command - username: test@ecample.com]
S (1314020372,54): -ERR Authentication failed.
C (1314020372,54): AUTH LOGIN
S (1314020372,57): + VXNlcm5hbWU6
C (1314020372,57): dGVzdEBlY2FtcGxlLmNvbQ==
S (1314020372,6): + UGFzc3dvcmQ6
C (1314020372,6): [AUTH LOGIN Command - password]
S (1314020377,65): -ERR Authentication failed.
C (1314020377,65): AUTH CRAM-MD5
S (1314020377,67): + PDk1NjA1QzM1MTY1Mjg1NTk4RTVGMEVEODc5NzFDQjRCQG1haWwyMT4=
C (1314020377,67): [CRAM-MD5 Response]
S (1314020382,7): -ERR Authentication failed.
C (1314020382,72): QUIT
S (1314020382,74): +OK Better luck next time.