Can you elaborate a bit on why this would be unwise? All procmail is doing right now (for me) is acting as a content filter, shared by all users and running suid... It hands the messages off to Dovecot for delivery.
I don't see the difference in doing this from a content_filter perspective. What am I missing (aside form efficiency of process)? > On Nov 10, 2015, at 07:41, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote: > > On Mon, Nov 09, 2015 at 11:02:21PM -0800, Vicki Brown wrote: > >> I am using Mac OS X Server. OS X Server uses postfix with dovecot set as >> mail_transport. >> >> I want to add procmail to the mix. I cannot use the (typical) >> mailbox_command = procmail -a "$EXTENSION" >> >> because >> mailbox_transport = dovecot >> >> overrides any mailbox_command parameter and it is NOT Possible to change, >> remove, or otherwise vary the >> mailbox_transport on OS X server. >> >> I'm thinking I should be able to set up a content_filter for procmail, >> but I've found nothing online to tell me if this is possible or how to >> declare it. > > With a great deal of care it may well be possible to configure > procmail as a "simple" content_filter (shared by all users and > running as some system account), that reinjects mail back into the > Postfix queue for delivery. In practice, I think this is unwise, > and would not recommend it. This is not what procmail is designed > to do. > > -- > Viktor. -- Vicki cfcl.com/vlb twitter.com/vlb
