LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"Peter M. Weiss +1 814 863 1843" <[log in to unmask]>
Tue, 6 Aug 1996 13:10:00 EDT
text/plain (92 lines)
Dear Postmaster:
 
A recent subscription request from one of your users "bounced"
(was returned) due to an error at your computer site.
 
Kindly inform your user of this difficulty, and when and if this
is repaired, advise him that he may then try to subscribe once again.
 
You might be interested in noticing that the MAILER at the Bitnet
Node UKANVM (where LDBASE-L) is hosted, routes all mail destined
for Internet domains that end in .EG via the Bitnet mailer
SMTPUSER@EGFRCUVX (aka FRCU.EUN.EG)
 
This is an unfortunate situation since I expect that all mail
from UKANVM destined for other .EG users is being rejected.
 
Thank you.
 
--  co-owner:   INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
URL:mailto:[log in to unmask] "Never confuse the messenger with the message"
 
------------------------- Message in error (69 lines) -------------------------
Received: from EGFRCUVX.BITNET by UKANVM.CC.UKANS.EDU (Mailer R2.10 ptf000)
 with BSMTP id 5716; Tue, 06 Aug 96 11:47:18 CDT
Received: from FRCU.EUN.EG by FRCU.EUN.EG (PMDF V4.2-11 #3805) id
 <[log in to unmask]>; Tue, 6 Aug 1996 19:47:29 O
Date: Tue, 06 Aug 1996 19:47:29 +0000 (O)
From: PMDF Mail Server <[log in to unmask]>
Subject: Undeliverable mail: SMTP delivery failure
To: [log in to unmask]
Message-id: <[log in to unmask]>
X-Envelope-to: [log in to unmask]
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary (ID MhVF/NbZTNI3kSoXFCDA8w)"
 
 
--Boundary (ID MhVF/NbZTNI3kSoXFCDA8w)
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
 
The message could not be delivered to:
 
[log in to unmask]: Remote system's reason for rejecting: <<[log in to unmask]>> .
   .. User not local, Relay disabled.
 
 
--Boundary (ID MhVF/NbZTNI3kSoXFCDA8w)
Content-type: MESSAGE/RFC822
 
Received: from UKANVM.CC.UKANS.EDU (MAILER@UKANVM) by FRCU.EUN.EG (PMDF V4.2-11
 #3805) id <[log in to unmask]>; Tue, 6 Aug 1996 19:46:22 O
Received: from UKANVM.CC.UKANS.EDU by UKANVM.CC.UKANS.EDU (Mailer R2.10 ptf000)
 with BSMTP id 5647; Tue, 06 Aug 96 11:43:30 CDT
Date: Tue, 06 Aug 1996 11:43:30 -0500
From: BITNET list server at UKANVM <[log in to unmask]> (1.7f)
Subject: Command confirmation request (520E81)
To: [log in to unmask]
Message-id: <[log in to unmask]>
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-LSV-ListID: LDBASE-L
 
Your command:
 
                        SUBSCRIBE LDBASE-L Manal Ismail
 
has been received.  You must now reply to this  message (as explained below)
to complete your subscription. The purpose of this confirmation procedure is
to check that  the address LISTSERV is about  to add to the list  for you is
working properly. This is a typical  procedure for high-volume lists and all
new subscribers  are subjected to  it - no offense  meant. We have  tried to
make this confirmation as simple and painless as possible, and apologize for
the inconvenience.
 
With most  mail programs, you  can confirm the  command by simply  using the
"reply"  function, without  including  the original  text,  and typing  "ok"
(without the quotes) as the text of  your message. Just "ok" - do not retype
the command  or anything else.  If this does not  work, you will  receive an
error  message. In  this  case, send  "ok 520E81"  instead,  using the  same
procedure with which you  sent the command you are now  asked to confirm. In
other words, with most mail programs you will only need to type "ok", but if
you are unlucky you may have to retype the confirmation code as well.
 
Finally, your command will be automatically  cancelled if you do not confirm
it within 71h. After  that time, you must start over  and resend the command
to get a new  confirmation code. If necessary, wait until  you know you will
be able  to reply  in time. If  on the  other hand you  change your  mind or
realize you made  a mistake when typing  the command, you do not  need to do
anything  - it  will expire  on its  own  in 71h  and, if  you discard  this
message, there is no risk of confirming it by accident.
 
--Boundary (ID MhVF/NbZTNI3kSoXFCDA8w)--

ATOM RSS1 RSS2