Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Unsolicited ads
Date: 10 Jun 1996 15:53:43 +0200	[thread overview]
Message-ID: <rjafybu5nc.fsf@kleene.dina.kvl.dk> (raw)
In-Reply-To: David Worenklein's message of 10 Jun 1996 09:30:08 -0400

>>>>> "DW" == David Worenklein <dcw@gcm.com> writes:

DW> Has anyone thought
DW> about ways of dealing with this?  

Complain.  I usually forward a copy to `postmaster', `abuse', and the
technical and administrative contact (from whois) of the first host(s)
mentioned in the `received:' headers and the DNS server of that host.

It is a boring and time consuming job, but I think it is the only way
to keep the noise at a manageable level.


  reply	other threads:[~1996-06-10 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-10 13:30 David Worenklein
1996-06-10 13:53 ` Per Abrahamsen [this message]
1996-06-10 17:26   ` Steven L Baur
1996-06-10 15:07 ` Ketil Z Malde
1996-06-10 17:13   ` Steven L Baur
1996-06-10 20:30     ` Lars Magne Ingebrigtsen
1996-06-10 22:12       ` Steven L Baur
1996-06-11  1:47         ` Lars Magne Ingebrigtsen
1996-06-16  0:45         ` Clarification (was Re: Unsolicited ads) Steven L Baur

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=rjafybu5nc.fsf@kleene.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).