From: phil@netroedge.com (Philip Edelbrock)
To: lm-sensors@vger.kernel.org
Subject: spam on this list
Date: Thu, 19 May 2005 06:23:46 +0000 [thread overview]
Message-ID: <3E317BC2.9000507@netroedge.com> (raw)
In-Reply-To: <3E314A6E.2BFB8F88@plain.de>
Sorry, I know the spam is a hassle. It would be nice to have a
moderator who can screen everything, but that takes too much time and
delays emails. Right now there is a procmail script which tags likely
spam and puts in a X-SBClass: header. If it is followed by 'Spam', then
it is almost certainly spam, if it is followed by 'Blocked', then it
scores high as being potential spam. You should be able to set some
rules in your mail client to throw those emails into a seperate folder.
It's not bullet proof (some legit mails get tagged wrong, and vice
versa), but it seems to be about 95% accurate in my experience.
BTW- If there are some recommendations on better alternatives, let me know.
Phil
Markus Schorer wrote:
>hi,
>
>being rather new here it seems to me that more spam is going
>over this list than i2c related stuff.
>
>any chance of getting the spam excluded?
>
>regards,
>
>
>
next parent reply other threads:[~2005-05-19 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E314A6E.2BFB8F88@plain.de>
2005-05-19 6:23 ` Philip Edelbrock [this message]
2005-05-19 6:23 ` spam on this list Jean Delvare
2013-11-23 14:41 Pierre Frenkiel
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 9:01 partition 100% full No space left on device. looks like xfs is corrupted or a bug Lista Unx
2016-08-01 12:00 ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-08-03 12:59 ` Spam on this list [Was: Re: partition 100% full No space left on device. looks like xfs iscorrupted or a bug] Carlos E. R.
2016-08-03 13:21 ` Martin Steigerwald
2016-08-03 13:34 ` Carlos E. R.
2016-08-03 23:15 ` Spam on this list Dave Chinner
2016-08-03 23:29 ` Darrick J. Wong
2016-08-04 0:51 ` Carlos E. R.
2016-08-04 11:34 ` Lista Unx
2016-08-04 13:40 ` Troy McCorkell
2016-08-04 15:49 ` Martin Steigerwald
2016-08-05 8:25 ` Carlos Eduardo Maiolino
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=3E317BC2.9000507@netroedge.com \
--to=phil@netroedge.com \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.