02-02-2005
Quote:
Originally Posted by elmonty
This is on a shared web host. I'm not sure I have access to the log.
Dear elmonty,
You should be able to specify the procmail log location in your procmailrc file at any place in the recipe chain with:
LOGFILE=/your/path/to/your/area/procmail.log
I'll take a look at the script soon.
5 More Discussions You Might Find Interesting
1. Email Antispam Techniques and Email Filtering
Here is a crude procmail recipe that I quickly created (NOT a procmail recipe expert, btw) that has been catching lots of spam (current second after the charset_spam recipe posted earlier):
:0B
* .*If.you.do.not.wish.to.receive...*
more_spam
:0B
* You.requested.to.receive.this.mailing... (0 Replies)
Discussion started by: Neo
0 Replies
2. Email Antispam Techniques and Email Filtering
This procmail recipe catches a lot of spam, but might accidently catch a friendly email occasionally:
:0
* ^From:.*()+.*@
number_spam
... trapping user names in the From header field that have 3 or more numbers. (0 Replies)
Discussion started by: Neo
0 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I got a script that runs automatically using the cron file.
The script starts running at midnight and suppose to delete image files from folders and sub-folders. The script ends when he finishes deleting or after 5 hours. My problem is that the script doesn't stop running even after 5... (3 Replies)
Discussion started by: biot
3 Replies
4. UNIX for Dummies Questions & Answers
Suppose executable X produces files A and B from nothing, Y produces C from A, Z produces D from B, and my final goal is to produce C and D. I wrote the following makefile:
.PHONY: all
all: C D
C: A
Y A
D: B
Z B
A B:
X
This makefile seems to reflect all dependencies, as it should... (2 Replies)
Discussion started by: ybelenky
2 Replies
5. Linux
When I do "set -n" or "set -o noexec" the shell doesn't do what it sould.
Infact if I check:
$: set -o
....
noexec off
....
f
...instead I can set normally the other option.
Who Knows what could be up? (2 Replies)
Discussion started by: flaviofachin
2 Replies
LEARN ABOUT DEBIAN
proclint
proclint(1) 2008-12-09 proclint(1)
NAME
proclint - Lint procmail rc files for proper syntax
SYNOPSIS
proclint [options] <procmail *.rc files>
OPTIONS
-h, --help
Display short help.
-i, --includerc
Scan and possibly list files included in code with INCLUDERC statements.
-I, --noinclude
Do not scan INCLUDERC references (default).
-l, --list
List lines in the procmail recipe files.
-L, --nolist
Do not list lines, except for errors (default).
-p, --procmailrc
Check $HOME/.procmailrca
DESCRIPTION
Check procmail rc files for proper syntax, recipe nesting, etc. The output consists of: "LINE-NUMBER:FLAG:DEPTH: text". FLAG is one of:
R recipe
C condition
A action (redirect, '!', or pipe, '|')
F folder
= assignment
+ continuation
E *line may be erroneous*
DEPTH indicates the depth of the recipe nesting and is shown only when greater than zero.
BUGS
There are many bugs. E.g. multiline handling is not done (continued strings).
Please regard the output as advisory only.x
STATUS CODES
Program returns non-zero in case problem is found.
ENVIRONMENT
None.
FILES
None.
SEE ALSO
procmail(1)
AUTHORS
Program was written by Alan K. Stebbens <aks@sgi.com>.
This manual page was written by Jari Aalto <jari.aalto@cante.net>. Released under license GNU GPL v2 or (at your option) any later
version. For more information about license, visit <http://www.gnu.org/copyleft/gpl.html>.
proclint 2008-12-09 proclint(1)