[Dovecot] System-wide sieve script?
In the dovecot LDA documentation, it mentions having sieve scripts
located in ~/.dovecot.sieve, which works great for per-user sieve code.
I was trying to find out if there was a system-wide sieve script (maybe
/etc/dovecot.sieve?) that would hopefully be run first, followed by any
per-user sieve code.
Anyone know if this is already possible, or if not, if there are any plans to implement this?
I'm assuming one could make a kludgey fix by having every .dovecot.sieve include a system-wide file, but that would allow a user to remove that "include" if they choose. I'd like to have a centrally controlled, immutable set of rules that all mail goes through.
If I missed something in the wiki or archives, I offer my apologies in advance.
Thanks!
-Ty!
On Wed, 2006-09-27 at 16:17 -0600, Ty! Boyack wrote:
In the dovecot LDA documentation, it mentions having sieve scripts located in ~/.dovecot.sieve, which works great for per-user sieve code.
I was trying to find out if there was a system-wide sieve script (maybe /etc/dovecot.sieve?) that would hopefully be run first, followed by any per-user sieve code.
Hello,
you can do this
lda {
...
# If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path =
...
}
in dovecot.conf. If a recipent sieve script is not present the global script will be. Personally I find this feature almost useless.
Anyone know if this is already possible, or if not, if there are any plans to implement this?
Sometime ago I made a feature request about having system-wide/domainwide/global scripts and executing them in a chain. Lookup my "LDA Sieve feature request" thread in the mailing-list archives. Basically objections were raised about how this should behave exactely. I did not have the time to continue thinking about that at the time. Maybe we can resume discussion on the logic and eventually come up with some scheme which makes sense to propose Timo for implementation.
I'm assuming one could make a kludgey fix by having every .dovecot.sieve include a system-wide file, but that would allow a user to remove that "include" if they choose. I'd like to have a centrally controlled, immutable set of rules that all mail goes through.
I thought about this too and this is doable if you manage your scripts through Horde Ingo, IIRC. But this is ugly at best. I would like to be able to put this into dovecot.conf too.
If I missed something in the wiki or archives, I offer my apologies in advance.
You did ;)
ciao
Luca
On Thu, 2006-09-28 at 01:03 +0200, Luca Corti wrote:
All work and no play makes Luca a dull boy ;)
in dovecot.conf. If a recipent sieve script is not present the global script will be. Personally I find this feature almost useless. ^^^ run
Sometime ago I made a feature request about having system-wide/domainwide/global scripts and executing them in a chain. ^^^^^^ per-user
ciao
Luca
Thanks, Luca!
I didn't mention very clearly that I need BOTH a system-wide and user script to run in some sort of chained fashion, as you pointed out. I had seen the global_script_path option, but agree that running the system wide script ONLY if the user script doesn't exist removes a lot of the flexibility that can be achieved with chained scripts, although it does provide a nice safety catch for missing user scripts. In our environment, it simply does not achieve what we need without some sort of chain.
I will go read your past thread to catch up on people's ideas of how this "should" work. Glad to hear this is already on the radar - I'll return when I'm up to speed with the community ;-)
-Ty!
Luca Corti wrote:
On Wed, 2006-09-27 at 16:17 -0600, Ty! Boyack wrote:
In the dovecot LDA documentation, it mentions having sieve scripts located in ~/.dovecot.sieve, which works great for per-user sieve code.
I was trying to find out if there was a system-wide sieve script (maybe /etc/dovecot.sieve?) that would hopefully be run first, followed by any per-user sieve code.Hello,
you can do this
lda {
...
# If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path =
...
}
in dovecot.conf. If a recipent sieve script is not present the global script will be. Personally I find this feature almost useless.
Anyone know if this is already possible, or if not, if there are any plans to implement this?
Sometime ago I made a feature request about having system-wide/domainwide/global scripts and executing them in a chain. Lookup my "LDA Sieve feature request" thread in the mailing-list archives. Basically objections were raised about how this should behave exactely. I did not have the time to continue thinking about that at the time. Maybe we can resume discussion on the logic and eventually come up with some scheme which makes sense to propose Timo for implementation.
I'm assuming one could make a kludgey fix by having every .dovecot.sieve include a system-wide file, but that would allow a user to remove that "include" if they choose. I'd like to have a centrally controlled, immutable set of rules that all mail goes through.
I thought about this too and this is doable if you manage your scripts through Horde Ingo, IIRC. But this is ugly at best. I would like to be able to put this into dovecot.conf too.
If I missed something in the wiki or archives, I offer my apologies in advance.
You did ;)
ciao
Luca
I have a command string
ssh dad@frank /usr/bin/imapd ./Maildir 2> /dev/null
that expects /usr/bin/imapd to exist to pass mail to the imap server but I can't find how to replicate the functionality in dovecot. Is it possible to wrapper dovecot to reproduce the functionality? Or is there another technique?
Lats
On Mon, 2006-10-16 at 20:12 +1000, lats wrote:
I have a command string
ssh dad@frank /usr/bin/imapd ./Maildir 2> /dev/null
that expects /usr/bin/imapd to exist to pass mail to the imap server but I can't find how to replicate the functionality in dovecot. Is it possible to wrapper dovecot to reproduce the functionality? Or is there another technique?
/usr/sbin/dovecot --exec-mail imap
johannes
On Mon, 2006-10-16 at 20:12 +1000, lats wrote:
I have a command string
ssh dad@frank /usr/bin/imapd ./Maildir 2> /dev/null
that expects /usr/bin/imapd to exist to pass mail to the imap server but I can't find how to replicate the functionality in dovecot. Is it possible to wrapper dovecot to reproduce the functionality? Or is there another technique?
/usr/sbin/dovecot --exec-mail imap
johannes
Thanks for that, I have just tried it and get the following:
/usr/sbin/dovecot --exec-mail imap Usage: dovecot [-F] [-c <config file>] Fatal: Unknown argument: --exec-mail
lats
On Mon, 2006-10-16 at 20:58 +1000, Jeff Latimer wrote:
/usr/sbin/dovecot --exec-mail imap Usage: dovecot [-F] [-c <config file>] Fatal: Unknown argument: --exec-mail
upgrade to 1.0, 0.99x is no longer supported.
johannes
participants (5)
-
Jeff Latimer
-
Johannes Berg
-
lats
-
Luca Corti
-
Ty! Boyack