unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: w3 under development or not?
Date: Fri, 14 Nov 2003 11:09:29 -0500	[thread overview]
Message-ID: <4nr80b2apy.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: ullqjary1.fsf@swbell.net

On Fri, 14 Nov 2003, pete_lee@swbell.net wrote:

> I was getting about 50-80 of those a day myself for a while... I
> wrote a perl script to parse a .spam file containing one regex per
> line.  If any of the regexes in the .spam file match the author or
> subject in the mail on the server, it's deleted on the server.  I
> mainly just focused on the service packs as they took so long to
> download.  I'm a perl novice, so I'm sure this code could be reduced
> to about 10 lines by someone that knows the language better.
> 
> Here's a snippet from my .spam:
> 
> critical.*update
> critical.*upgrade
> customer.*bulletin
> public.*assistanc
> internet.*system
> security.*pack
> security.*update
> security.*patch
> delivery.*system
> microsoft
> 
> And the script (I called pop-spam.pl) I just call with no arg for
> preview: 'perl pop-spam.pl', and 'perl pop-spam.pl delete' when I'm
> certain of my regexes.

This is a really dangerous recommendation.  If you just want to
eliminate executable attachments, which you seem to be trying to do,
use something like this Procmail recipe:

:0 H
* ^Content-Type: multipart
# check body for executable filenames
{
  :0 B
  * name=.*\.(exe|bat|pif|com|lnk|scr|vbs)(")?(\ *|\t*)$
    {
     :0
     /wherever/spam
    }
}

or install a program designed for that purpose, e.g. SpamAssassin.
Matching regular expressions against the subject is risky - are you
sure you will never want to find out about security packages, or
receive mail from people at Microsoft?

It's even riskier to delete message you haven't seen, but that's your
choice.

Ted

  reply	other threads:[~2003-11-14 16:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.124.1068506807.2005.help-gnu-emacs@gnu.org>
2003-11-11 17:16 ` w3 under development or not? Björn Lindström
2003-11-11 22:50   ` Stefan Monnier
     [not found]     ` <bosoof$hru$1@news1.wdf.sap-ag.de>
2003-11-12 10:21       ` A. L. Meyers
2003-11-12 13:59       ` Stefan Monnier
2003-11-13 15:10   ` Friedrich Dominicus
2003-11-14  8:12   ` Shane
2003-11-14  9:19     ` Poppong mail (Re: w3 under development or not?) Gian Uberto Lauri
2003-11-14 10:23     ` OT spamfilter A. L. Meyers
2003-11-14 18:22       ` Harry Putnam
2003-11-14 20:07         ` A. L. Meyers
2003-11-14 19:01       ` Tim McNamara
2003-11-14 15:30     ` w3 under development or not? Peter Lee
2003-11-14 16:09       ` Ted Zlatanov [this message]
2003-11-14 17:40         ` Peter Lee
2003-11-14 18:43           ` Ted Zlatanov
2003-11-14 22:39             ` Peter Lee
2003-11-15  4:34               ` Juri Linkov
2003-11-15 13:31               ` Ted Zlatanov
2003-11-17 15:44               ` Alan Mackenzie
2003-11-14 18:21       ` Harry Putnam
2003-11-14 16:01     ` Gnus attachment downloading blocks other Emacs interaction (was: w3 under development or not?) Ted Zlatanov
2003-11-12 21:07 w3 under development or not? Joe Corneli
  -- strict thread matches above, loose matches on Subject: below --
2003-11-10 21:59 Joe Corneli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4nr80b2apy.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).