Tickets :: Comment on [#12129] Sieve example config does not work with Dovecot 2.1.15

* Your Email Address
* Spam protection	Enter the letters below: . . __ .___. __ . . \| \|/ ` _/ / `\|\ \| \|/\\|\__../__.\__.\| \\|
Comment	> I haven't attempted this setup before, so I don't know how far back > the issue goes. Lots online about setups up to mid-2011 or so, > involving H3/4 and dovecot-1x, but nothing for H5 / dovecot-2.x (and > no documentation that I can find). > > /ingo/conf/backends.local.php as follows: > > $backends['imap']['disabled'] = true; > $backends['sieve']['disabled'] = false; > > $backends['sieve']['params']['usetls'] = false; > $backends['sieve']['params']['debug'] = true; > $backends['sieve']['scriptparams']['utf8'] = true; > > I have logging at DEBUG and see nothing to indicate an attempt to > contact the managesieve process, likewise in the dovecot log (whereas > it's evident when I probe it with netcat). > > In Configuration > Ingo, I've tried both Preferences and SQL storage > backends: no difference. Also I've tried setting the configs above > directly in backends.php, still no joy. > > The auth parameter in Horde config is set to use Imp for login (which > in turn uses IMAP login to the same dovecot instance). Everything > else I can think of is pretty standard. On Gentoo but using the pear > install method (clean H5 install). > > Happy to provide whatever further info requested, just ask.
Attachment
Watch this ticket