procmail
[Top] [All Lists]

Re: filtering not working

2003-05-22 18:07:56
thanks for the tips. I finally found out why. Verbose logging really helps.
the test directory that i create owned by root.

thanks again

mike

----- Original Message -----
From: "Professional Software Engineering" 
<PSE-L(_at_)mail(_dot_)professional(_dot_)org>
To: <procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE>
Sent: Thursday, May 22, 2003 4:00 PM
Subject: Re: filtering not working


At 15:06 2003-05-22 +0800, Michael P. Carel wrote:

have a problem here in redhat 7.3 procmail,

It'd be loads better to indicate the version of procmail, rather than your
OS distribution version.  I assure you that the average contributor here
doesn't follow which version of procmail is distributed with any given
version of a distribution (or for that matter, necessarily knows what the
current release of any given distro is, much less the version that would
be
packaged with an outdated one).  Of all the distros, RedHat is perhaps the
most puzzling, since they've had a track record of including betas in some
distros.

 my filtering doesnt work. heres
my config:

.forward

"|exec /usr/bin/procmail -f- || exit 75 #mikecarel"

Have you confirmed the binary path as valid?

There are other, perhaps somewhat more desireable .forward invocations you
can use.  One fairly bulletproof one is on the page linked in my .sig.

.procmailrc

VERBOSE=no
MAILDIR=/home/mikecarel/mail

:0:
* ^Subject:.test
test

that regexp dot means 'exactly one of anything'.  So, unless your subject
has just one tab or space after the colon, this isn't necessarily going to
match.  For people looking for "test" at the beginning of a subject, the
expression is usually:

:0:
* ^Subject:[    ]*test
test

Where the brackets contain a space and a tab.  This better handles
variations in MUAs and the typing of individual users.

Can anyone help?

Enable a logfile and VERBOSE logging (which, for some reason, I see you
EXPLICITLY disable)?  Read the VERBOSE logfile?

If that fails to provide clues, try following the link in my sig and
download "procdiag", read the script source, and then execute it and
examine the output.  The most common newbie mistakes are issues with file
permissions.

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer:
<http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the
list.


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>