TERMINATE

Terminate prematurely and requeue the mail.

HANGUP

Terminate prematurely and bounce the mail.

INTERRUPT

Terminate prematurely and bounce the mail.

QUIT

Terminate prematurely and silently lose the mail.

ALARM

Force a timeout (see TIMEOUT).

USR1

Equivalent to a VERBOSE =off.

USR2

Equivalent to a VERBOSE =on.

-v

Procmail will print its version number, display its compile time configuration and exit.

-p

Preserve any old environment.  Normally procmail clears the environment upon startup, except for the value of TZ.  However, in any case: any default values will override any preexisting environment variables, i.e., procmail will not pay any attention to any predefined environment variables, it will happily overwrite them with its own defaults.  For the list of environment variables that procmail will preset see the procmailrc(5) man page.  If both -p and -m are specified, the list of preset environment variables shrinks to just: LOGNAME, HOME, SHELL, ORGMAIL and MAILDIR.

-t

Make procmail fail softly, i.e., if procmail cannot deliver the mail to any of the destinations you gave, the mail will not bounce, but will return to the mailqueue.  Another delivery-attempt will be made at some time in the future.

"-f fromwhom"

Causes procmail to regenerate the leading `From ' line with fromwhom as the sender (instead of -f one could use the alternate and obsolete -r).  If fromwhom consists merely of a single `-', then procmail will only update the timestamp on the `From ' line (if present, if not, it will generate a new one).

-o

Instead of allowing anyone to generate `From ' lines, simply override the fakes.

-Y

Assume traditional Berkeley mailbox format, ignore any Content-Length: fields.

"-a argument"

This will set $1 to be equal to argument . Each succeeding "-a argument" will set the next number variable ($2, $3, etc).  It can be used to pass meta information along to procmail.  This is typically done by passing along the $@x information from the sendmail mailer rule.

"-d recipient ..."

This turns on explicit delivery mode, delivery will be to the local user recipient . This, of course, only is possible if procmail has root privileges (or if procmail is already running with the recipient's euid and egid). Procmail will setuid to the intended recipients and delivers the mail as if it were invoked by the recipient with no arguments (i.e., if no rcfile is found, delivery is like ordinary mail).  This option is incompatible with -p .

-m

Turns procmail into a general purpose mail filter.  In this mode one rcfile must be specified on the command line.  After the rcfile, procmail will accept an unlimited number of arguments. If the rcfile is an absolute path starting with /etc/procmailrcs/ without backward references (i.e. the parent directory cannot be mentioned) procmail will, only if no security violations are found, take on the identity of the owner of the rcfile (or symbolic link). For some advanced usage of this option you should look in the EXAMPLES section below.

-z

This turns on LMTP mode, wherein procmail acts as an RFC2033 LMTP server. Delivery takes place in the same  manner and under the same restrictions as the delivery mode enabled  with -d . This option is incompatible with   -p and -f .

Mprocmail, P=/usr/bin/procmail, F=mSDFMhun, S=11, R=21,
        A=procmail -m $h $g $u

R$*<@some.where>$*
        $#procmail $@/etc/procmailrcs/some.rc $:$1@some.where.procmail$2
R$*<@$*.procmail>$*
        $1<@$2>$3       Already filtered, map back

SENDER = "<$1>"                 # fix for empty sender addresses
SHIFT = 1                       # remove it from $@



:0                              # sink all junk mail
* ^Subject:.*junk
/dev/null



:0 w                            # pass along all other mail
! -oi -f "$SENDER" "$@"

/etc/passwd

to set the recipient's LOGNAME, HOME and SHELL variable defaults

/var/mail/$LOGNAME

system mailbox; both the system mailbox and the immediate directory it is in will be created every time procmail starts and either one is not present

/etc/procmailrc

initial global rcfile

/etc/procmailrcs/

special privileges path for rcfiles

$HOME/.procmailrc

default rcfile

/var/mail/$LOGNAME.lock

lockfile for the system mailbox (not automatically used by procmail, unless $DEFAULT equals /var/mail/$LOGNAME and procmail is delivering to $DEFAULT)

/usr/sbin/sendmail

default mail forwarder

_????`hostname`

temporary `unique' zero-length files created by procmail

Autoforwarding mailbox found

