procmail
[Top] [All Lists]

Re: Invoking a program via procmail isn't working.

2005-08-22 14:21:42

On Aug 22, 2005, at 1:25 PM, Professional Software Engineering wrote:

At 12:10 2005-08-22 -0700, Bruce Johnson wrote:

I'm trying to process messages sent to an account,


So, the procmailrc content you posted is in a user's .procmailrc,  
not a
global .procmailrc?  Does this user have a valid login shell?


Yes.


 two parts we want
to keep the whole message, as well as parse the body of a message for
certain lines and do stuff based on that:

PMDIR=$HOME
MAILDIR=$HOME/mail   # all mailboxes are in mail/
LOGFILE=$PMDIR/procmail.log
LOG="--- Logging ${LOGFILE} for ${LOGNAME}, "


Add:
         VERBOSE=ON

To the stuff up there.


Ok.


:0
               * ^TO.*


That's a curious condition.  Mind translating to english what you  
think
this is really necessary for?


I want every mail sent to this user to go through the filter. This is  
the account our mail server AV software is sending 'virus found'  
messages to. For various reasons we want to keep a copy of all the  
messages, but the perl script is parsing out two lines of the  
message: the name of the virus found and the originating sender.

This was copied from an existing, known-to-work rule that forwarded a  
copy of every mail on to one person while retaining a copy locally; I  
think it was copied right out of the procmailex man pages.

Then I'm checking to see if they're from the local domain and if so  
we get a separate email with the info.



               {
                  :0 c
                    | perl $HOME/procvir.pl >> procvir.log


If you're going to write to something, you really should include the
locking flag on that rule.


The problem is that the program 'procvir.pl' is never running at all,
as far as I can tell.


What does your VERBOSE log say?  Is _perl_ in your path (as per the  
path
that procmail gets handed when it is invoked, not whatever your  
login shell
might ADD to the path when you login separatley).  For that matter,  
do you
HAVE a shell defined?

Actually perl shouldn't be there at all, the script is world  
executable, and has the perl path set:

#!/usr/bin/perl

But I wasn't getting anything out with it, so I threw the reference  
to perl in there.


--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs



____________________________________________________________
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