OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 

From: Simon White (simonmtds.com)
Date: Mon Mar 03 2003 - 12:28:36 CST


03-Mar-03 at 19:05, Dirk H. Schulz (techgurumultibyte.de) wrote :
> Hi there,
>
ing.
ing.
>
> The question is: I have some users with uppercase letters on one of my
> mailservers, and I do need them thus.
>
8)
8)
> translates uppercase to lowercase letters. I would like to change that.
>
ase
ase
> fine and 2.0 does not, and other messages stating that with snapshots
> before 2.0 it works and so on.
>
> What I would like to know now:
>
> What does postfix really do in which version?
they
they
> are?
>
> Thanks for any clarification.

RFC 2821

Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command and
extension name keywords) are not case sensitive, with the sole exception
in this specification of a mailbox local-part (SMTP Extensions may
explicitly specify case-sensitive elements). That is, a command verb,
an argument value other than a mailbox local-part, and free form text
MAY be encoded in upper case, lower case, or any mixture of upper and
lower case with no impact on its meaning. This is NOT true of a mailbox
local-part. The local-part of a mailbox MUST BE treated as case
sensitive. Therefore, SMTP implementations MUST take care to preserve
the case of mailbox local-parts. Mailbox domains are not case
sensitive. In particular, for some hosts the user "smith" is different
from the user "Smith". However, exploiting the case sensitivity of
mailbox local-parts impedes interoperability and is discouraged.

Regards,

--
83%-]
83%-]
I
I
can't help but cry. I mean, I'd love to be skinny like that but not with
all those flies and death and stuff. -- Mariah Carey