Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Cc: po-utils-forum@iro.umontreal.ca, Bruno Haible <haible@ilog.fr>,
	eliz@is.elta.co.il, ding@gnus.org
Subject: Thinking about SPAM and bounce messages (Re: null-device)
Date: 14 Jul 2001 05:57:42 +0200	[thread overview]
Message-ID: <shg0c0i2mh.fsf_-_@tux.gnu.franken.de> (raw)
In-Reply-To: <oqg0c0oi28.fsf@lin2.sram.qc.ca>

[Reply-To: ding@gnus.org; or should I've better used Mail-Followup-To:?]

pinard@iro.umontreal.ca (François Pinard) writes:

> SPAM is a pain, and a growing one.

Just let it grow and die a sudden death (like dinos).

> It is for me at least, but less for the members of the mailing lists I
> manage, hopefully.  I think for my users that a few "non-member
> submission" (and associated delays) messages is better than the SPAM
> which I see alone, and which they would otherwise receive.

I disagree.  Dalays, okay, using the internet we've to expect delays all
the time.  More important is that always the From: line is changed.
Emacs/Gnus offers gnus-summary-resend-bounced-mail (S D b) --
unfortunately, it doesn't work too nice with bounces by majordomo

(cf. my last message to the ding list, please).

If proper bouncing doesn't work, I'd recommend to forward the message in
a straiht manner.

The last issue: Sometimes \201's are creeping in the "non-member
submission" messages.

> For the non-mailing-list messages I get, I have my own SPAM filters.
> I keep asking managers for other mailing list I'm subscribed to, to
> better do their share at blocking SPAM, because I consider that SPAM
> should be blocked directly by the mailing lists, rather than by all
> recipients down the road.

Blocking isn't enough.  I'll have to "complain", too.  Blocking without
complaining will not help to improve the world.  Of course, you can do
this to save your own health, but it's not okay to try to do this for
others, too (even if innocent users are crying for this remedy!).

I hope, it's clear what I want to say.

> But I'll happily let my users decide.  I do not personally need to
> impose anti-SPAM to them.  I thought I was doing them a service, I may
> be wrong! :-)

;-)

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.suse.de/~ke/                                  |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)


           reply	other threads:[~2001-07-14  3:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <oqg0c0oi28.fsf@lin2.sram.qc.ca>]

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=shg0c0i2mh.fsf_-_@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    --cc=ding@gnus.org \
    --cc=eliz@is.elta.co.il \
    --cc=haible@ilog.fr \
    --cc=po-utils-forum@iro.umontreal.ca \
    /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).