"Christopher Porreca" <[EMAIL PROTECTED]> wrote:
>
>When sending a message it takes some time before it gets reported into my
>maillog, which was not an issue yesterday.
Sounds like your "trigger" is hosed. How long is "some time"?
>I have also noticed the
>following from ProcMail:
>
>May 13 09:18:19 newman qmail: 926601499.074869 delivery 557041: success:
>procmail:_Couldn't_create_"/var/spool/mail/bobb"/did_0+0+1/
You've got two problems here. First is that procmail is trying to
deliver to /var/spool/mail. Bobb needs to modify his .procmailrc to
deliver to the right place, e.g., tack this onto the end:
:0:
$HOME/Mailbox
The second problem is that procmail doesn't return an exit status that
qmail interprets as an error, so messages are going into the bit
bucket.
I use a procmail wrapper by Phillip Hands, slightly modified for my
system:
#!/bin/sh
# Copyright (c) 1998 Software in the Public Interest <http://www.debian.org/>
# Written by Philip Hands <[EMAIL PROTECTED]>. Distributed under the GNU GPL
# $Id: qmail-procmail,v 1.2 1998/03/24 19:31:27 phil Exp $
# modified by Dave Sill
/var/qmail/bin/preline /usr/local/bin/procmail $* && exit 0
# check if procmail returned EX_TEMPFAIL (75)
[ $? = 75 ] && exit 111
# otherwise return a permanent error
exit 100
>I have raised concurrencylocal from 70 -> 150 yesterday, and
>concurrencyremote from 90 -> 200. I rarely see more than one of each
>qmail-local and qmail-remote processes running at one time...
If you're not hitting the limit, raising it won't help. :-)
-Dave
