[Dovecot] sieve is broken in the latest revision
All the sudden messages filtered by sieve are delivered to folders named after the recipient instead of sticking to the rules and delivering the messages to the INBOX. Is this an intended change?
Instead of
Maildir/.INBOX
it goes to
Maildir/.user@domain.com
Cheers,
Olivier
All the sudden messages filtered by sieve are delivered to folders named after the recipient instead of sticking to the rules and delivering the messages to the INBOX. Is this an intended change?
Instead of
Maildir/.INBOX
it goes to
Maildir/.user@domain.com Sounds to me like you're using the latest version of Dovecot, but you didn't recompile Pigeonhole for it. Recently, a field was added to an internal structure of dovecot-lda that Sieve depends on. I can imagine
Op 15-9-2010 13:10, interfaSys sàrl schreef: that your Sieve is using the -a/-r argument of deliver-lda as an -m argument now.
If the problem persists after recompiling Pigeonhole you should elaborate more on your setup. The following information is then important:
- What are the exact versions/revisions of Dovecot and Pigeonhole (Sieve) you have installed?
- What is your Dovecot configuration (show output of dovecot -n)
- How are messages delivered? Via LDA or LMTP? If LDA: how is it invoked from your MTA?
Regards,
Stephan.
On 15/09/2010 12:23, Stephan Bosch wrote:
All the sudden messages filtered by sieve are delivered to folders named after the recipient instead of sticking to the rules and delivering the messages to the INBOX. Is this an intended change?
Instead of
Maildir/.INBOX
it goes to
Maildir/.user@domain.com Sounds to me like you're using the latest version of Dovecot, but you didn't recompile Pigeonhole for it. Recently, a field was added to an internal structure of dovecot-lda that Sieve depends on. I can imagine
Op 15-9-2010 13:10, interfaSys sàrl schreef: that your Sieve is using the -a/-r argument of deliver-lda as an -m argument now.
If the problem persists after recompiling Pigeonhole you should elaborate more on your setup. The following information is then important:
- What are the exact versions/revisions of Dovecot and Pigeonhole (Sieve) you have installed?
- What is your Dovecot configuration (show output of dovecot -n)
- How are messages delivered? Via LDA or LMTP? If LDA: how is it invoked from your MTA?
Regards,
Stephan.
Hello Stephan,
Indeed, I had not recompiled Pigeonhole because the server is unreachable. I've tried with the latest revision I had and it didn't help.
Is there a snapshot somewhere that would contain the necessary changes?
Cheers,
Olivier
On 15.9.2010, at 12.36, interfaSys sàrl wrote:
Sounds to me like you're using the latest version of Dovecot, but you didn't recompile Pigeonhole for it. Recently, a field was added to an internal structure of dovecot-lda that Sieve depends on. I can imagine that your Sieve is using the -a/-r argument of deliver-lda as an -m argument now.
Indeed, I had not recompiled Pigeonhole because the server is unreachable. I've tried with the latest revision I had and it didn't help.
Is there a snapshot somewhere that would contain the necessary changes?
There are no necessary changes. Simply recompiling should have helped.
Op 15-9-2010 13:36, interfaSys sàrl schreef:
Indeed, I had not recompiled Pigeonhole because the server is unreachable. I've tried with the latest revision I had and it didn't help. Server is down due to maintenance. It should have taken just one hour, but for some reason it is taking much longer than that.
Is there a snapshot somewhere that would contain the necessary changes?
There should be no need to download a new revision. A clean recompile should do the trick.
Regards,
Stephan.
On 15/09/2010 12:40, Stephan Bosch wrote:
Op 15-9-2010 13:36, interfaSys sàrl schreef:
Indeed, I had not recompiled Pigeonhole because the server is unreachable. I've tried with the latest revision I had and it didn't help. Server is down due to maintenance. It should have taken just one hour, but for some reason it is taking much longer than that.
Is there a snapshot somewhere that would contain the necessary changes?
There should be no need to download a new revision. A clean recompile should do the trick.
Regards,
Stephan.
I've just tried with v0.2.0 as well and it doesn't help. Messages are delivered to the user@domain.com folder.
It always worked until the latest revision of Dovecot (8b6b0412dc18).
Messages are delivered via LDA from Exim Here are some config lines:
managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date sieve = ~/.dovecot.sieve sieve_dir = ~/sieve protocols = imap pop3 sieve service managesieve-login { executable = managesieve-login inet_listener sieve { protocol = sieve service managesieve { executable = managesieve protocol = sieve unix_listener login/sieve { mail_plugins = $mail_plugins sieve
lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header =
Cheers,
Olivier
On 15/09/2010 12:40, Stephan Bosch wrote:
Op 15-9-2010 13:36, interfaSys sàrl schreef:
Indeed, I had not recompiled Pigeonhole because the server is unreachable. I've tried with the latest revision I had and it didn't help. Server is down due to maintenance. It should have taken just one hour, but for some reason it is taking much longer than that.
Is there a snapshot somewhere that would contain the necessary changes?
There should be no need to download a new revision. A clean recompile should do the trick.
Regards,
Stephan.
It's fixed. I apologize, I was linking against 2.0.2 instead of the latest revision... Thanks for the help.
Cheers,
Olivier
participants (3)
-
interfaSys sàrl
-
Stephan Bosch
-
Timo Sirainen