diff options
| -rw-r--r-- | tracker/Error_on_search_in_roundcube/comment_5_8d269a7cf3b5f938b70198b2f18af014._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/tracker/Error_on_search_in_roundcube/comment_5_8d269a7cf3b5f938b70198b2f18af014._comment b/tracker/Error_on_search_in_roundcube/comment_5_8d269a7cf3b5f938b70198b2f18af014._comment new file mode 100644 index 0000000..09b9d8a --- /dev/null +++ b/tracker/Error_on_search_in_roundcube/comment_5_8d269a7cf3b5f938b70198b2f18af014._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="guilhem" + avatar="http://cdn.libravatar.org/avatar/86d6cb4bde1ef88730b14ccad0414c28" + subject="comment 5" + date="2015-09-28T23:03:31Z" + content=""" +The IMAP connection used the default socket timeout (60s). I know some servers send back continuation responses (“+”) to keep the connection alive and avoid triggering the timeout, but I don't kown Dovecot 2.2.13 behaves regarding that. I changed the default socket timeout to 180s, could you try again? If that solves your problem, I think the proper solution would be to change to the socket options to use keepalive probes either at the TCP level or higher at the IMAP layer. +"""]] |