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 15:45:07 GMT
Valentina Medici ha scritto:
> Hi,
> the malformed MIME messages aren't created by a mainstream application.
> Unfotunately we need to be extremely tolerant and try to decode as many
> messages as possibile, despite their adherence to the standard. If I may
> put my two cents in, I still think that if you want to be tolerant, you
> should decode a message if you have enough information to do it correctly.

IMHO it worth being tolerand when you know an old application is doing
things wrong and there is nothing to do to fix it. But IMHO, before
implementing any "workaround" to compensate for other developers errors
we have to understand what application is creating similar messages and why.

Maybe this is only a single in-house developer having made a mistake and
an email to him will let him fixing the bug and have a better world ;-)

Being too much tolerand may cause the opposite behaviour: people stop
reading rfcs/specifications because they only try manual
interoperability for some combinations of client<->server, and if this
works they publish their code/application.

> Anyway, Stefano suggestion is quite valuable, we will consider it.

I'm still interested in understanding the source of that kind of message.
Maybe the full headers can say something about what code produced it and
what IP produced it. Can you post them?


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

View raw message