Ralf Hildebrandt:
> * Victor Duchovni <victor.ducho...@morganstanley.com>:
> > On Mon, Feb 22, 2010 at 02:57:54PM +0100, Ralf Hildebrandt wrote:
> >
> > > Can anybody comment on this ugly "fix" for Umlauts in realnames?
> > >
> > > # Already with Quotes ("=22") thus do nothing
> > > /^From: =\?iso-8859-1\?Q\?=22(.*)=22\?= <(.*)>$/ REPLACE From:
> > > =?iso-8859-1?Q?=22$1=22?= <$2>
> > > # No quotes
> > > /^From: =\?iso-8859-1\?Q\?(.*)\?= <(.*)>$/ REPLACE From:
> > > =?iso-8859-1?Q?=22$1=22?= <$2>
> > >
> > > #becaus:
> > > #wrong =?iso-8859-1?Q?Kr=FCger=2C_Stephanie?=
> > > #correct =?iso-8859-1?Q?=22Dr._med._Stefan_R=F6pke=22?=
> >
> > The "wrong" form is RFC compliant. No quotes are required, because
> > they are not part of the value, they are part of the syntax for a
> > quoted-string encapsulation of the value inside the quotes. When using
> > RFC 2047 encoding, the encoded string is an RFC822 atom and does not
> > require any quotes.
>
> But Exchange forgets the "" and just encodes
> L?stn?me, Firstn?me
> instead of
> "L?stn?me, Firstn?me"
>
> thus the quoted-string encapsulation is wrong?!
RFC822..RFC5322 do not need quotes around text inside the
=?iso-8859-1?Q?stuff?=, as long as there are no spaces. That
was an explicit design choice.
Wietse
Wietse