The system mailbox had its suid or sgid bit set, procmail terminates with EX_NOUSER assuming that this mailbox must not be delivered to.

Bad substitution of "x"

Not a valid environment variable name specified.

Closing brace unexpected

There was no corresponding opening brace (nesting block).

Conflicting options

Not all option combinations are useful

Conflicting x suppressed

Flag x is not compatible with some other flag on this recipe.

Couldn't create "x"

The system mailbox was missing and could not/will not be created.

Couldn't create maildir part "x"

The maildir folder "x" is missing one or more required subdirectories and procmail could not create them.

Couldn't create or rename temp file "x"

An error occurred in the mechanics of  delivering to the directory folder "x".

Couldn't determine implicit lockfile from "x"

There were no `>>' redirectors to be found, using simply `$LOCKEXT' as locallockfile.

Couldn't read "x"

Procmail was unable to open an rcfile or it was not a regular file, or procmail couldn't open an MH directory to find the highest numbered file.

Couldn't unlock "x"

Lockfile was already gone, or write permission to the directory where the lockfile is has been denied.

Deadlock attempted on "x"

The locallockfile specified on this recipe is equal to a still active $LOCKFILE.

Denying special privileges for "x"

Procmail will not take on the identity that comes with the rcfile because a security violation was found (e.g. -p or variable assignments on the command line) or procmail had insufficient privileges to do so.

Descriptor "x" was not open

As procmail was started, stdin, stdout or stderr was not connected (possibly an attempt to subvert security)

Enforcing stricter permissions on "x"

The system mailbox of the recipient was found to be unsecured, procmail secured it.

Error while writing to "x"

Nonexistent subdirectory, no write permission, pipe died or disk full.

Exceeded LINEBUF

Buffer overflow detected, LINEBUF was too small, PROCMAIL_OVERFLOW has been set.

MAILDIR is not an absolute path

MAILDIR path too long

ORGMAIL is not an absolute path

ORGMAIL path too long

default rcfile is not an absolute path

default rcfile path too long

The specified item's full path, when expanded, was longer than LINEBUF or didn't start with a file separator.

Excessive output quenched from "x"

The program or filter "x" tried to produce too much output for the current LINEBUF, the rest was discarded and PROCMAIL_OVERFLOW has been set.

Extraneous x ignored

The action line or other flags on this recipe makes flag x meaningless.

Failed forking "x"

Process table is full (and NORESRETRY has been exhausted).

Failed to execute "x"

Program not in path, or not executable.

Forced unlock denied on "x"

No write permission in the directory where lockfile "x" resides, or more than one procmail trying to force a lock at exactly the same time.

Forcing lock on "x"

Lockfile "x" is going to be removed by force because of a timeout (see also: LOCKTIMEOUT ).

Incomplete recipe

The start of a recipe was found, but it stranded in an EOF.

Insufficient privileges

Procmail either needs root privileges, or must have the right (e)uid and (e)gid to run in delivery mode.  The mail will bounce.

Invalid regexp "x"

The regular expression "x" contains errors (most likely some missing or extraneous parens).

Kernel-lock failed

While trying to use the kernel-supported locking calls, one of them failed (usually indicates an OS error), procmail ignores this error and proceeds.

Kernel-unlock failed

See above.

Lock failure on "x"

Can only occur if you specify some real weird (and illegal) lockfilenames or if the lockfile could not be created because of insufficient permissions or nonexistent subdirectories.

Lost "x"

Procmail tried to clone itself but could not find back rcfile "x" (it either got removed or it was a relative path and you changed directory since procmail opened it last time).

Missing action

The current recipe was found to be incomplete.

Missing closing brace

A nesting block was started, but never finished.

Missing name

The -f option needs an extra argument.

Missing argument

You specified the -a option but forgot the argument.

Missing rcfile

You specified the -m option, procmail expects the name of an rcfile as argument.

Missing recipient

You specified the -d option or called procmail under a different name, it expects one or more recipients as arguments.

No space left to finish writing "x"

The filesystem containing "x" does not have enough free space to permit delivery of the message to the file.

Out of memory

The system is out of swap space (and NORESRETRY has been exhausted).

Processing continued

The unrecognised options on the command line are ignored, proceeding as usual.

Program failure (nnn) of "x"

Program that was started by procmail returned nnn instead of EXIT_SUCCESS (=0); if nnn is negative, then this is the signal the program died on.

