james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Kühn <typedef_...@hotmail.com>
Subject Re: Pushing towards a RELEASE
Date Fri, 05 May 2006 09:25:33 GMT
----- Original Message ----- 
From: "Stefano Bagnara" <apache@bago.org>

> Markus Kühn wrote:
>> So the bug is that if you turn 8bit support on you have to check if an 
>> incoming message as encoding information?
>> And is this bug confirmed by Sun?
> The setContent bug is in their bugparade "in progress."
> The bug I talk about is not the same but similar. It is "correct" code in 
> SMTPTransport that simply hit the "in progress" bug: the proposed a 
> workaround for the bug, the should use it in their code.
> I have not found this SMTPTransport bug reported in their bug db. ALso I 
> had no time to write a unittest and report it. Any volounteer is welcome!
> The bug is:
> - read a 7bit quoted-printable message from a stream
> - send it via SMTPtransport to a server supporting 8bitmime and having 
> activated 8bitmime support in the SMTPSession.
> You receive a message with headers updated to report 8bit content, but 
> content unaltered and still containing the quoted-printable stuff.
> Furthermore if you read an 8bitmime message from a stream and you sent it 
> via STMPTransport to a server not supporting  8bitmime it is not converted 
> to 7bitmime.
> So we have 2 bugs here.
> I have not reported the bug almost for time reasons but also because the 
> main bug is in their db since 2001 and it is still "in progress"...

I think the encoding issue and missing encoding information (now bug nr. 3) 
could be considered as "bugs" themselves, so you should report them. I am 
curious about their point of view.


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

View raw message