On Tue, Apr 23, 2002 at 11:39:45AM -0600, Scott M Likens wrote:
> Out of Curiosity does it actually run procmail at all?
>
> Because i have the same exact thing and guess what. The mail_transport =
> cyrus takes priority and kicks out procmail. But i see you changed your
> master.cf does procmail know how to deliver properly to cyrus? and if so
> how?
There is more than one way to run cyrus with procmail. I am using it since
years with postfix. That's my entry in master.cf
cyrusp unix - n n - - pipe
user=cyrus:mail argv=/usr/bin/procmail -p /etc/cyrus/procmailrc
LOGNAME=${user} EXTENSION=${extension} RECIP=${recipient}
main.cf:
mailbox_transport = cyrusp
You can create a recipe directory for your cyrus users like
/var/cyrus/rc
The main procmailrc file /etc/cyrus/procmailrc contains something like
HOME=/var/cyrus/rc
DELIVERMAIL=/usr/local/imap/bin/deliver
INCLUDERC=$HOME/rc/$LOGNAME/procmail
The procmail file named by INCLUDERC contains the individual user recipes.
e. g.
:0 H
* ^TOpostfix-users@
| $DELIVERMAIL -a $LOGNAME -m user.$LOGNAME.lists.postfix
> >> If you use Cyrus you must loose procmail. Sorry no ifs ands or buts.
procmail isn't supported by the cyrus project. That's all. But it works
nevertheless.
The main advantage of sieve (simple and not prune to dangerous command
calls) can be achieved with a web interface letting users only create
simple procmail recipes. If you are interested you can try vfilter at
ftp://ftp.pure.ch/pub/filter
Werner