Quota exceeded while writing "x"

The filesize quota for the recipient on the filesystem containing "x" does not permit delivering the message to the file.

Renaming bogus "x" into "x"

The system mailbox of the recipient was found to be bogus, procmail performed evasive actions.

Rescue of unfiltered data succeeded/failed

A filter returned unsuccessfully, procmail tried to get back the original text.

Skipped: "x"

Couldn't do anything with "x" in the rcfile (syntax error), ignoring it.

Suspicious rcfile "x"

The owner of the rcfile was not the recipient or root, the file was world writable, or the directory that contained it was world writable, or this was the default rcfile ($HOME/.procmailrc) and either it was group writable or the directory that contained it was group writable (the rcfile was not used).

Terminating prematurely whilst waiting for ...

Procmail received a signal while it was waiting for ...

Timeout, terminating "x"

Timeout has occurred on program or filter "x".

Timeout, was waiting for "x"

Timeout has occurred on program, filter or file "x".  If it was a program or filter, then it didn't seem to be running anymore.

Truncated file to former size

The file could not be delivered to successfully, so the file was truncated to its former size.

Truncating "x" and retrying lock

"x" does not seem to be a valid filename or the file is not empty.

Unable to treat as directory "x"

Either the suffix on "x" would indicate that it should be an MH or maildir folder, or it was listed as an second folder into which to link, but it already exists and is not a directory.

Unexpected EOL

Missing closing quote, or trying to escape EOF.

Unknown user "x"

The specified recipient does not have a corresponding uid.

[pid] time & date

Procmail's pid and a timestamp.  Generated whenever procmail logs a diagnostic and at least a second has elapsed since the last timestamp.

Acquiring kernel-lock

Procmail now tries to kernel-lock the most recently opened file (descriptor).

Assigning "x"

Environment variable assignment.

Assuming identity of the recipient, VERBOSE=off

Dropping all privileges (if any), implicitly turns off extended diagnostics.

Bypassed locking "x"

The mail spool directory was not accessible to procmail, it relied solely on kernel locks.

Executing "x"

Starting program "x".  If it is started by procmail directly (without an intermediate shell), procmail will show where it separated the arguments by inserting commas.

HOST mismatched "x"

This host was called "x", HOST contained something else.

Locking "x"

Creating lockfile "x".

Linking to "x"

Creating a hardlink between directory folders.

Match on "x"

Condition matched.

Matched "x"

Assigned "x" to MATCH .

No match on "x"

Condition didn't match, recipe skipped.

Non-zero exitcode (nnn) by "x"

Program that was started by procmail as a condition or as the action of a recipe with the `W' flag returned nnn instead of EXIT_SUCCESS (=0); the usage indicates that this is not an entirely unexpected condition.

Notified comsat: "$LOGNAME@offset:file"

Sent comsat/biff a notice that mail arrived for user $LOGNAME at `offset' in `file'.

Opening "x"

Opening file "x" for appending.

Rcfile: "x"

Rcfile changed to "x".

Reiterating kernel-lock

While attempting several locking methods, one of these failed.  Procmail will reiterate until they all succeed in rapid succession.

Score: added newtotal "x"

This condition scored `added' points, which resulted in a `newtotal' score.

Unlocking "x"

Removing lockfile "x" again.

"h'-w' 'u' |exec /usr/bin/procmail"

|/usr/bin/procmail

#!/bin/sh



ORGMAIL=/var/mail/$LOGNAME



if cd $HOME &&
 test -s $ORGMAIL &&
 lockfile -r0 -l1024 .newmail.lock 2>/dev/null
then
  trap "rm -f .newmail.lock" 1 2 3 13 15
  umask 077
  lockfile -l1024 -ml
  cat $ORGMAIL >>.newmail &&
   cat /dev/null >$ORGMAIL
  lockfile -mu
  formail -s procmail <.newmail &&
   rm -f .newmail
  rm -f .newmail.lock

PATH=/usr/local/bin:/usr/bin:/bin
MAILDIR=$HOME/Mail      #you'd better make sure it exists
DEFAULT=$MAILDIR/mbox   #completely optional
LOGFILE=$MAILDIR/from   #recommended

:0:
* ^From.*berg
from_me

:0
* ^Subject:.*Flame
/dev/null