Andrew Schulman schreef:
I'm trying to use Avelsieve with Dovecot managesieve, to generate
sieve scripts for exim. This almost works, except for one thing:
Dovecot reports a fixed ManageSieve CAPABILITIES string, that includes
several caps (reject, imapflags, relational, regex, notify) that exim
doesn't support. The client (Avelsieve) dutifully copies those caps
into the sieve script, where exim chokes on them:
$ /usr/lib/sendmail -v -bf .forward <testmsg.mbox
Sender taken from "From " line
Return-path taken from "Return-path:" header line
Return-path = [EMAIL PROTECTED]
Sender = [EMAIL PROTECTED]
Recipient = [EMAIL PROTECTED]
Testing Sieve filter file ".forward"
fileinto `inbox'
Sieve error: unknown capability in line 9
The result from the user's point of view is that his/her filter script
doesn't work: all messages get filed into "inbox".
If managesieve included a configurable capabilities string, then we
could work around this problem and use it with exim.
I have thought about this. But, I came to the conclusion that in that
case the script needs to be verified by exim's sieve implementation and
not the CMU implementation dovecot currently uses. Otherwise, there is
no guarantee that an uploaded script actually compiles for exim as well.
This opens the possibility that scripts can be uploaded successfully,
but fail upon mail delivery without further notice to the user.
As of yet, I did not find a reliable way to execute the Exim binary and
subsequently extract any error messages from its output. Also,
alternatively, Exim's sieve implementation is not easily compiled into
an external program like managesieve. It has been more than a year since
I've looked at this alternative. So, I can give it another look in a few
weeks.
If you already have a full idea on how to do this, I'd be happy to hear
it. However, I do not think that just making the sieve capability string
configurable is a good solution to use Exim together with dovecot
managesieve.
Regards,
--
Stephan Bosch
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
