LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

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

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

Parts/Attachments: text/plain (34 lines)
Print Reply
Mime-Version:
1.0
Content-Type:
text/plain; charset=US-ASCII
Date:
Mon, 26 Nov 2007 13:27:41 -0500
Content-Disposition:
inline
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
From:
Kevin Parris <[log in to unmask]>
In-Reply-To:
Content-Transfer-Encoding:
quoted-printable
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Yes, "OK" is not a 'command' but is the primary response when a command has been given that requires confirmation.  So in a sense "OK" actually IS a command, thus it may not be the first non-blank element of a message sent to a list.

>>> <[log in to unmask]> 11/26/07 11:58 AM >>>
A user responded to a list with the following:

[start quote]
OK here.
Kraig
OK here.
Kraig

-----Original Message-----
From: List Name [mailto:[log in to unmask]] On Behalf Of
Original Sender
Sent: Monday, November 19, 2007 3:00 PM
To: [log in to unmask] 
Subject: [LIST-NAME] Fw: Listserv - NEED response
[end quote]

Listserv rejected the message thinking it might have been a command.  OK 
is not a vailid command (at least not listed on REFCARD).

Was it just because it was a two word sentance on the first line?  I'd 
like to let the user (and my CIO) the reason.

-- 
The Kool-Aid from Redmond is powerful stuff.  -- Gregg Eldred


William Brown
Web Development & Messaging Services
Technology Services, WNYRIC, Erie 1 BOCES
(716)821-7285

ATOM RSS1 RSS2