james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: [mime4j] [PATCH] - Proposed patch to decode base64 messages with malformed Content-Transfer-Encoding headers
Date Thu, 22 Jan 2009 08:35:58 GMT
Valentina Medici ha scritto:
> Hi all!
> I have a MIME base64 decoded message in which the header
> Content-Transfer-Encoding is almost correct except for the fact that the
> new line after the header is missing. In the current implementation of
> mime4j (0.5) that file couldn't be decoded.
> In the proposed patch, if the Content-Transfer-Encoding is not
> recognized, it will be guessed if possible.
> So, if the header is like the one I receive,i.e.:
> Content-Transfer-Encoding: base64 Content-Disposition: attachment;

How much of this messages are you  receiving ?
What kind of application creates this falformed message? If it is a
mainstream application then it probably worth including a workaround in
mime4j, but it if is an in-house application then we probably cannot
include it in the main library.

In this last case maybe you should fix this with a custom
inputstreamfilter that simply intercept that sequence adding the CRLF in
the appropriate place.


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message