On Wed, 11 Dec 2002, Professional Software Engineering wrote:
I'm rather fond of specifying the base directory when specifying paths,
because I get consistent results that way.
I agree that it's generally a good idea, but in this particular case I
don't think it's a problem. After all, I am getting log results even with
the relative directory path. However, I may try specifying the full path
if other more likely solutions fail.
Well, assuming the Cc: you claim existed was actually there, this should
have matched. I ran it in a sandbox with a constructed message and it
worked just fine. Perhaps you have a linefeed problem in the rcfile?
...
How do you edit your procmailrc file? Did it pass through a windowz box?
I'm mostly using vim 6.1.165 from the 'vim-enhanced-6.1-14' RPM from Red
Hat. I say "mostly" because one or two edits were performed with Pico 4.2
from the 'pine-4.44-13' RPM from Red Hat.
Just for kicks, I copy & pasted the text from my existing .procmailrc file
to a new .procmailrc file created from scratch using only vim. Still no
luck.
Try prefixing the openldap recipe (or position it above all your filing
recipes) with:
:0
* 1^0 ^Cc:\/.*
* 1^0 ^To:\/.*
{ }
(this will emit the matches to the verbose log, and handles either or both
headers appearing There is a space within the braces - without it, you'll
end up writing to a file named "{}".)
Then, throw the message at it again and check the log.
Thanks for the suggestion, but I'm a little unclear on how to implement
it. Would my procmailrc read (in part) as follows?
[...begin partial quote...]
:0
* 1^0 ^Cc:\/.*
* 1^0 ^To:\/.*
{ }
:0:
* ^X-Spam-Flag.*YES
mail/spam
[...end partial quote...]
(By the way, it'd sure be nice if VERBOSE=yes was a bit more verbose.
There's not too much helpful information on the logfile even with the
VERBOSE flag set.)
Each condition matching or not matching, and if you used scoring, the
individual scores, plus lockfile activity, and includerc activity, gets
logged.. What more are you expecting it to log? Cyclic parsing of
regexps-in-progress? Commentary on recipe efficiency?
I suppose I should have said, "There's not enough helfpul information...".
Minimally I'd like to see the exact time & date of each operation, as well
as having the option to see which files were touched (read from or written
to). For example, I'm wondering if maybe the order of operations (mail
received by sendmail, mail handed to procmail, mail processed by
spamassassin, mail handed back to procmail) as shown in the log is perhaps
not the actual order of operations in practice. I'd also like to see the
exact message that procmail is getting during each step.
For example, the OpenLDAP server v2.0.25 will spew out all sorts of
potentially useful information including packet dumps, depending on how
high a numeric value you specify for 'loglevel' in slapd.conf. I'm aware
that there are other UNIX tools for achieving this level of
troubleshooting, but it's really convenience to be able to specify a
loglevel in a config file for a particular daemon or app.
--
Graham Freeman
Manager of Information Technology
Far Western Anthropological Research Group, Inc.
+1 530 756 3941 ext 111
graham(_at_)farwestern(_dot_)com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail