From: amu@MIT.EDU (Aaron M. Ucko)
Subject: Re: E-mail abuse report (was: Now available.)
Date: 05 Dec 1998 19:02:10 -0500 [thread overview]
Message-ID: <udlbtlikuil.fsf@snorklewacker.mit.edu> (raw)
In-Reply-To: Jason L Tibbitts III's message of "05 Dec 1998 14:36:41 -0500"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=NIL, Size: 347 bytes --]
Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
> I can close the list to nonmembers rather trivially, but that gets in the
> way of folks who post from multiple addresses (like Lars) which I can cope
And in the way of folks like me who read the list via read-only gateways...
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
next prev parent reply other threads:[~1998-12-06 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x7btll3pt6.fsf@peorth.gweep.net>
[not found] ` <1rn254hyab.fsf@haey.ifi.uio.no>
1998-12-05 15:53 ` Lars Magne Ingebrigtsen
1998-12-05 19:35 ` Jason L Tibbitts III
1998-12-06 0:02 ` Aaron M. Ucko [this message]
1998-12-06 2:10 ` Kjetil Torgrim Homme
1998-12-07 15:09 ` Jason L Tibbitts III
1998-12-06 19:14 ` Lars Magne Ingebrigtsen
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=udlbtlikuil.fsf@snorklewacker.mit.edu \
--to=amu@mit.edu \
/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).