Summary | Occasional IMAP read errors |
Queue | IMP |
Queue Version | Git master |
Type | Bug |
State | No Feedback |
Priority | 1. Low |
Owners | |
Requester | Twilek (at) gmx (dot) de |
Created | 04/19/2009 (5925 days ago) |
Due | |
Updated | 05/13/2009 (5901 days ago) |
Assigned | 04/20/2009 (5924 days ago) |
Resolved | 05/13/2009 (5901 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
just fine with SASL-IR authentication on dovecot.
Based on the timestamps provided in your log, the socket read from
dovecot is timing out. PHP is returning false from the fgets()
command after the default network timeout period (10 seconds). So
Horde/IMP isn't at fault there.
The only possible way that IMP could be at fault is if the password
isn't set correctly the first time around. But that doesn't seem to
be the case because you login just fine after the initial attempt (and
a incorrect password delay shouldn't last 10+ seconds - and if it
does, you have not correctly configured IMP).
IMAP server (latest Dovecot). Logging in again solves the problem.
This problem seems to appear randomly. Other Programs like
Squirrelmail do not have the same problem so it does not seem to be
on dovecots side.
the relevant debug logs.
------------------------------
S (1240258469,83): * OK Dovecot ready.
C (1240258469,83): [SASL-IR AUTHENTICATE Command - username: twilek]
[ERROR: IMAP read error.]
C (1240258479,83): [LOGIN Command - username: twilek]
S (1240258484,18): 2 BAD Error in IMAP command LOGIN: Unknown command.
C (1240258484,18): 3 LOGOUT
S (1240258484,19): * BYE Logging out
S (1240258484,19): 3 OK Logout completed.
------------------------------
S (1240258484,23): * OK Dovecot ready.
C (1240258484,23): [SASL-IR AUTHENTICATE Command - username: twilek]
S (1240258494,19): 1 OK Logged in.
C (1240258494,2): 2 SELECT "INBOX.Trash"
S (1240258494,2): * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
S (1240258494,2): * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted
\Seen \Draft \*)] Flags permitted.
S (1240258494,2): * 93 EXISTS
S (1240258494,2): * 22 RECENT
and so on ....
State ⇒ Feedback
IMAP server (latest Dovecot). Logging in again solves the problem.
This problem seems to appear randomly. Other Programs like
Squirrelmail do not have the same problem so it does not seem to be
on dovecots side.
the relevant debug logs.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Occasional IMAP read errors
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
IMAP server (latest Dovecot). Logging in again solves the problem.
This problem seems to appear randomly. Other Programs like
Squirrelmail do not have the same problem so it does not seem to be on
dovecots side.
horde.log looks like this:
Apr 19 12:20:33 HORDE [error] [imp] IMAP read error. [pid 7512 on line
3229 of "/usr/share/php/Horde/Imap/Client/Socket.php"]
Apr 19 12:20:40 HORDE [error] [imp] Bad IMAP request: Error in IMAP
command LOGIN: Unknown command. [pid 7512 on line 3346 of
"/usr/share/php/Horde/Imap/Client/Socket.php"]
Apr 19 12:20:40 HORDE [error] [imp] IMAP server denied authentication.
[pid 7512 on line 393 of "/usr/share/php/Horde/Imap/Client/Socket.php"]
Apr 19 12:20:40 HORDE [error] [imp] IMAP server denied authentication.
for twilek [192.168.1.1] to {127.0.0.1:143 [imap]} [pid 7512 on line
64 of "/var/www/horde/imp/lib/Auth/imp.php"]
Apr 19 12:20:40 HORDE [notice] [imp] 192.168.1.1 Die Anmeldung ist
fehlgeschlagen, weil Sie Ihren Benutzernamen oder Ihr Passwort falsch
eingegeben haben. [pid 7512 on line 41 of
"/var/www/horde/imp/login.php"]
Apache log shows no errors