Hello, Since we put the new Horde into production, more and more users are complaining about the following error 'The mail server does not support IMAP4rev1 (RFC 3501).' although the capability is always announced by the mail servers.
What we found so far is that for some reason, the session stores an empty capabilitiy list and therefore the error happens. We patched this by forcing a capability reload in this case, but this is not at all a clean way to do it. I appended the workaround patch hoping to give you a hint to this behaviour. kind regards, Claude Tompers -- Claude Tompers Ingénieur réseau et système Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473
--- Socket.php 2012-06-05 15:37:10.000000000 +0200
+++ Socket.php.orig 2012-06-05 15:35:58.000000000 +0200
@@ -478,11 +478,7 @@
// If we already have capability information, don't re-set with
// (possibly) limited information sent in the inital banner.
if (isset($this->_init['capability'])) {
- if (count($this->_init['capability']) === 0) {
- error_log(__FUNCTION__.': '.$this->_params['username'].' disabling cap setting but have empty list???');
- unset($this->_init['capability']);
- } else
- $this->_temp['no_cap'] = true;
+ $this->_temp['no_cap'] = true;
}
// Get greeting information. This is untagged so we need to specially
signature.asc
Description: OpenPGP digital signature
-- imp mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: imp-unsubscr...@lists.horde.org
