From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-kernel@vger.kernel.org
Subject: ADMIN: The plague of ill-defined content filters...
Date: Thu, 7 Jun 2001 13:45:12 +0300 [thread overview]
Message-ID: <20010607134512.X5947@mea-ext.zmailer.org> (raw)
[ If you want to comment about this topic, respect the Reply-To ! ]
The last week or so has seen a profileration of email bounces during
the mail delivery, or "DATA" phase.
I can somewhat sympathise the goals of the filters, but some are quite
unfathomable of how they decide what exact content is undesirable, and
what isn't...
The most common ill-defined filters seem to essentially grep for a sequence
of characters anywhere in the message body without paying attention to such
small details as if that character sequence forms a word, or is part of some
other word.
Example (obfuscated against stupid grep):
the l i n k to ...
It was matched against:
i n k
Right, definitely the same thing, isn't it ?
Better filters look for longer character sequences, possibly even detecting
word separators.
At the end of the page:
http://vger.kernel.org/majordomo-info.html
you can see how VGER filters through-going traffic -- "Taboo things"...
That thing works so well, that rarely anything truly spammish goes thru.
Senders of such messages don't get any notification at all.
(In case the message is e.g. too large, they get a word that it has been
diverted to Approval.)
Best filters give parametrizable amounts of points to found matches, some
may be harmless enough to exist elsewere, while others are dead give-aways
of spam. When the message accumulates high enough treshold value of such
points, it can fairly certainly be classified as spam.
Best sites let at least system postmaster receive anything without it
being filtered -- I have seen cases where big corporate input filter says
in its reject message that "do contact 'filtops@...' if you t h i n k
something is wrong...", and when I send the exact message there, it bounces...
So, if you all the sudden loose your subscription, it could be just
because your ISP decided that a 3 character sequence anywhere in the
message body is a sign of spam.
/Matti Aarnio co-postmaster of vger.kernel.org
reply other threads:[~2001-06-07 10:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010607134512.X5947@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®