On Thu, 19 Aug 2010 04:02:32 +0200, fakessh fakessh@fakessh.eu wrote:
On Wed, 18 Aug 2010 12:51:33 -0700, Kaz Kylheku kaz@kylheku.com wrote:
pysieved set up in /etc/inetd.conf setup
[ ... ]
hi all I never managed to pull pysieved
I use managesieve directly.
Hi fakessh,
The Roundcube managesieve plugin needs to talk to a managesieve server on port 2000. (I've looked at the code and didn't find any evidence of any capability of managing script storage directly, without the protocol. Maybe I didn't look hard enough?)
The pysieved program provides that server. It has has plugins of its own for different kinds of authentication and storage. My e-mail accounts are real system accounts, so I use the PAM authentication plugin, and the Exim storage model.
So with this setup my users are able to control Exim filters from the Roundcube UI.
I think this is probably the best solution for people who want to stick with their Exim setup, at least until Exim integrates the managesieve protocol.
managesieve is hard coded in the config for dovecot
That may be, but with a little configuring, the sieve scripts generated by Roundcube seem work fine in a .forward file used by Exim. (BTW, pysieved actually manages .forward as a symbolic link to the currently active filter. The filters are stored in a subdirectory of the user's home).
I've been reading that the Exim sieve implementation has some limitations compared to dovecot; I will probably run into these sooner or later.
I hope that this enlightened you
Not really; I already googled up that you can get an nice sieve implementation with Dovecot. I wanted to get it working with Exim. I don't want to risk a working, live e-mail set up by switching to a whole other MTA, that's all.
List info: http://lists.roundcube.net/users/ BT/9b404e9e