[Tickets #12129] Sieve example config does not work with Dovecot 2.1.15
noreply at bugs.horde.org
noreply at bugs.horde.org
Tue Mar 19 17:38:31 UTC 2013
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/12129
------------------------------------------------------------------------------
Ticket | 12129
Created By | bugs.horde.org at headbank.co.uk
Summary | Sieve example config does not work with Dovecot 2.1.15
Queue | Ingo
Version | 3.0.1
Type | Bug
State | Unconfirmed
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
bugs.horde.org at headbank.co.uk (2013-03-19 17:38) wrote:
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.
More information about the bugs
mailing list