6.0.0-alpha14
7/3/25

[#13594] Can't connect to local Dovecot over SSL any more
Summary Can't connect to local Dovecot over SSL any more
Queue IMP
Queue Version Git master
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester software-horde (at) interfasys (dot) ch
Created 09/22/2014 (3937 days ago)
Due
Updated 09/22/2014 (3937 days ago)
Assigned
Resolved 09/22/2014 (3937 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/22/2014 09:47:25 PM arjen+horde (at) de-korte (dot) org Comment #4 Reply to this comment
Alternatively, if you're using Dovecot and connect from localhost, set

     $servers['advanced']['secure'] = false;

in your imp/config/backends.local.php. Dovecot will accept unsecured 
connections from localhost by default.
09/22/2014 09:20:56 PM software-horde (at) interfasys (dot) ch Comment #3 Reply to this comment
09/22/2014 09:15:25 PM Michael Slusarz Comment #2
State ⇒ Not A Bug
Reply to this comment
09/22/2014 12:59:58 PM software-horde (at) interfasys (dot) ch Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Can't connect to local Dovecot over SSL any more
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Here is the log entry
2014-09-22T13:35:59+02:00 WARN: HORDE [imp] PHP ERROR: fgets(): SSL 
read operation timed out [pid 40124 on line 153 of 
"/usr/local/php54/lib/php/Horde/Imap/Client/Socket/Connection/Socket.php"]

I thought this might be due to some security tightening in Dovecot, 
but reversing the changes didn't help.
So it could be an Apache 2.4.10 or PHP 5.4.33 problem, but the log 
does not give enough information.

Horde connects from ::1 to the local Dovecot server
The config states that it should use SSL which is not necessary, but 
it's the default, so if this is a bug, then it might affect more people.

Were there any recent changes made to IMP regarding how it connects via SSL?



Saved Queries