Back to the main page

Mailing List Logs for ShadowRN

Message no. 1
From: "L-Soft list server at LISTPROC.ITRIBE.NET (1.8c)"
Subject: Command confirmation request (5A8E67)
Date: Fri, 27 Mar 1998 07:38:48 -0500
Your command:

SUBSCRIBE SRCARD Srcard S. Card

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 your subscription is reachable. This is a typical procedure for
high-volume lists and all new subscribers are subjected to it - you are
not being singled out. Every effort has been made to make this
verification as simple and painless as possible. Thanks in advance for
your cooperation.

To confirm the execution of your command, simply reply to the present
message and type "ok" (without the quotes) as the text of your message.
Just the word "ok" - do not retype the command. This procedure will work
with any mail program that fully conforms to the Internet standards for
electronic mail. If you receive an error message, try sending a new
message to LISTSERV@********.ITRIBE.NET (without using the "reply"
function - this is very important) and type "ok 5A8E67" as the text of
your message.

Finally, your command will be cancelled automatically if you do not
confirm it within 48h. After that time, you must start over and resend
the command to get a new confirmation code. If you change your mind and
decide that you do NOT want to confirm the command, simply discard the
present message and let the command expire on its own.
Message no. 2
From: Luis Costa <lcosta@********.PT>
Subject: Re: Command confirmation request (5A8E67)
Date: Fri, 27 Mar 1998 12:46:40 -0000
ok
Message no. 3
From: "Ken Dirk (DrugDoc)" <dirkkenn@***.EDU>
Subject: Re: Command confirmation request (5A8E67)
Date: Fri, 27 Mar 1998 07:31:04 -0800
OK
Message no. 4
From: hansen <hansen@********.COM.SG>
Subject: Re: Command confirmation request (5A8E67)
Date: Sat, 28 Mar 1998 01:18:39 +0800
ok
-----Original Message-----
From: L-Soft list server at LISTPROC.ITRIBE.NET (1.8c)
<LISTSERV@********.ITRIBE.NET>
To: SRCARD@********.ITRIBE.NET <SRCARD@********.ITRIBE.NET>
Date: Friday, March 27, 1998 8:43 PM
Subject: Command confirmation request (5A8E67)


>Your command:
>
> SUBSCRIBE SRCARD Srcard S. Card
>
>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 your subscription is reachable. This is a typical procedure for
>high-volume lists and all new subscribers are subjected to it - you are
>not being singled out. Every effort has been made to make this
>verification as simple and painless as possible. Thanks in advance for
>your cooperation.
>
>To confirm the execution of your command, simply reply to the present
>message and type "ok" (without the quotes) as the text of your message.
>Just the word "ok" - do not retype the command. This procedure will work
>with any mail program that fully conforms to the Internet standards for
>electronic mail. If you receive an error message, try sending a new
>message to LISTSERV@********.ITRIBE.NET (without using the "reply"
>function - this is very important) and type "ok 5A8E67" as the text of
>your message.
>
>Finally, your command will be cancelled automatically if you do not
>confirm it within 48h. After that time, you must start over and resend
>the command to get a new confirmation code. If you change your mind and
>decide that you do NOT want to confirm the command, simply discard the
>present message and let the command expire on its own.
>

Further Reading

If you enjoyed reading about Command confirmation request (5A8E67), you may also be interested in:

Disclaimer

These messages were posted a long time ago on a mailing list far, far away. The copyright to their contents probably lies with the original authors of the individual messages, but since they were published in an electronic forum that anyone could subscribe to, and the logs were available to subscribers and most likely non-subscribers as well, it's felt that re-publishing them here is a kind of public service.