Has anyone else run into this problem which one would-be subscriber sent
to me this morning? Our list uses CONFIRM but when he tried to subscribe
he received nothing (or so he thought) until he received the notice that
since he had failed to confirm within the specified period his
subscription request had been cancelled. He then wrote to me and I asked
him to try once more to subscribe and to copy the subscription request to
me. He did so, and it looked perfectly in order. That was yesterday.
This morning I received the following.
The message to which his confirmation request was attached was not from
one of our subscribers nor was it from someone at his own node.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Judith Hopkins, Listowner of Autocat
[log in to unmask]
http://www.acsu.buffalo.edu/~ulcjh
---------- Forwarded message ----------
Date: Fri, 20 Feb 1998 08:10:21 -0500
From: XXXXX XXXXX <[log in to unmask]>
To: [log in to unmask]
Subject: Messages Run Amuck
Hi Judith,
Thanks for your help with regard to subscribing to Autocat. As it turns
out, I *have* actually been getting the confirmation messages, I just
didn't know it because they have somehow been getting attached to the
bottom of other messages -- how bizarre! A colleague and I were discussing
this situation yesterday, and she mentioned that she had run into a similar
problem, and had by accident found her confirmation message at the bottom
of another message, so I carefully checked my mail, and there it was! I
have forwarded to you an exact copy of the most recent message that I have
received -- I have also gone ahead and confirmed using the other address
and code as instructed in the message. I suspect that this is a local
problem, and in no way a flaw with the Autocat Listserver.
Thanks for your help!
******************************************************************************
>X-Sender: [log in to unmask]
>X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
>Date: Thu, 19 Feb 1998 17:23:11 -0500
>To: [log in to unmask]
>From: Carolyn Smith <[log in to unmask]>
>Subject: Away for the day
>
>I will not be in my office on Friday February 20 . I will return to my
>office for normal working hours Monday February 23 at 7:30 a.m.
>
>Please direct any emergency moving request to ex 4458.
>
>Thank you, and I hope each of you have a nice, safe weekend.
>
>See you on Monday.
>
>Carolyn
>
>From Thu Feb 19 17:42:11 1998
>Return-Path: <Mailer-Daemon>
>Received: from deliverance.acsu.buffalo.edu by mail.gac.peachnet.edu
(SMI-8.6/SMI-SVR4)
> id RAA15104; Thu, 19 Feb 1998 17:42:08 -0500
>Message-Id: <[log in to unmask]>
>Received: (qmail 27285 invoked from network); 19 Feb 1998 21:42:37 -0000
>Received: from listserv.acsu.buffalo.edu (128.205.7.35)
> by deliverance.acsu.buffalo.edu with SMTP; 19 Feb 1998 21:42:37 -0000
>Date: Thu, 19 Feb 1998 16:42:37 -0500
>From: "L-Soft list server at University at Buffalo (1.8c)"
> <[log in to unmask]>
>Subject: Command confirmation request (11DD86)
>To: XXXXX XXXXX <[log in to unmask]>
>X-LSV-ListID: AUTOCAT
>Content-Length: 1489
>
>Your command:
>
> SUBSCRIBE AUTOCAT Xxxxxx Xxxxx
>
>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 [log in to unmask] (without using the "reply"
>function - this is very important) and type "ok 11DD86" 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.
>
|
