Hi, I use postfix with procmail and I sometimes (possibly 3 - 4 times a
day roughly) get an error such as:
Oct 10 10:30:30 toowong postfix/pipe[10817]: 6824B1FC5F1:
to=<user(_at_)mydomain(_dot_)com>, relay=procmail, delay=1000, status=bounced
(Command time limit exceeded: "/usr/bin/procmail". Command output:
procmail: Extraneous locallockfile ignored procmail: Extraneous
locallockfile ignored procmail: Extraneous locallockfile ignored
procmail: Extraneous locallockfile ignored procmail: Extraneous
locallockfile ignored )
The mail then bounces back to me, although the mail was actually
processed by procmail so I *think* it's failing on removing the lock file.
I'm sure it's got something to do with my rules, so here they are:
TIMEOUT=1960
LOGFILE=/tmp/procmail
:0
* ^To(_dot_)*(_at_)spam(_dot_)mydomain(_dot_)com
{
:0cw:
/var/spool/spam
:0i:
| /usr/bin/spam_learn.sh
}
:0
* ^To:(_dot_)*undeliverable(_at_)mydomain(_dot_)com
{
:0cw:
/var/spool/undeliverable
:0:
| /usr/bin/undeliverable.sh
}
:0
* ^To:(_dot_)*undeliverable(_at_)remove(_dot_)domain(_dot_)com
{
:0cw:
/var/spool/undeliverable
:0:
| /usr/bin/undeliverable.sh
}
:0w
* ^To:(_dot_)*expenses(_at_)accounts(_dot_)mydomain(_dot_)com
* ^Subject:[ \t]*\/[^ ].*
| sudo /usr/bin/ssh administrator(_at_)192(_dot_)168(_dot_)0(_dot_)3 "cmd /C
c:\\\\perl\\\\bin\\\\expenses.pl $MATCH"
:0w
* ^To:(_dot_)*expenses(_at_)ham(_dot_)mydomain(_dot_)com
* ^Subject:[ \t]*\/[^ ].*
| sudo /usr/bin/ssh administrator(_at_)192(_dot_)168(_dot_)0(_dot_)3 "cmd /C
c:\\\\perl\\\\bin\\\\expenses.pl $MATCH"
:0
* ^To:(_dot_)*unsubscribe(_at_)mydomain(_dot_)com
{
:0cw
! user(_at_)mydomain(_dot_)com
:0c:
/var/spool/unsubscribe
:0:
| /usr/bin/unsubscribe.sh
}
:0
* ^To:(_dot_)*unsubscribe(_at_)remove(_dot_)mydomain(_dot_)com
{
:0cw
! user(_at_)mydomain(_dot_)com
:0c:
/var/spool/unsubscribe
:0:
| /usr/bin/unsubscribe-internal.sh
}
:0:
* ^From:.*mydomain.com
* ^Subject:.*EzySolutions for SAP.*
| /usr/local/sbin/appointments.pl
:0:
* ^(To|From):.*mydomain.com
* !^To:(_dot_)*crm(_dot_)*(_at_)(_dot_)*mydomain(_dot_)com
* !^Subject:.*CRM:[0-9]+
* !^Subject:.*Cron.*
* !^Subject:.*SPAM.*
| /usr/local/sbin/emails.pl
I think it's the last rule that generates the lock file problem, as if I
specify to create a lockfile that I name, then I sometimes get:
Forcing lock on "/tmp/procmail.lock
Can anyone see anything wrong with those rules?
/usr/local/sbin/emails.pl does write to a file so that is why I'm using
a lock file for that section.
Thanks for any help.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail