Okay, as suggested by Jernej Zajc (thanx), I set the SHELL variable to
/bin/bash and it didn't work. I also set it to /bin/sh to see what would
happen and it didn't work either. Both of these shells are specified in
/etc/shells so it should be OK as far as that's concerned. I then checked
/var/log/maillog to see if that could tell me anything and everytime procmail
tries to process a message, it logs this:
Jan 10 01:44:23 localhost sendmail[5042]: BAA05041: to=<binary(_at_)localhost>,
delay
=00:00:01, xdelay=00:00:00, mailer=local, stat=Sent
Jan 10 01:55:54 localhost sendmail[5074]: BAA05074:
from=<binary(_at_)vbe(_dot_)com>,
size=
686, class=0, pri=30686, nrcpts=1,
msgid=<Pine.LNX.4.10.10001100035060.4841-1000
00(_at_)localhost(_dot_)localdomain>, proto=ESMTP,
relay=IDENT:binary(_at_)localhost
[127.0.0.1]
Jan 10 01:55:54 localhost procmail[5076]: Suspicious rcfile
"/home/binary/.procm
ailrc"
Jan 10 01:55:54 localhost sendmail[5075]: BAA05074: to=<binary(_at_)localhost>,
delay
=00:00:01, xdelay=00:00:00, mailer=local, stat=Sent
Note the "Suspicious rcfile" part. I looked through my rc file a billion
times and cannot find anything wrong with it, but I'm not exactly a procmail
expert.. so maybe you guys can spot something that would cause procmail to
think of the file as "suspicious." The original message of my problem along
with my ~/.procmailrc file is located at the bottom of this e-mail.
Once again, any incite would be greatly appreciated.
Jernej Zajc wrote:
On Sun, 9 Jan 2000 kikin19(_at_)vbe(_dot_)com wrote:
[...]
Okay, I've also made the directory ~/Procmail to coincide with my
.procmailrc file's $PMDIR variable and configured .fetchmailrc so I can
use fetchmail to retrieve the mail from my ISP's mail server. I use
PINE for my mail client, and so my mail would be transferred to ~/mail.
Given all of this information, can ANYONE tell me why when i type
'fetchmail' and it gets all my mail from the server, the one test
message I have to test my recipe above to make sure procmail is working
doesn't filter at all. The message simply has the words 'procmail test'
for the subject line, so it should trigger the recipe i have above. In
addition, even though i've specified a log file and made VERBOSE=yes and
LOGABSTRACT=all, it seems as though procmail never even makes a log file
so I can't even troubleshoot the problem.
Hello,
look through some logs, try setting SHELL variable in your
procmailrc file, this shell has to be defined in /etc/shells if
you use sendmail. Forward mechanism passes a message to
sendmail, which, if no shells are defined in /etc/shells, puts a
warning in a log that a given user cannot forward to shell
programs. Manual page of sendmail will tell you more.
Procmail cannot write any logs cause it doesn't even get
executed. Check logs for sendmail.
Okay, I'm having some problems getting procmail to work on my computer.
Here's the lo-down:
I'm running Red Hat 6.0 (which is set up to use procmail as the default
MDA). I've set up the .procmailrc file in my home directory and it
looks like this:
----------------------------------
SHELL=/bin/bash
VERBOSE=yes
PATH=$HOME/bin:/usr/local/bin:/usr/bin:/bin
LOGABSTRACT=all
MAILDIR=$HOME/mail
DEFAULT=/var/spool/mail/binary
PMDIR=$HOME/.procmail
LOGFILE=$PMDIR/log
# Recipes
:0
* ^Subject: .*test.*
IN-testing
-------------------------------------
Okay, I've also made the directory ~/Procmail to coincide with my
.procmailrc file's $PMDIR variable and configured .fetchmailrc so I can
use fetchmail to retrieve the mail from my ISP's mail server. I use
PINE for my mail client, and so my mail would be transferred to ~/mail.
Given all of this information, can ANYONE tell me why when i type
'fetchmail' and it gets all my mail from the server, the one test
message I have to test my recipe above to make sure procmail is working
doesn't filter at all. The message simply has the words 'procmail test'
for the subject line, so it should trigger the recipe i have above. In
addition, even though i've specified a log file and made VERBOSE=yes and
LOGABSTRACT=all, it seems as though procmail never even makes a log file
so I can't even troubleshoot the problem.
--
rdk
--