From: dashielljt <dashielljt@gmpexpress.net>
To: Marco Calistri <ik5bcu@tin.it>
Cc: linux-newbie@vger.kernel.org
Subject: Re: A "subject" rule for procmail
Date: Sun, 14 Sep 2003 01:32:54 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0309140120090.875@localhost> (raw)
In-Reply-To: <XFMail.20030913224135.ik5bcu@tin.it>
You have now learned the futility of subject filters. Perhaps a white
list filter would work better. Unfortunately I don't know how to set one
of them up in procmail but have one set up and working in pine. As a
stopgap measure in procmail, search for something like this, :0 HB
* prescription
spam
-- ----- That effectively searches both the header and body of the message
for prescription and tosses those messages into the spam folder. I don't
send anything to /dev/null automatically. I have a chance to look at it
before taking further action. A white list filter's concept is there are
people and lists that don't send you spam; their addresses are put onto a
white list. Everyone on that white list goes into your inbox, everyone
else goes into spam folder. A further wrinkle on a white list filter is
the spam2go folder. See when I search spam, I find some good e-mail in it
that won't be picked up by my white list just yet. So I deal with that
e-mail accordingly and put the real spam into spam2go and then that
empties the spam folder. That way when I next look at spam folder I'm not
looking at any old messages since any old spam was already put into
spam2go. What happens to the contents of spam2go? Well I enable display
of full headers and select all messages when spam2go count gets to 50
messages happens every two days now and forward all messages as a mime
digest to uce@ftc.gov. Then I delete all messages from spam2go so it only
gets new spam for uce@ftc.gov to check out. The federal trade commission
sometimes takes some action against spam artists and corporations that
sponsor spam when legal grounds can be found.GNU Linux a real operating
system with a clu
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-09-14 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 20:41 A "subject" rule for procmail Marco Calistri
2003-09-14 5:32 ` dashielljt [this message]
2003-09-14 9:41 ` Peter Edstrom
2003-09-14 10:11 ` dashielljt
2003-09-14 16:02 ` Peter Edstrom
2003-09-14 9:49 ` (F)A " Steven
2003-09-14 19:56 ` Marco Calistri
2003-09-15 11:25 ` Peter Edstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0309140120090.875@localhost \
--to=dashielljt@gmpexpress.net \
--cc=ik5bcu@tin.it \
--cc=linux-newbie@vger.kernel.org \
/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