On Tue, 3 Feb 1998, Michael Beattie wrote: > Uh huh... that wasnt my question, but I have since installed procmail as a > result of that thread. I guess I have another question, the smail > configuration (transports) that procmail suggests, anybody had problems > with it?? (this one:) > > local: return_path, local, from, driver=pipe; user=root, > cmd="/usr/bin/procmail -d $($user$)"
I'll let the smail experts chime in on this one. > and again, this rule for procmail, (above) where does this Resent-cc thing > come in, and why does it need to be removed? Put it in your "~/.procmailrc". It will put all the debian realated mail in a mail/Deb-user file. BTW, the following should be at the top of your .procmailrc: # the following the the .procmailrc for Brandon Mitchell # first some variables are initialized PATH=/bin:/usr/bin:/usr/local/bin:/home/bhmit1/bin HOME=/home/bhmit1 MAILDIR=$HOME/mail # you'd better make sure it exists DEFAULT=/var/spool/mail/bhmit1 # completely optional LOCKFILE=$HOME/.procmail/lockmail LOGFILE=$HOME/.procmail/from.log # you probably want to trim this PMDIR=$HOME/.procmail # put all procmail scripts here VERBOSE=off # turn on for debuging the logfile Then, in pine, add mail/Deb-user to the list of incoming-folders. Tabing at the end of one folder should offer opening the next one with new messages in it. Good luck, Brandon P.S. I almost forgot, removing the Resent-cc will eliminate the problem in pine when replying to this group. No more unexpected data in the cc list. ----- Brandon Mitchell <[EMAIL PROTECTED]> "We all know linux is great... it PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds" Phone: (757) 221-4847 --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
