similar to: [re] patching dovecot for managesieve/sieve

Hi all, I am having real trouble when attempting to patch dovecot 1.2 to include the Pidgeonhole sieve support on my CentOS 5.6 x64 mail server. I am relatively new to the programming side of linux, but I am not having a lot of luck when trying to get this thing to compile. Here's what happens: [root at mail ~]# whereis dovecot dovecot: /usr/sbin/dovecot /etc/dovecot.conf /usr/lib/dovecot

Hi, we still run dovecot 1.2.17 and upgrading is not planed for some time. But I'm asked to install a sieve system to be used with SOGo soon. What do I have to install / configure? Is installing/configuring the dovecot-sieve-0.1.19 and dovecot-managesieve-0.11.13 enough? We still use mostly the default settings for imaps/pop3s. And of course configure SOGo. Thanks for any feedback.

Hi, On my Debian Squeeze server I installed Dovecot 1.2.16 from http://xi.rename-it.nl/debian/ and configured as follow: # dovecot -n # 1.2.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-110209 i686 Debian 6.0 ext3 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap sieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable:

Hello everyone, I'm fairly new to Dovecot, but I've gotten the majority of things working except for Sieve. I'm running Dovecot 1.2.9 coupled with Postfix and SpamAssassin all with a virtual domains setup. I am receiving mail and it is being processed by all the plugins that operate through Postfix. The quota configured in Dovecot appears to be working because my mail client shows

I'm integrating Sieve (the new one) and ManageSieve into wip/dovecot. Currently, this works as dovecot options because dovecot must be built before sieve can be configured and sieve must be built before managesieve can be configured/built. Now, the question arose what the long-term solution (in pkgsrc) should be. To my understanding, with dovecot 2.0, ManageSieve will no longer need to patch

Am 15.07.2015 um 07:24 schrieb Felix Zielcke: > Am Dienstag, den 14.07.2015, 22:44 +0200 schrieb Christian Theune: >> Hi, >> >> I?ve been a long-time user of Cyrus and started using sieve with >> Dovecot recently. A question that came up is: how do I access a >> users?s sieve scripts through managesieve without their credentials? >> Managesieve allows

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not

Hello Dovecot users, I hereby release new versions of the Sieve packages for the recently released Dovecot v1.2.0 (Congrats Timo!). Apart from small changes to make things compile with Dovecot again, a few other bugs were fixed as well. Unfortunately, the (FreeBSD-specific) 8kb script truncation bug remains. Although it is reported for Dovecot v1.1.16, I see no reason why it should not

Hi, I?ve been a long-time user of Cyrus and started using sieve with Dovecot recently. A question that came up is: how do I access a users?s sieve scripts through managesieve without their credentials? Managesieve allows separating authentation and the corresponding mailbox identification, right? That?s what I used with cyrus sieve all the time. :) I didn?t find documentation in the wiki or

Hi, Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical hosts. I recently noticed ".dovecot.sieve" and ".sieve/managesieve.sieve" are not replicating from one host to the other in either direction. Mail is having no trouble replicating on both hosts with dsync, it is only sieve files that are not replicating for unclear reasons. # doveconf -n host 1:

I see, If i need anything else i'll post, Thanks, > -----Original Message----- > From: Larry Rosenman [mailto:larryrtx at gmail.com] > Sent: segunda-feira, 13 de Outubro de 2014 21:05 > To: Jorge Bastos > Subject: Re: Compile dovecot with sieve/managesieve support > > Pigeonhole does ManageSieve as well...... > > On 10/13/14, Jorge Bastos <mysql.jorge at

Is it possible the Sieve/ManageSieve documentation on the Wiki can be cleaned up? It's incredibly confusing now. Some of the Sieve configuration information says certain options are deprecated, but then the example on how to configure it uses the deprecated options rather than what they *should* be now. More confusion is the sieve plugin configuration listing those same deprecated options,

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

Hello Dovecot users, Apart from unfinished development of the date extension, this is a set of bug-fix releases. A few portability issues were found, a few stupidities were fixed and the ManageSieve proxy now also works with TLS. Most notably, the include extension had an issue regarding the expansion of $HOME in the personal include path. I've built a project site at:

Hello Dovecot users, Apart from unfinished development of the date extension, this is a set of bug-fix releases. A few portability issues were found, a few stupidities were fixed and the ManageSieve proxy now also works with TLS. Most notably, the include extension had an issue regarding the expansion of $HOME in the personal include path. I've built a project site at:

Hi folks, I'm setting up a dovecot server with managesieve support. I'd like to offer spamfiltering through a Sieve script to my users by default, but still allow them to modify the filtering rules through Managesieve. I found the sieve_global_path configuration option, which seems perfect for what I want. I can configure a default script there, which will work for all users until they

I'm trying to integrate both the new sieve implementation and managesieve into pkgsrc. Managesieve seems to need some dovecot libraries that dovecot doesn't install (lib-storage/libstorage.a, lib-auth/libauth.a, lib-imap/libimap.a, lib-index/libindex.a, lib-mail/libmail.a, lib-charset/libcharset.a, lib-dict/libdict.a and lib-charset/libcharset.a). There seems to be no provision in pkgsrc

Hi, this is my configuration # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.1 (Santiago) ext4 auth_debug = yes auth_master_user_separator = * auth_username_format = %Lu auth_verbose = yes disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting =

Hello mailinglist-subscribers, i have an issue with the managesieve / sieve plugin in dovecot. We use roundcube as webmailer and if i define a new filter to move incoming mails directly into a subfolder i get the following sieve-code: require ["fileinto","imap4flags"]; # rule:[mail into folder] if allof (header :contains "from" "sender at domain.org") {