Kostik <[email protected]> ha escrit:

> Sergey, how about fixs?

Pushed.

> Content-Transfer-Encoding: base64
> Content-Type: image/pjpeg; filename==?koi8-r?B?Yml6em9uYS5qcGc=?=

That's not a valid header.  Quoth RFC 2045, 5.1.:

(1)  content := "Content-Type" ":" type "/" subtype
                *(";" parameter)
                ; Matching of media type and subtype
                ; is ALWAYS case-insensitive.

(2)  parameter := attribute "=" value

(3)  value := token / quoted-string

(4)  token := 1*<any (US-ASCII) CHAR except SPACE, CTLs,
                 or tspecials>

(5)  tspecials :=  "(" / ")" / "<" / ">" / "@" /
                   "," / ";" / ":" / "\" / <">
                   "/" / "[" / "]" / "?" / "="
                   ; Must be in quoted-string,
                   ; to use within parameter values

The (4) is violated because "=" is listed in (5).

We are trying to tolerate certain deviations from the standard, insofar
as their handling is practically feasible and does not disturb normal
processing.  But this one is not a deviation, it is an open violation
of the standard.

> Content-Disposition: attachment; charset=koi8-r;
> filename==?koi8-r?B?Yml6em9uYS5qcGc=?=

Apart from the above, this header is lacking leading whitespace before
the continuation line.  The MUA that produced it must be really broken.

Regards,
Sergey



_______________________________________________
Bug-mailutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-mailutils

Reply via email to