Tickets :: Comment on [#9058] IMP ACL - ACL capability may not be available until after login.

* Your Email Address
* Spam protection	Enter the letters below: ._. __ .__.._.. . \| / `[__] \| \|__\| _\|_\__.\| \|_\|_\| \|
Comment	>>>> http://comments.gmane.org/gmane.mail.imap.dovecot/47967 >>> >>> This is not the correct way to fix. >>> >>> And this code does work, because it has been tested by at least two >>> different developers. So the question is why is it not working on >>> your system, and you are the only one in the position to help us out >>> with that. >> >> sorry i cant find something >> in horde log , ( full error ph log is enabled ) but i will help to >> find out whats going wrong >> describe how to debug the problem >> >> acl imap work on my setup with thunderbird and acl extension >> so its not a server problem,the server entries were not changed at >> upgrade so the only logical solution >> seems that the problem is on the client side > > i did this as temp workaround in rfc2086.php > > > if (substr($this->_params['protocol'], 0, 4) != 'imap') { > /* No point in going any further if it's not an IMAP server. / > // $this->_error = PEAR::raiseError(_("Only IMAP servers > support shared folders.")); > $this->_supported = true; > } > > //else { > // $this->_caps = $this->_getCapability(); > // if (is_a($this->_caps, 'PEAR_Error')) { > // $this->_error = $this->_caps; > // return; > //} > > / If we couldn't get the server's capability, assume ACL is > * not supported for now. */ > $this->_supported = true; > //} > > as i have loadbalanced servers i will let stay the other install in > orginal, so testing > is no Problem with the orginal code be easy switching servers
Attachment
Watch this ticket

Saved Queries