Re: [Dovecot] simultaneous scripts not running via sieve_before
Thanks for the advise - it worked a treat!
Glad to finally have this sieve stuff under control, after weeks of trying to
get it working :)
From: Stephan Bosch
To: Duane Hill
Cc: dovecot@dovecot.org
Sent: Tuesday, 13 December 2011 3:25 AM
Subject: Re: [Dovecot] simultaneous scripts not running via sieve_before
Op 12/12/2011 2:57 PM, Duane Hill schreef:
> On Monday, December 12, 2011 at 13:02:05 UTC, scott_the_music...@yahoo.com.au
> confabulated:
>> protocol lda {
>> mail_plugins = sieve quota
>> sieve=~/.dovecot.sieve
>> sieve_extentions = +include
>> sieve_dir=~/sieve
>> sieve_before = /home/%u/sieve/redirect.svbin
>> sieve_global_path = /etc/globalsieverc.svbin
>> [/code]
> sieve_before and sieve_after are directories where extra scripts are
> run sequentially before user scripts and after user scripts. See:
>
> http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration
It can be a file, but then it must point to the sieve script (in this case
redirect.sieve) and not to the compiled binary (redirect.svbin in this case).
Regards,
Stephan.
[Dovecot] simultaneous scripts not running via sieve_before
Hi again everyone,
So I've finally got sieve integration happening on my REHL Postfix/Dovecot
server, with private user scripts happily running when users create them. (we
user SquirrelMail, so the avelsieve plugin runs the sieve integration).
Now I'd like to utilise additional per-user scripts (probably via
sieve_before), but I've not been able to get my additional scripts to execute.
I am doing the following:
a) getting avelsieve to write my redirect script (ie. logging on as user,
completing private script wizard, and activating it)
b) compiling .dovecot.sieve with sievec
c) copying the resultant .dovecot.svbin to sieve/ directory (and renaming it eg
redirect.svbin
still, it appears that each /home/%u/.dovecot.sieve file is the only one taking
effect. Any thoughts on how to make the other ones active? (The idea behind
this is to automatically forward all of joeuser@mydomain's incoming mail to
somewhere like joeusersbac...@gmail.com, for backup reasons. One day, I'll work
out how to configure postfix to do this for all outgoing email too, but that's
for another day :)
Below are what my .conf files look like. Thanks in advance,
Scott
/etc/dovecot.conf:
[code]
protocols = imap imaps managesieve
listen = *
protocol imap {
#mail_plugins = sieve quota
}
##
## ManageSieve specific settings
##
protocol managesieve {
# debugging
mail_debug = yes
#login_executable = /usr/libexec/dovecot/managesieve-login
#mail_executable = /usr/libexec/dovecot/managesieve
#managesieve_max_line_length = 65536
#managesieve_logout_format = bytes ( in=%i : out=%o )
#managesieve_implementation_string = Cyrus timsieved v2.2.13
}
protocol lda {
mail_plugins = sieve quota
sieve=~/.dovecot.sieve
sieve_extentions = +include
sieve_dir=~/sieve
sieve_before = /home/%u/sieve/redirect.svbin
sieve_global_path = /etc/globalsieverc.svbin
[/code]
[Dovecot] [re] patching dovecot for managesieve/sieve
My apologies for the repost yesterday; it was not intentional. I was attempting to post a followup from my mobile, when something went awry with the editing options on my phone. Anyway.. I have managed to download and compile my own patched dovecot/dovecot-sieve/dovecot-managesieve modules from scratch, with Thanks to this page hardc0l2e.wordpress.com/2010/02/26/managesieve-with-dovecot-on-centos-5-4/ But when I run http://mydomain.com/src/configtest.php , I am still getting the following rather non-descriptive error: "I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=ManageSieve) is bad?" Where else can I look to resolve this? should managesieve show up as its own /etc/init.d service? Or does dovecot simply control it? How can I confirm that deliver is being used as my LDA? Thanks again, Scott
Re: [Dovecot] patching dovecot for sieve/managesieve support, centos 5.6?
- Forwarded Message - From: Scott Lewis To: "dovecot@dovecot.org" Sent: Thursday, 3 November 2011 4:31 PM Subject: patching dovecot for sieve/managesieve support, centos 5.6? 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@mail ~]# whereis dovecot dovecot: /usr/sbin/dovecot /etc/dovecot.conf /usr/lib/dovecot /usr/libexec/dovecot /usr/share/man/man8/dovecot.8.gz [root@mail dovecot-1.2-sieve-0.1.19]# ./configure --with-dovecot=/usr/lib/dovecot ... checking whether to build static libraries... yes dovecot-config not found from /usr/lib/dovecot, use --with-dovecot=PATH to give path to compiled Dovecot sources or to a directory with the installed dovecot-config file. configure: error: dovecot-config not found -- I get this message regardless of whether I set --with-dovecot as /usr/sbin/dovecot, or /etc, or /usr/libexec/dovecot. I have SquirrelMail 1.4.22 running, and the avelsieve front-end seems happy enough. when I visit https://mail.mydomain.com/src/configtest.php, I get: Avelsieve plugin details: backend = ManageSieve ERROR: I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=Managesieve) is bad? thanks in advance!
[Dovecot] patching dovecot for sieve/managesieve support, centos 5.6?
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@mail ~]# whereis dovecot dovecot: /usr/sbin/dovecot /etc/dovecot.conf /usr/lib/dovecot /usr/libexec/dovecot /usr/share/man/man8/dovecot.8.gz [root@mail dovecot-1.2-sieve-0.1.19]# ./configure --with-dovecot=/usr/lib/dovecot ... checking whether to build static libraries... yes dovecot-config not found from /usr/lib/dovecot, use --with-dovecot=PATH to give path to compiled Dovecot sources or to a directory with the installed dovecot-config file. configure: error: dovecot-config not found -- I get this message regardless of whether I set --with-dovecot as /usr/sbin/dovecot, or /etc, or /usr/libexec/dovecot. I have SquirrelMail 1.4.22 running, and the avelsieve front-end seems happy enough. when I visit https://mail.mydomain.com/src/configtest.php, I get: Avelsieve plugin details: backend = ManageSieve ERROR: I could not determine the capabilities for Sieve Mail Filtering. Perhaps connectivity with ManageSieve server (if backend=Managesieve) is bad? thanks in advance!
