OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Address Extensions with virtual maps are always converted to lowercase.

From: Wietse Venema (wietseporcupine.org)
Date: Thu Jan 12 2006 - 16:37:15 CST

Andrzej Adam Filip:
[ Charset ISO-8859-1 unsupported, converting... ]
> Wietse Venema wrote:
> > Andrzej Adam Filip:
> >
> >>Victor Duchovni wrote:
> >> [...]
> >>>This is not a bug. It is intentional behaviour. RFC822 addresses are case
> >>>insensitive. If your configuration depends on the case of the extension,
> >>>it is wrong.
> >>
> >>*YOU* ARE WRONG.
> >>
> >>RFC recomendations "discontinues" the long standing tradition.
> >>
> >>http://www.ietf.org/rfc/rfc2821.txt
> >>[...] 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.
> >
> > There is such a thing as technically correct (case sensitive
> > mailbox names) and practically correct.
> >
> > I would be missing a lot of mail just because some systems to
> > map all or part of my address to upper case. I don't care that
> > those systems are broken, I want to receive my mail.
>
> We must *clearly* separate two situations:
> a) MTA acts as relay to another MTA/system
> According to RFC2821 case of local-part *MUST BE* preserved
> b) MTA conducts "final delivery"
> MTA *MAY* treat local-part as case insensitive.
>
> I think most of out disagreement has raised from mixing "a" and "b"
> situations. Some people *want to* use case sensitive local-parts.
>
> Sendmail *CAN* treat local parts in case sensitive but I think it is a bad
> recommendation on *this* mail list :-)
> http://www.sendmail.org/faq/section4.html#4.17

How many table lookups do you propose for an address mapping or
access map lookup when a transit MTA handles mail for
WiEtSeVeNeMaporcupine.org. 2**12 lookups?

        Wietse