Me thinks you misread the RFC822 ... ;-)

It is actually quite clear:

6.2.4.  DOMAIN-DEPENDENT LOCAL STRING

indicates that the local part (part before the '@') is whatever the local (receiving) server allows.

Then, explicitly in 3.4.7 (as you noted), the RFC says:

Except as noted, alphabetic strings may be represented in  any
        combination of upper and lower case.  The only syntactic units
        which requires preservation of case information are:

                    -  text
                    -  qtext
                    -  dtext
                    -  ctext
                    -  quoted-pair
                    -  local-part, except "Postmaster"

Where local-part is again, the part before the '@'.

This explicitly states that the local-part is CASE SENSITIVE (other than 
"Postmaster" which *has* to be case insensitive...).

Rolf



M. Adam Davis wrote:

>[snip]
>The key is that according to http://www.faqs.org/rfcs/rfc822.html ,
>email names (like domain names and field names) are case insensitive
>(section 3.4.7).  While the server may only accept adavis@ubasics.com
>as the name it sets up for the account, when it receives an email for
>ADavis, aDavis, AdAvIs or any other case permutation it is supposed to
>accept it for the adavis account.
>
>The services themselves may have additional (silly) restrictions for
>what name you can set up, and perhaps these restrictions are what
>you're running into - but I've yet to see a system that rejects
>incoming email because of case issues.  Try it out with your own
>email, or even the PICList@mit.edu.
>
>-Adam
>
>  
>



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist