> I just have a couple comments that you might like to know... > > [...] > >>:0: >> > The trailing : isn't required if you aren't specifying a local lock > file (or so the man page says...).
I am suffering from procmail overload! Most of my procmail examples and info came from Google so my knowledge is all patchwork. I've seen examples that used locks and ones that did not. For certain situations locking is suggested and others it is not required. I failed safe, specified a lockfile and used locking for all of my rules at the slight expense of speed. > >>* ^List-Id:.*bugtraq* >>/var/spool/mail/yuser >> > [...] > >>* ^(To|Cc):.*luau* >> > I notice you do ^(To|Cc) a lot. You may find this quote from the > man page useful: > > > If the regular expression contains `^TO' it will be sub- > > stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X- > > Envelope|Apparently(-Resent)?)-To):(.*[^a-zA-Z])?)', which > > should catch all destination specifications containing a > > specific word. > >>/var/spool/mail/yuser I tried that and had some success. For the example above with the LUAU rule it would work fine. Problem I had was in my section that blocks out mail that was not explicitly sent TO or CC me, the '^To_' flag did not work too well. The '^TO_' is was broad and too much got by. Thanks for the input! > [...] > > --Ray
