9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spam rejection after reception does have limits
Date: Sun, 28 Sep 2003 11:12:09 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0309281103580.27422-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <001601c385d6$bff7f5e0$b9844051@insultant.net>

On Sun, 28 Sep 2003, boyd, rounin wrote:

> Ron sez:
> > I wouldn't go that far. In the good 'ole days, DARPANET was an elitist
> > institution: nobody got in unless DARPA said ok.

> body sez:
> it was designed to be a closed, fault tolerant, net for the military.
>
> run by bob <guess>?

yeah. I saw Dave Crocker at SGI about ten years ago and we were talking
about the inappropriate uses that "the great unwashed" were putting the
internet to -- uses never envisioned when it was "elite net" and only
certain folks got to use email, much less hook up to it.

He had seen cases of people sending billing and payment notices for their
business, in the clear, over email, with sensitive bits in them. We were
both kind of amazed (appalled) at how things had worked out. But why not?
The protocols were all designed with one assumption: if you were on the
net at all, you had passed some sort of barriers already.

Now, of course, it is tending to collapse so this may be less of a problem
in a short while.

"Your message was rejected as Spam. The subject was: Your new tool has
arrived. The word which caused the rejection was: tool"

Second try: Subject: That you-know-what is here at the you-know-what

"Your message was rejected as ..."

Third try: Subject: U got thing here now cum get it

"You message ..."

[[ recipient of email goes out of business waiting for email about their
new tool ]]

ron



  reply	other threads:[~2003-09-28 17:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27 22:46 ron minnich
2003-09-28  1:11 ` boyd, rounin
2003-09-28  9:08   ` Charles Forsyth
2003-09-28  9:16     ` boyd, rounin
2003-09-28  8:10 ` Lucio De Re
2003-09-28  8:59   ` boyd, rounin
2003-09-28  9:42     ` Lucio De Re
2003-09-28 10:18       ` boyd, rounin
2003-09-28 10:50       ` boyd, rounin
2003-09-28 11:18         ` Lucio De Re
2003-09-28 11:44           ` boyd, rounin
2003-09-28 11:05       ` boyd, rounin
2003-09-28 11:47         ` Lucio De Re
2003-09-28 11:58           ` boyd, rounin
2003-09-28 12:17             ` Lucio De Re
2003-09-29  9:14         ` Douglas A. Gwyn
2003-09-29  9:37           ` boyd
2003-09-28 15:33       ` ron minnich
2003-09-28 15:39         ` boyd, rounin
2003-09-28 17:12           ` ron minnich [this message]
2003-09-28 17:22             ` boyd
2003-09-28 10:16     ` Charles Forsyth
2003-09-28 10:23       ` boyd, rounin
2003-09-29  3:23         ` salomo3
2003-09-29  3:32           ` boyd
2003-09-29  5:18             ` Lucio De Re
2003-09-29  9:18               ` boyd
2003-09-29 13:53             ` Joel Salomon
2003-09-29  9:14     ` Douglas A. Gwyn
2003-09-29  9:13   ` Douglas A. Gwyn
2003-09-29  9:44     ` SPAM: " Charles Forsyth
2003-09-29 15:21       ` Douglas A. Gwyn
2003-09-29 16:02         ` Joel Salomon
2003-09-29 21:24           ` boyd

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=Pine.LNX.4.44.0309281103580.27422-100000@maxroach.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.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).