procmail and regular expressions

[warlord at MIT.EDU (Derek Atkins)]

If someone is posting to "10 or so addresses" then the message is
probably close enough to spam that I don't mind ignoring it for a
while ;)

-derek

Jerry Feldman <gaf at blu.org> writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Content-Type: text/plain; charset=us-ascii
> 
> I normally recommend to some lists that people use bcc rather than expose 
> 10 or so addresses, which is why I filter on other than the to/cc lines. 
> But, using the List-id: field does work fine.
> Derek Atkins wrote:
> > I file all 'bcc's into a no-mans-land folder -- if someone doesn't
> > want people to know how I received their message, then it can
> > well wait until I get to it.
> > 
> > Considering many mailing list managers add info like X-Sent-To or
> > other headers, I find that even BCC'd messages usually get filtered
> > properly.  Then again I use GNUS, so perhaps it does a better job
> > of filtering than procmail.
> > 
> > -derek
> > 
> > Jerry Feldman <gaf at blu.org> writes:
> > 
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > Content-Type: text/plain; charset=us-ascii
> > > 
> > > The ^TO_ does work nicely, but falls down when people use bcc. That is why 
> > > I started to use the subject tags.
> > > Lars Kellogg-Stedman wrote:
> > > > > 
> > > > > My condition for that should match is:
> > > > > 	* ^Subject:*\[iPAQ\]
> > > > > 
> > > > > Note that the leading asterisk is a flag to procmail, so the RE passed 
> > to 
> > > > > egrep would be:
> > > > > "^Subject:*\[iPAQ\]"
> > > > 
> > > > 
> > > > Jerry,
> > > > 
> > > > Assuming that you've cut and pasted that verbatim, you've got a regular 
> > > > expression that means:  A line that starts with "Subject" followed zero 
> > > > or more ":" characters followed by [iPAQ].
> > > > 
> > > > You need to add a "." in front of the "*".
> > > > 
> > > > On a seperate note, I've generally found it more robust to filter 
> > > > mailing list messages on the To: or Cc: fields (actually, by using the 
> > > > ^TO_ "magical" regular expression in procmail).
> > > > 
> > > > -- Lars
> > > > 
> > > 
> > > - -- 
> > > Jerry Feldman <gaf at blu.org>
> > > Boston Linux and Unix user group
> > > http://www.blu.org PGP key id:C5061EA9
> > > PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
> > > 
> > > 
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.0.6 (GNU/Linux)
> > > Comment: Exmh version 2.5 12/25/2001
> > > 
> > > iD4DBQE8Mfgb+wA+1cUGHqkRAgmcAJ9z1jbb4SzwuWPV7AJA4v1MhJLH3QCYyBhB
> > > wWDTmXsvmL//or08R/B8EA==
> > > =6Zba
> > > -----END PGP SIGNATURE-----
> > > 
> > > _______________________________________________
> > > Discuss mailing list
> > > Discuss at blu.org
> > > http://www.blu.org/mailman/listinfo/discuss
> > 
> > -- 
> >        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >        Member, MIT Student Information Processing Board  (SIPB)
> >        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
> >        warlord at MIT.EDU                        PGP key available
> > 
> 
> - -- 
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix user group
> http://www.blu.org PGP key id:C5061EA9
> PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Exmh version 2.5 12/25/2001
> 
> iD8DBQE8Mgdu+wA+1cUGHqkRAgroAJ9MzpljAN5NuDehkUFPl0AN8ydYaACfUewc
> D0c2MO+Bh3YENDff2EawQvY=
> =9kf8
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available