Tickets :: [#11413] Getting error he mail server does not support IMAP4rev1 (RFC 3501).

6.0.0-alpha14

7/1/25

Summary	Getting error he mail server does not support IMAP4rev1 (RFC 3501).
Queue	Horde Base
Queue Version	FRAMEWORK_4
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	steve (at) quorg (dot) org
Created	09/11/2012 (4676 days ago)
Due
Updated	10/15/2012 (4642 days ago)
Assigned	09/25/2012 (4662 days ago)
Resolved	10/15/2012 (4642 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/15/2012 08:47:35 PM	Git Commit	Comment #13	Reply to this comment
Changes have been made in Git (develop): commit 35ff92c72c6eae2e5bd8e61c26ff75bff7ec2462 Author: Michael M Slusarz <slusarz@horde.org> Date: Mon Oct 15 00:06:45 2012 -0600 [mms] Fix reinitializing a prior authenticated client object when the IMAP server subsequently becomes unavailable (~~Bug #11413~~). Conflicts: framework/Imap_Client/package.xml .../Imap_Client/lib/Horde/Imap/Client/Base.php \| 20 ++++++++++++-------- .../Imap_Client/lib/Horde/Imap/Client/Socket.php \| 4 +++- .../lib/Horde/Imap/Client/Socket/Pop3.php \| 2 +- framework/Imap_Client/package.xml \| 15 ++++++++++++++- 4 files changed, 30 insertions(+), 11 deletions(-) http://git.horde.org/horde-git/-/commit/35ff92c72c6eae2e5bd8e61c26ff75bff7ec2462

10/15/2012 07:06:28 PM	Michael Slusarz	Comment #12	Reply to this comment
This also fixed a very annoying issue when you do a logout and re-login with a Kolab backend. Actually... there is still an issue with this. I believe it has to do with session destruction. But it has nothing to do with this ticket.

10/15/2012 10:03:11 AM	Thomas Jarosch	Comment #11	Reply to this comment
This also fixed a very annoying issue when you do a logout and re-login with a Kolab backend. -> The Kolab backend always failed to properly re-authenticate to the IMAP server. Jan wasn't seeing this so I blamed my borked installation until now ;)

10/15/2012 06:36:55 AM	Git Commit	Comment #10	Reply to this comment
Changes have been made in Git (master): commit 35ff92c72c6eae2e5bd8e61c26ff75bff7ec2462 Author: Michael M Slusarz <slusarz@horde.org> Date: Mon Oct 15 00:06:45 2012 -0600 [mms] Fix reinitializing a prior authenticated client object when the IMAP server subsequently becomes unavailable (~~Bug #11413~~). Conflicts: framework/Imap_Client/package.xml .../Imap_Client/lib/Horde/Imap/Client/Base.php \| 20 ++++++++++++-------- .../Imap_Client/lib/Horde/Imap/Client/Socket.php \| 4 +++- .../lib/Horde/Imap/Client/Socket/Pop3.php \| 2 +- framework/Imap_Client/package.xml \| 15 ++++++++++++++- 4 files changed, 30 insertions(+), 11 deletions(-) http://git.horde.org/horde-git/-/commit/35ff92c72c6eae2e5bd8e61c26ff75bff7ec2462

10/15/2012 06:29:57 AM	Michael Slusarz	Comment #9 Version ⇒ FRAMEWORK_4 State ⇒ Resolved Assigned to Michael Slusarz	Reply to this comment
OK - I can confirm this happens, but ONLY if the master IMAP server goes down and IMP can continue to connect to an imapproxy server. The problem is that the IMAP client object does not fully reset itself when attempting to re-authenticate. As a (convoluted) result, the internal cached capability array becomes empty without any ability to re-populate this data once the IMAP server can be authenticated to again. Solution is to properly reset internal values to prevent this caching.

10/15/2012 06:27:14 AM	Git Commit	Comment #8	Reply to this comment
Changes have been made in Git (FRAMEWORK_4): commit 2f24da742294f8edabf4cd1284c32ef5db6d66f2 Author: Michael M Slusarz <slusarz@horde.org> Date: Mon Oct 15 00:06:45 2012 -0600 [mms] Fix reinitializing a prior authenticated client object when the IMAP server subsequently becomes unavailable (~~Bug #11413~~). .../Imap_Client/lib/Horde/Imap/Client/Base.php \| 20 ++++++++++++-------- .../Imap_Client/lib/Horde/Imap/Client/Socket.php \| 4 +++- .../lib/Horde/Imap/Client/Socket/Pop3.php \| 2 +- framework/Imap_Client/package.xml \| 4 ++-- 4 files changed, 18 insertions(+), 12 deletions(-) http://git.horde.org/horde-git/-/commit/2f24da742294f8edabf4cd1284c32ef5db6d66f2

09/26/2012 02:26:24 PM	Jan Schneider	Comment #7 State ⇒ Not A Bug	Reply to this comment
This happens if the IMAP server doesn't return an IMAP4REV1 capability. If this is intermittent, it's probably some sporadic issue with your IMAP server returning response. You can enable IMAP logging to see the communication. It's connecting to postfix. Not sure which version or which additions as I'm not in charge of the server. Postfix is not an IMAP server. But if you are not able to debug the server, there isn't much we can help you with anyway. But if it can't use IMAP4REV1 then surely it should just fall back to IMAP4 rather than stopping working entirely (I can't view the inbox etc). That's not how IMAP works. Talk to your mail server administrator.

09/26/2012 02:11:02 PM	steve (at) quorg (dot) org	Comment #6	Reply to this comment
This happens if the IMAP server doesn't return an IMAP4REV1 capability. If this is intermittent, it's probably some sporadic issue with your IMAP server returning response. You can enable IMAP logging to see the communication. It's connecting to postfix. Not sure which version or which additions as I'm not in charge of the server. But if it can't use IMAP4REV1 then surely it should just fall back to IMAP4 rather than stopping working entirely (I can't view the inbox etc).

09/25/2012 10:42:48 PM	Jan Schneider	Comment #5 State ⇒ Feedback	Reply to this comment
This happens if the IMAP server doesn't return an IMAP4REV1 capability. If this is intermittent, it's probably some sporadic issue with your IMAP server returning response. You can enable IMAP logging to see the communication.

09/11/2012 11:39:25 AM	steve (at) quorg (dot) org	Comment #4	Reply to this comment
Using imap proxy? Nope. Connecting directly to the server. Horde is not on the same host as the IMAP server though, but no proxy.

09/11/2012 11:36:25 AM	joao (dot) machado (at) co (dot) sapo (dot) pt	Comment #3	Reply to this comment
Using imap proxy? [Show Quoted Text - 12 lines][Hide Quoted Text] This is an intermittent bug and I'm afraid I can't find any pattern as to how to get it repeatably. When logged in, i will click on my inbox, or select a message from my inbox and I will get the following error: "The mail server does not support IMAP4rev1 (RFC 3501)." After this point, i can log out/back in and will still get it. Restarting firefox doesn't help. After a day or two it will seem to fix itself and I can read emails again. I have noticed this behaviour on Firefox 13-15 but not on Chrome.

09/11/2012 10:48:10 AM	steve (at) quorg (dot) org	Comment #2	Reply to this comment
OK, I can confirm that it happens in Chrome (v21) too.

09/11/2012 09:45:26 AM	steve (at) quorg (dot) org	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Due ⇒ 09/09/2012 Summary ⇒ Getting error he mail server does not support IMAP4rev1 (RFC 3501). Type ⇒ Bug Queue ⇒ Horde Base	Reply to this comment
This is an intermittent bug and I'm afraid I can't find any pattern as to how to get it repeatably. When logged in, i will click on my inbox, or select a message from my inbox and I will get the following error: "The mail server does not support IMAP4rev1 (RFC 3501)." After this point, i can log out/back in and will still get it. Restarting firefox doesn't help. After a day or two it will seem to fix itself and I can read emails again. I have noticed this behaviour on Firefox 13-15 but not on Chrome.