From: Jens Suelwald <jsuelwald@werebones.de>
To: linux-admin@vger.kernel.org
Subject: Re: Spammers
Date: 09 Aug 2003 20:51:41 +0200 [thread overview]
Message-ID: <1060455100.16417.14.camel@science> (raw)
In-Reply-To: <20030809175520.GL6898@mea-ext.zmailer.org>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Am Sam, 2003-08-09 um 19.55 schrieb Matti Aarnio:
> Running lists _closed_ doesn't solve the thing either. It would
> be enough for a spammer to fake source address that is known poster
> to a list. We have to use message content analysis, but that isn't
> very effective, when the content is extremely short (one web URL,
> or some such..) Main reason to not to close the lists is that
> it would be a royal pain for managers, and for users...
It would reduce the amoung of spam...
Running spamassassin wouild help to get rid of most the spammails, i
think
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-08-09 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6734256000.20030809185259@xhost.cz>
2003-08-09 17:55 ` Spammers Matti Aarnio
2003-08-09 18:51 ` Jens Suelwald [this message]
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=1060455100.16417.14.camel@science \
--to=jsuelwald@werebones.de \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).