On 08:50:42 2007-09-27 Lars Stavholm [EMAIL PROTECTED] wrote:
Daniel L. Miller wrote:
Charles Marcus wrote:
On 9/26/2007, Bill Landry ([EMAIL PROTECTED]) wrote:
These folders could easily be create dynamically by maildrop, if
used as your MDA. I use it as my MDA between Postfix and
From dovecot.conf..
# Space separated list of wanted authentication mechanisms:
# plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi
# NOTE: See also disable_plaintext_auth setting.
mechanisms = cram-md5 plain login
#
What is your setting in dovecot-sql.conf?
On Sun, 2007-09-09 at 17:56 +0400, Gregory Mokhin wrote:
deliver([EMAIL PROTECTED]): Info: cmusieve: Using mailbox: test
deliver([EMAIL PROTECTED]): Info: cmusieve: Using username: [EMAIL PROTECTED]
deliver([EMAIL PROTECTED]): Info: cmusieve: Using sieve path:
/home/vmail/.dovecot.sieve
I guess it depends on what your Sieve code looks like? Or does it give
the same error even if your script is only keep;?
It doesn't depend on the script. Even the simplest script stop; gives
this error. I added two debug strings to cmusieve_deliver_mail in
cmusieve-plugin.c:
if (getenv(DEBUG)
Steffen Kaiser wrote:
Any idea how to fix that?
Second:
When you remove the compiled Sieve script, is it re-created by deliver?
I have the same problem with the same config myself. No evidence that
the script is being compiled automatically. If I remove the
sieve=path global setting from
Hello,
I'm using dovecot 1.0.3 and Dovecot Sieve plugin 1.0.2. Sieve script works
fine with normal addresses, like [EMAIL PROTECTED], and messages marked with
X-Spam-Flag: YES are delivered directly to INBOX.Spam.
To make deliver understand recipient_delimiter I tried two methods, the
first one
