6.0.0-beta1
7/18/25

[#10417] POP3 Connection don't work in current release! Server Supports UIDL but IMP check says no!
Summary POP3 Connection don't work in current release! Server Supports UIDL but IMP check says no!
Queue IMP
Queue Version 5.0.9
Type Bug
State Resolved
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester netwalker (at) lanparty-nrw (dot) de
Created 08/09/2011 (5092 days ago)
Due
Updated 08/09/2011 (5092 days ago)
Assigned 08/09/2011 (5092 days ago)
Resolved 08/09/2011 (5092 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/09/2011 04:53:53 PM Michael Slusarz State ⇒ Resolved
Priority ⇒ 2. Medium
 
08/09/2011 04:53:10 PM Git Commit Comment #4 Reply to this comment
Changes have been made in Git for this ticket:

Bug #10417: Fix regression in POP3 Socket driver that caused incorrect 
parsing of server data

  2 files changed, 9 insertions(+), 6 deletions(-)
http://git.horde.org/horde-git/-/commit/c697fa16ac93fe2cbfff292347b18323528bbdcf
08/09/2011 04:40:51 PM Jan Schneider State ⇒ Assigned
Assigned to Michael Slusarz
 
08/09/2011 12:16:00 PM netwalker (at) lanparty-nrw (dot) de Comment #3 Reply to this comment
Two Logs one from courier one from dovecot:

DebugLog Server1: [courier pop3 Server]
S (1312891582,22): +OK Hello there.
C (1312891582,22): CAPA
S (1312891582,24): +OK Here's what I can do:
S (1312891582,24): SASL PLAIN LOGIN CRAM-MD5 CRAM-SHA1 CRAM-SHA256
S (1312891582,24): TOP
S (1312891582,24): USER
S (1312891582,24): LOGIN-DELAY 10
S (1312891582,24): PIPELINING
S (1312891582,24): UIDL
S (1312891582,24): IMPLEMENTATION Courier Mail Server
S (1312891582,24): .
C (1312891582,24): USER mail@example.com
S (1312891582,26): +OK Password required.
C (1312891582,26): [USER Command - password]
S (1312891582,28): +OK logged in.
C (1312891582,3): QUIT
S (1312891582,32): +OK Bye-bye.

DebugLog Server2: [dovecot pop3 Server]
S (1312891864,23): +OK mDd-MDA ready.
C (1312891864,23): CAPA
S (1312891864,25): +OK
S (1312891864,25): CAPA
S (1312891864,25): TOP
S (1312891864,25): UIDL
S (1312891864,25): RESP-CODES
S (1312891864,25): PIPELINING
S (1312891864,25): STLS
S (1312891864,25): USER
S (1312891864,25): SASL PLAIN DIGEST-MD5 CRAM-MD5
S (1312891864,26): .
C (1312891864,26): USER netwalker@lanparty-nrw.de
S (1312891864,28): +OK
C (1312891864,28): [USER Command - password]
S (1312891866,77): +OK Logged in.
C (1312891866,79): QUIT
S (1312891866,82): +OK Logging out.

08/09/2011 11:39:20 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
To further debug this issue, we need details of the IMP -> IMAP/POP 
communication.

To enable debugging, see instructions contained in 
imp/config/backends.php (the 'debug' config parameter).

Debugging should not be enabled on a production server,   Attach/post 
only the portion of the log that directly deals with the problem 
reported (it may be simplest to clear the log file and then perform 
the event that causes the error).
08/09/2011 11:02:11 AM netwalker (at) lanparty-nrw (dot) de Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ POP3 Connection don't work in current release! Server Supports UIDL but IMP check says no!
Due ⇒ 08/13/2011
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
POP3 Connection don't work in current release! Server Supports UIDL 
but IMP check says no!

I checked the pop3 feature with dovecot pop3 and courier pop3 Server 
both Support the UIDL Feature. If I try with telnet both tell me after 
the CAPA command UIDL is Supported

IMP5 currently don't work with pop3!?

Saved Queries