I do not know about you, but I have always had problems with $HOME in my
INCLUDES.
Have you tried to use the full path name...? that always works for me..
On Sat, 26 May 2001, Lisa Winkler wrote:
->I'm having trouble getting procmail to recognize my INCLUDERC. I have the
->following .procmailrc in my home directory:
->
->-rw-r--r-- 1 lmw lmw 345 May 22 21:08 .procmailrc
->
->PATH=$HOME/bin:/usr/bin:/bin:/usr/local/bin:.
->MAILDIR=$HOME/mail # You'd better make sure it exists
->DEFAULT=$HOME/mbox
->LOGFILE=$HOME/procmail.log
->LOCKFILE=$HOME/.lockmail
->
->INCLUDERC=$HOME/.killfilerc
->
-># testing
->:0
->* ^From(_dot_)*lmw(_at_)po(_dot_)cwru(_dot_)edu
->Junk
->
-># Anything that has not been delivered by now will go to $DEFAULT
-># using LOCKFILE=$DEFAULT$LOCKEXT
->
->and .killfilerc, also in my home directory:
->
-> -rw-r--r-- 1 lmw lmw 1138 Mar 31 12:00 .killfilerc
->
->:0
->* ^From(_dot_)*htmlmail(_at_)mail(_dot_)ezbid(_dot_)com
->Junk
->
-><lots of entries like this one snipped>
->
->Basically I want my .killfilerc to be autogenerated for me (I have a perl
->script to do this) and leave my .procmailrc for any other filters I want
->to add. If I just take the contents of the .killfilerc and copy it in
->place of the INCLUDERC statement, it works fine. But if I leave it as
->described, it doesn't seem to read my .killfilerc at all. The rule that
->is in my .procmailrc gets matched, but none of the ones in .killfilerc
->do. I don't think it's a permission problem since both files have the
->same permissions. Any suggestions?
->
->Thanks,
->Lisa
->
->
->_______________________________________________
->procmail mailing list
->procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
->http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
->
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail