On 4/18/05, Hossein Movahhedian <dma8hm1956(_at_)gmail(_dot_)com> wrote:
### The first one
LISTS_DIR=/dos/f/Lists
MSG_FILE=/ext3/home/tmp/procmail.msg
LOGFILE=/ext3/home/tmp/procmail.from
VERBOSE=on
LOGABSTRACT=all
:0
* ^TO_.*farsitex-user@
{
:0
| echo "Mail received from: Ftex-user" >> $MSG_FILE
:0:
$LISTS_DIR/.NEW_Ftex-user
}
In this instance you should have gotten the file
/ext3/home/tmp/procmail.from created, containing at least a log of the
assignment to LOGABSTRACT and an indication of no match on the recipe
condition.
### The second one
LISTS_DIR=/dos/f/Lists
LOG_FILE=/ext3/home/tmp/procmail.msg
LOGFILE=/ext3/home/tmp/procmail.from
VERBOSE=on
LOGABSTRACT=all
:0
* ^TO_.*farsitex-user@
{
OLDLOG=$LOGFILE
LOGFILE=$LOG_FILE
LOG="Mail Received from ftext-user$NL"
LOGFILE=$OLDLOG
:0:
$LISTS_DIR/.NEW_Ftex-user
}
Same here.
But still they don't work and while $LOGFILE and $MSG_FILE are
created with other lists, nothing is created with `farsitex-user'
list.
If /ext3/home/tmp/procmail.msg is not created, that simply indicates
the recipe didn't match. If the procmail.from file is not being
created, it indicates that procmail IS NOT RUNNING AT ALL for these
messages -- or perhaps it is running, but is delivering and exiting
much sooner, such as during processing of /etc/procmailrc.
In the former case this is not a procmailrc problem, but a mail
delivery issue, and you're looking in entirely the wrong place for the
solution. In the latter case we can't help until you figure out why
/etc/procmailrc is bypassing your personal .procmailrc.
____________________________________________________________
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