1995-02-13 - Automatic reply to your test message (lwall)

Header Data

From: News auto-reply daemon <news@lucy.ee.und.ac.za>
To: cypherpunks@toad.com
Message Hash: dac280b44cc84ffa4075e72807192a854ef9e0b291eb01a63ec78d0e704e9e4b
Message ID: <9502130858.AA27833@lucy.ee.und.ac.za>
Reply To: <PINE4545-dhfsdkjc@ack.berkeley.edu>
UTC Datetime: 1995-02-13 08:59:18 UTC
Raw Date: Mon, 13 Feb 95 00:59:18 PST

Raw message

From: News auto-reply daemon <news@lucy.ee.und.ac.za>
Date: Mon, 13 Feb 95 00:59:18 PST
To: cypherpunks@toad.com
Subject: Automatic reply to your test message   (lwall)
In-Reply-To: <PINE4545-dhfsdkjc@ack.berkeley.edu>
Message-ID: <9502130858.AA27833@lucy.ee.und.ac.za>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="Boundary..3926.1071713480.multipart/mixed"

--Boundary..3926.1071713480.multipart/mixed
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

This is an automatic reply, to let you know that a test message from you
(or listing your address in the Reply-To header) recently arrived here
at news system "ee.und.ac.za", which is in the Electronic Engineering
department at the University of Natal, Durban, South Africa.

A lot of people are confused by automatic reply messages, so this
message tries quite hard to explain what is going on.  If you have any
good suggestions for ways in which the wording of this message can be
improved, please send them to <news@ee.und.ac.za>.

Some of the reasons people post test messages is to check whether their
news system is correctly configured to let their messages get out, and
to check whether their mail system is correctly configured to let mail
get back to them.  Because of these uses of test messages, some news
administrators -- trying to be helpful -- configure their news systems
to send automatic responses.

It is possible that somebody tricked you into posting a test message, or
that somebody else forged a test message that either appeared to be from
you or directed replies to you.  If that is what happened to you, then
you may be able to use the information below to help you to track down
the perpetrator.

Each message in almost all of the *.test newsgroups is a considered
as a candidate for an automatic reply like this one.  If the message
header or the first few lines of the body contains any of the phrases
"ignore", "no reply", "do not reply" or a few other variants, then
the message is ignored.  If the message does not contain any of those
trigger phrases, then the auto-replier sends back a reply like this
one.  (If you get more than one copy of this reply, that might mean
that there is a problem in the mail system; please ask your local mail
administrator for help.)

It's too late to have any effect on this message, because this reply
has already been sent, but in future, if you do not want to receive
automatic replies like this, then you should either refrain from posting
messages to the *.test newsgroups, or ensure that your postings to the
*.test newsgroups contain the trigger phrases that will cause your
messages to be ignored by auto-repliers.  Please also note that name
has not been added to any kind of subscription list, so there's no need
to try to unsubscribe or to send "ignore" messages back via electronic
mail.

By the way, this site receives messages in certain newsgroups, or with
certain distributions, that some people might consider to be unusual for
a site in South Africa.  We do that deliberately, so please don't be too
surprised.

If you want to write to the human who administers the news system that
generated this auto-reply message, the address <news@ee.und.ac.za>
should work.


--Boundary..3926.1071713480.multipart/mixed
Content-Type: application/octet-stream; name="bin00001.bin"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bin00001.bin"
Content-Description: "A copy of the header and the first few lines of   the body of your test message."

UGF0aDogZWUudW5kLmFjLnphIXVjdGhweCF0aWNzYS5jb20hcHNncmFpbiFu
bnRwLnNraS5tc2tjYy5vcmchcHNpbm50cCFwc2lubnRwIXBzaW5udHAhcmVi
ZWNjYSFwYXVsaW5nLndhZHN3b3J0aC5vcmchZW1pLmNvbSF1dW5ldCFuZXdz
Lm1hdGh3b3Jrcy5jb20hem9tYmllLm5jc2MubWlsIW5ld3MuZHVrZS5lZHUh
Z29kb3QuY2MuZHVxLmVkdSFodWRzb24ubG0uY29tIW5ld3MucG9wLnBzdS5l
ZHUhbmV3cy5jYWMucHN1LmVkdSFob3dsYW5kLnJlc3Rvbi5hbnMubmV0IWFn
YXRlIW92ZXJsb2FkLmxibC5nb3YhZW1mLmVtZi5uZXQhaGlsYmVydC5kbmFp
LmNvbSFuYm4hbWl3b2shbmV3cy56ZWl0Z2Vpc3QubmV0IWFjay5iZXJrZWxl
eS5lZHUhbm90LWZvci1tYWlsClN1YmplY3Q6IGx3YWxsCk1lc3NhZ2UtSUQ6
IDxQSU5FNDU0NS1kaGZzZGtqY0BhY2suYmVya2VsZXkuZWR1PgpOTlRQLVBv
c3RpbmctSG9zdDogYWNrLmJlcmtlbGV5LmVkdQpPcmdhbml6YXRpb246IGN5
cGhlcnB1bmtzCkxpbmVzOiAyCkZyb206IGN5cGhlcnB1bmtzQHRvYWQuY29t
CkRpc3RyaWJ1dGlvbjogd29ybGQKTmV3c2dyb3VwczogYWx0LnRlc3QKRGF0
ZTogNiBGZWIgMTk5NSAxOTozNDoxOSBHTVQKCnRlc3QKdGVzdAo=
--Boundary..3926.1071713480.multipart/mixed--




Thread