Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: [ot] spam on ding.
Date: Mon, 25 Feb 2002 23:19:04 +1100	[thread overview]
Message-ID: <874rk54uvb.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <hhvgcl4wjl.fsf@blah.pl> (Maciej Matysiak's message of "Mon, 25 Feb 2002 12:42:54 +0100")

On Mon, 25 Feb 2002, Maciej Matysiak wrote:
> On the 24th of February 2002 at 05:16, "Jason R. Mastaler"
> <jason-dated-1015215420.8e8b50@mastaler.com> wrote:

[...]

>>> sounds reasonable for me. what was lars' opinion?
>> I think Lars derives satisfaction from canceling SPAM off the news
>> server.  :-)
> 
> that's not good solution, because you see the spam anyways. and then
> we have junk messages in list archives (which can be deleted, but
> that's another waste of someone's resources).

You might consider using a personal solution to the problem such as TDMA[1]
or SpamAssassin[2] to filter your personal email for SPAM before it
reaches you.

I use SpamAssassin myself and find it quite effective. I don't block
based on it's results but, if you wish, it can be configured to reject
mail as early as the SMTP transaction, should you chose it.

This also has the advantage of not irritating the living daylights out
of some people, such as myself, who respond to a mechanical challenge to
prove my identity by ignoring it.

Not to mention the advantage in terms of keeping the mailing list open
to posters who are not subscribed which, I note, have included some
fairly key XEmacs and Emacs people who contributed very valuable
analysis and design.

        Daniel

Footnotes: 
[1]  Which may or may not be able to do much for you; I don't really know.

[2]  <http://spamassassin.taint.org/>

-- 
Poets and such persons talk about the public as if it were some enormous and
abnormal monster-a huge hybrid between the cow they milk and the dragon that
drinks their blood.
        -- G. K. Chesterton



  parent reply	other threads:[~2002-02-25 12:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-24  0:26 Maciej Matysiak
2002-02-24  1:45 ` Jason R. Mastaler
2002-02-24  1:45 ` Jason R. Mastaler
2002-02-24  2:10   ` Maciej Matysiak
2002-02-24  2:10   ` Maciej Matysiak
2002-02-24  4:16     ` Jason R. Mastaler
2002-02-24  4:16     ` Jason R. Mastaler
2002-02-25 11:42       ` Maciej Matysiak
2002-02-25 12:19         ` Daniel Pittman
2002-02-25 12:19         ` Daniel Pittman [this message]
2002-02-25 13:37           ` Per Abrahamsen
2002-02-25 13:37           ` Per Abrahamsen
2002-02-25 14:14             ` Simon Josefsson
2002-02-25 14:14             ` Simon Josefsson
2002-02-25 16:34           ` Paul Jarc
2002-02-25 16:34           ` Paul Jarc
2002-02-25 16:48           ` Jason R. Mastaler
2002-02-25 16:48           ` Jason R. Mastaler
2002-02-26  7:41             ` Daniel Pittman
2002-02-26  7:41             ` Daniel Pittman
2002-02-25 11:42       ` Maciej Matysiak
2002-02-24 17:34   ` Stainless Steel Rat
2002-02-24 17:34   ` Stainless Steel Rat
2003-01-02  2:32   ` Lars Magne Ingebrigtsen
2003-01-02  3:16     ` Michael Shields
  -- strict thread matches above, loose matches on Subject: below --
2002-02-24  0:26 Maciej Matysiak

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=874rk54uvb.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    /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).