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 (14 lines)
Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Wed, 6 Sep 2006 10:28:20 -0400
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=ISO-8859-1
Organization:
University of Tennessee at Chattanooga
From:
Jeff Kell <[log in to unmask]>
Someone please refresh my foggy memory, I can't seem to pinpoint the current "state of the art" in the archives/manuals:

Traditionally, email is case-sensitive to the left of the '@' and case-insensitive to the right (RFCs and whatnot).

Listserv used to be picky about case enforcement, then somewhere along the way it got a little more forgiving for certain commands (query, delete, etc).

I also seem to recall a global configuration magic flag to make Listserv even less picky about case enforcement.

But my immediate problem is in enforcement of Send= policy.  I have a list with Send= Editor,Confirm and Editor= somebody@somewhere,(OTHERLIST) where the OTHERLIST is a list of approved senders.  It appears that Listserv (14.5) is being case-sensitive about this check, and I would really like it NOT to be case sensitive.

Is there a solution to this?  Is this a LSTOWN-L question?

Jeff

ATOM RSS1 RSS2