Re: OT Procmail rule not working.
On Wed, Oct 24, 2001 at 07:13:57PM -0700 I heard the voice of Will Yardley, and lo! it spake thus: i use: #mutt :0 * ^Return-Path:.*mutt-users-owner.*@mutt\.org lists:mutt/ FWIW, I'd venture you'd be better off using the Sender: header. I moved over to maildrop for filtering a while back (too dang sick of procmail's various stupidities), and my rule looks like: # Mutt if(/^Sender: owner-mutt-users/) to $MBOXDIR/mutt-users Using the .*'s in the rule really kills the efficiency of it; with Sender:, you don't need any wildcards, so it's 'quicker'. Of course, whether it's a noticeable difference is questionable... -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet
Re: OT Procmail rule not working.
* John P. Verel ([EMAIL PROTECTED]) wrote: Questions: Does your $HOME/Mail directory exist? What's the PMDIR and INCLUDERC environmental variables for? I'm running procmail-3.21-0.71, and have either of them. They are based on the Procmail Quickstart page: http://www.ii.com/internet/robots/procmail/qs/ procmail is running on the mail server instead of my local machine (that may change in the future). but here's the output of a procmail -v command on the mail server: gulf% procmail -v procmail v3.11pre3 1995/05/17 written and created by Stephen R. van den Berg [EMAIL PROTECTED] Submit questions/answers to the procmail-related mailinglist by sending to: [EMAIL PROTECTED] And of course, subscription and information requests for this list to: [EMAIL PROTECTED] Locking strategies: dotlocking, flock() Default rcfile: $HOME/.procmailrc System mailbox: /usr/spool/mail/$LOGNAME Yeah yeah, I know it's a little old, nothing I can do about it right now. So far none of the suggestions state why it doesn't work correctly. The same script works just fine on my home machine, just not here at work. -- Carl B. Constantine University of Victoria Programmer Analyst http://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED]
Re: OT Procmail rule not working.
I have a procmail rule to move list mail to a folder. But it's not working correctly according to my procmail logs. Here's the procmail script: PATH=/public/bin:/local/bin:/usr/bin:/bin SHELL=/public/bin/tcsh VERBOSE=on LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/Procmail LOGFILE=$PMDIR/log #INCLUDERC=$PMDIR/testing.rc INCLUDERC=$PMDIR/lists.rc ### # Mailing lists # ### #:0: #* X-Mailing-List: \/[^@]+ #lists/`echo $MATCH | sed -e 's/[\/]/_/g'` :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` It's this last rule that doesn't work. Here's what it produced for a mail msg to this list: what's MATCH set to? -- |- CODE WARRIOR -| [EMAIL PROTECTED] * ah! i see you have the internet [EMAIL PROTECTED] (Andrew Brown)that goes *ping*! [EMAIL PROTECTED] * information is power -- share the wealth.
OT Procmail rule not working.
I have a procmail rule to move list mail to a folder. But it's not working correctly according to my procmail logs. Here's the procmail script: PATH=/public/bin:/local/bin:/usr/bin:/bin SHELL=/public/bin/tcsh VERBOSE=on LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/Procmail LOGFILE=$PMDIR/log #INCLUDERC=$PMDIR/testing.rc INCLUDERC=$PMDIR/lists.rc ### # Mailing lists # ### #:0: #* X-Mailing-List: \/[^@]+ #lists/`echo $MATCH | sed -e 's/[\/]/_/g'` :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` It's this last rule that doesn't work. Here's what it produced for a mail msg to this list: procmail: Assigning INCLUDERC=/home/cconstan/Procmail/lists.rc procmail: Assigning MATCH= procmail: Matched mutt-users procmail: Match on ^Sender: owner-\/[^@]+ procmail: Executing echo $MATCH | sed -e 's/[\/]/_/g' procmail: Locking lists/.lock procmail: Assigning LASTFOLDER=lists//msg.LoPC procmail: Opening lists//msg.LoPC procmail: Acquiring kernel-lock procmail: [15789] Wed Oct 24 11:49:59 2001 procmail: Unlocking lists/.lock From [EMAIL PROTECTED] Wed Oct 24 11:49:57 2001 Subject: Re: limit header size Folder: lists//msg.LoPC 2991 procmail: Notified comsat: cconstan@0:/home/cconstan/Mail/lists//msg.LoPC Notice it created a different message file instead of putting it in the proper file. A listing of ~/Mail/lists: (cconstan@viper): ~/Procmail% ls -l ~/Mail/lists total 9422 -rw--- 1 cconstan 5560 Oct 24 12:14 mutt-users -rw--- 1 cconstan 9387453 Oct 24 11:03 mutt-users.01Oct24 -rw--- 1 cconstan 232405 Oct 18 08:26 uvsubnet Anyone have ideas as to why this isn't working correctly? Thanks. -- Carl B. Constantine University of Victoria Programmer Analyst http://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED]
Re: OT Procmail rule not working.
Here's my procmail recipe to filter mutt mailing list mail: :0 * ^TO_mutt Mutt That's all it takes. It ends up in a mailbox called Mutt. Questions: Does your $HOME/Mail directory exist? What's the PMDIR and INCLUDERC environmental variables for? I'm running procmail-3.21-0.71, and have either of them. John On 10/24/01, 12:26:38PM -0700, Carl B . Constantine wrote: I have a procmail rule to move list mail to a folder. But it's not working correctly according to my procmail logs. Here's the procmail script: PATH=/public/bin:/local/bin:/usr/bin:/bin SHELL=/public/bin/tcsh VERBOSE=on LOGABSTRACT=all MAILDIR=$HOME/Mail PMDIR=$HOME/Procmail LOGFILE=$PMDIR/log #INCLUDERC=$PMDIR/testing.rc INCLUDERC=$PMDIR/lists.rc ### # Mailing lists # ### #:0: #* X-Mailing-List: \/[^@]+ #lists/`echo $MATCH | sed -e 's/[\/]/_/g'` :0: * ^Sender: owner-\/[^@]+ lists/`echo $MATCH | sed -e 's/[\/]/_/g'` It's this last rule that doesn't work. Here's what it produced for a mail msg to this list: procmail: Assigning INCLUDERC=/home/cconstan/Procmail/lists.rc procmail: Assigning MATCH= procmail: Matched mutt-users procmail: Match on ^Sender: owner-\/[^@]+ procmail: Executing echo $MATCH | sed -e 's/[\/]/_/g' procmail: Locking lists/.lock procmail: Assigning LASTFOLDER=lists//msg.LoPC procmail: Opening lists//msg.LoPC procmail: Acquiring kernel-lock procmail: [15789] Wed Oct 24 11:49:59 2001 procmail: Unlocking lists/.lock From [EMAIL PROTECTED] Wed Oct 24 11:49:57 2001 Subject: Re: limit header size Folder: lists//msg.LoPC 2991 procmail: Notified comsat: cconstan@0:/home/cconstan/Mail/lists//msg.LoPC Notice it created a different message file instead of putting it in the proper file. A listing of ~/Mail/lists: (cconstan@viper): ~/Procmail% ls -l ~/Mail/lists total 9422 -rw--- 1 cconstan 5560 Oct 24 12:14 mutt-users -rw--- 1 cconstan 9387453 Oct 24 11:03 mutt-users.01Oct24 -rw--- 1 cconstan 232405 Oct 18 08:26 uvsubnet Anyone have ideas as to why this isn't working correctly? Thanks. -- Carl B. Constantine University of Victoria Programmer Analysthttp://www.uvic.ca UNIX System Administrator Victoria, BC, Canada [EMAIL PROTECTED] -- John P. Verel Norwalk, Connecticut
Re: OT Procmail rule not working.
John P. Verel wrote: Here's my procmail recipe to filter mutt mailing list mail: :0 * ^TO_mutt Mutt That's all it takes. It ends up in a mailbox called Mutt. might be better to use a different header since the TO expression is a special case and has to match To, Cc, etc also if someone's name or email address started with 'mutt' their mail would end up in your mutt folder. i use: #mutt :0 * ^Return-Path:.*mutt-users-owner.*@mutt\.org lists:mutt/ that's for Maildir - for mbox you'd ommit the trailing slash and add a ':' after the 0 in fact on the recipe above it should probably be: :0: * ^TO_mutt Mutt for mbox it's best to use a lock file. w -- GPG Public Key: http://infinitejazz.net/will/pgp/