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	> 4.3.7: IMP H3 (4.3.7) Final does not work using comming dovecot version 2 > using imap acls as tested > > dovecot Timo Sirainen developer changed acl behavior, clients should be fixed > > more info > http://dovecot.org/list/dovecot/2010-April/048147.html > > slusarz@horde.org wrote > > > This works fine in IMP 5. The problem with IMP 4 is that c-client > doesn't support the CAPABILITY command so we have to use hackish ways > to work around it. > > You should open a ticket re: this issue on http://bugs.horde.org/ > > > meanwhile as workaround i found > > horde/imp does a check which seems to get workarounded by > > horde/lib/Horde/IMAP/ACL/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 = false; > } elseif (!isset($this- _caps['acl'])) { > / If we couldn't get the server's capability, we'll assume > ACL is > not supported for now. */ > > ----change---from---false---to---true > > $this- _supported = true; > > > > } else { > $this- _supported = true; > } > > the alternate workaround with dovecot > is setting manual imap capability list > didnt tested that yet >
Attachment
Watch this ticket