Thanks to Ben Parker and others who responded to my question.

>Be thankful that LISTSERV now gives this warning
yes.

usually I paste the email address given in the header of the email from a
requester when I add a person to a list. If the email address is taken from
the mail server from the vendor then it probably has a fixed character
format (since it comes from the same source). However, if it comes from the
personal computer, then it could be different since the account holder can
type it any way s/he wants.

If it is the latter case, the warning from LISTSERV is certainly useful but
if LISTSERV could be make case insensitive, it would be much better - just
like LISTSERV rejects a message that is sent twice or it rejects a
command-message that is sent to the list.

Rather then being dependent on the how the email address is typed, is it
possible for LISTSERV to convert all addresses to its own format - thus
contributing to a more problem-free software.

regards
jacky
----------
From:   Ben Parker[SMTP:[log in to unmask]]
Sent:   Monday, July 05, 1999 7:14 PM
Subject:        Re: case insensitive

On Mon, 5 Jul 1999 16:10:46 +0200, Jacky Foo <[log in to unmask]> wrote:

>Is there a way to avoid duplicate names of subscribers just because
>LISTSERV is unable to differentiate an address because it is case
>insensitive ?

No.  RFC821 and other mail standards require that case differences in the
local
or userID part of the address (left of '@') MUST be preserved, so LISTSERV
must
do so as well.  Be thankful that LISTSERV now gives this warning:

>>  Note that the following  equivalent address
>>  has been found in the list:
>>
>>    [log in to unmask] Dr Rachain Weannara
>>
>> You may want to issue a QUIET DELETE command followed by a
>> QUIET ADD of the preferred address to avoid complaints about duplicate
mail.

Note also that in some DBMS based lists (where the UEMAIL field is
configured as
a unique key) this is no longer allowed to happen, although case is still
preserved as required.