Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jason R. Mastaler" <jason-dated-1015206302.084d51@mastaler.com>
Subject: Re: [ot] spam on ding.
Date: Sat, 23 Feb 2002 18:45:00 -0700	[thread overview]
Message-ID: <a59gs4$jk3$1@quimby2.netfonds.no> (raw)
In-Reply-To: <hhn0xzafnp.fsf@blah.pl> (Maciej Matysiak's message of "Sun, 24 Feb 2002 01:26:34 +0100")

Maciej Matysiak <phoner@blah.pl> writes:

> can anything be done to block them? it seems that anyone can post on
> ding, maybe the listowner should close the list, or just moderate
> posts from not subscribed posters?

The problem with closing the list is that it makes things very
inconvenient for those who just want to post to ding, but don't want
to subscribe.  Manual moderation of non-subscribed posters is
laborious and results in unnecessary delay for those messages.

Something I've proposed to Lars in the past is using TMDA to protect
the ding list.  The idea is that TMDA intercepts mail sent to
ding@gnus.org, and allows the message through if 1) the sender is
subscribed, or 2) he is on the "whitelist".  Otherwise he confirms his
post and is then automatically added to the whitelist so future posts
go right through.  This is nice because it keeps SPAM off the list
while still allowing legitimate non-members to post without much
hassle.

If you want to see an example of what the confirmation process would
look like for non-subscribers, send a message to <ding-test@gnus.org>
and follow the instructions you get back.  After you confirm that
first message, try sending a second, and notice that you don't have to
confirm again.

> or block the sclp3.sclp.com if possible?

You've misinterpreted the mail headers.  sclp3.sclp.com hosts
gnus.org, so blocking it probably wouldn't be a very good idea.  :-)

-- 
(http://tmda.sourceforge.net/)



  parent reply	other threads:[~2002-02-24  1:45 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  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 11:42       ` Maciej Matysiak
2002-02-25 12:19         ` Daniel Pittman
2002-02-25 12:19         ` Daniel Pittman
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-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
2002-02-24  1:45 ` Jason R. Mastaler [this message]
  -- 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='a59gs4$jk3$1@quimby2.netfonds.no' \
    --to=jason-dated-1015206302.084d51@mastaler.com \
    /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).