lst_ho...@kwsoft.de:
> > There is no "wrong" To-Header. File a bug-report with Mozilla.
> 
> That's what i tried to find out: Who is at fault and what is the root-case...
> If the bug is still present in TB3 i will bother to file a bug.

If software X mis-handles a correctly-formatted message header,
then software X is broken.

Tell them to apply RFC822 syntax to the RFC 2047 ENCODED string,
not the DECODED string.

The whole point of RFC 2047 encoding is to make the ENCODED string
compatible with RFC822 syntax.

        Wietse

Reply via email to