On Mon, Jul 23, 2001 at 10:09:29AM +0100, Marcus Williams wrote:
> (1) By putting procmail delivery recipes in the .qmail-<user> files
> [...] vpopmail (or at least vdelivermail) will not be used as the
> delivery method [...]
... unless the receipes send messages on to it, as you say below.
> (2) [from a long series of searches on google when I wanted to do
> something similar] You can put procmail in front of the vdelivermail
> line in you .qmail-default so your procmail scripts act on everything
> coming into the domain and then pipes mail onward to vdelivermail. Use
> a line like:
>
> | preline procmail -m /path/to/procmailrc |
> /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
>
> To do this you have to get your procmailrc file to deliver to stdout
> by default by adding a line like:
>
> DEFAULT="|"
>
> to your procmailrc file. However, this goes strangely wrong if your
> procmail recipes are non-delivering (ie they put an incoming mail in a
> folder and then drop out of procmail) as the procmail process wont
> then pipe a mail onwards down to vdelivermail. Vdelivermail then goes
> on to deliver an empty mail to the user - effectively its been given
> an empty pipe. (This is fairly easy to fix by patching vpopmail).
How about using just
|preline procmail -m /path/to/procmailrc
in .qmail-default and calling vdelivermail from individual procmail
recipes, possibly using DEFAULT? That way, vdelivermail need't be
started for recipes with nothing to send to it. (I'm not a procmail
user, so I may be missing something about how it operates.)
hope this helps,
--
Daniel Biddle <[EMAIL PROTECTED]>
