On Fri, Jul 30, 2010 at 7:08 AM, CT Guy
<procmail(_at_)websites(_dot_)teamhendricks(_dot_)com> wrote:
Did anyone have any suggestions on this recipe?
Regarding the perl warning:
Do you happen to be running CentOS or a similar RPM-based system that
automatically installs package updates?
There was a change recently to one of the packages on which
SpamAssassin depends, which causes the warning about SPF.pm that
you're seeing in your log. I don't recall the exact details, it was
discussed on one or both of the spamaassassin and centos mailing
lists.
Regarding the messages going to /dev/null:
Based on your procmailrc and the earlier less-verbose log I'd say that
the most likely source of the problem is your siteadmin-blacklist.txt
file. Unless we're still not seeing your entire recipe set, that's
the only rule that stores into /dev/null based on something external
to procmailrc that may have changed.
Regarding SHELLMETAS:
It isn't clear how procmail is designed to behave when this is unset.
It may mean that procmail should never pass external commands through
a shell, or it may mean that it always should. In any case unsetting
it is very likely to change the way tests such as [ -s ... ] and fgrep
are executed, which might alter the way they are logged but might also
alter their success or failure.
Putting VERBOSE=YES
into the recipe causes bounceback fail messages to the sender.
That's because you should not assign VERBOSE until after you have
assigned to LOGFILE. In fact LOGFILE should be set as early as
possible. During mail delivery, stderr is captured and sent back as a
bounce, as you've noticed.
____________________________________________________________
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