Hi Norman!
If I don't use James, the message is passed to other server (IIS, Exchange,
etc) untouched... (nothing changes)
IMHO, I think that these other servers don't see the content, only envelope
and nothing more (If James is configured without any mailet, James acts as
an standard server, and all work ok). But with Mailets/JavaMail, James is
more "sophisticated", and... more sensible to Mime violations.
--- Guillermo
----- Original Message -----
From: "Norman Maurer" <[EMAIL PROTECTED]>
To: "James Developers List" <server-dev@james.apache.org>
Sent: Thursday, October 05, 2006 9:11 AM
Subject: Re: [jira] Commented: (JAMES-648) Corrupted MIME message with 8bit
in body
Hi Guillermo,
just an question .. How looks the message if you not use james ? It have
still to Content-Type headers ?
bye
Norman
Guillermo Grandes schrieb:
EHLO Stefano :-)
I have test this, work "half" ;-)
Now body is not corrupted, Content-Transfer-Encoding is set to 8bit, but
the header:
Content-Type: multipart/mixed;
boundary="----_=_NextPart_000_01C0B2DF.DE9D0F20"
Is removed and only maintains: "Content-Type: text/plain;
charset=iso-8859-1"
... the never ending story ... :-)
I want test the other non-issued problem in the work, I will comment to
you tomorrow.
--- Guillermo
----- Original Message ----- From: "Stefano Bagnara" <[EMAIL PROTECTED]>
To: "James Developers List" <server-dev@james.apache.org>
Sent: Wednesday, October 04, 2006 8:58 PM
Subject: Re: [jira] Commented: (JAMES-648) Corrupted MIME message with
8bit in body
Guillermo Grandes wrote:
[I think that supporting a relaxed interpretation is MUCH MORE
difficult]
Yes, I know,... the life is thus.
You trucated the line. This way make no sense.
I said that supporting the relaxed intepretation was much more
difficult
than supporting 8bitmime that is an rfc spec and would have probably
solved your problem anyway. But this was only a consideration: I don't
have time to work on any of this issue now.
Have sense, all is difficult, all depends/question of time, "more
things,
few time"..., I understand, we will see that we can do :-)
I just updated javamail to 1.4.1ea-SNAPSHOT from 15/Sep/2006 and
decommented all of the previously disabled 8bitmime support code and
tests seems to pass now.
You can find a binary build of the current trunk here:
http://jamesdev.void.it:8080/continuum/servlet/browse?file=10/dist/james-3.0-dev/downloads/bin/james-binary-3.0-dev.zip
Please let me know if you are able to test this and what are the
results.
[...]
I see that project glassfish started to fix a few of the bugs I
reported
against javamail: imho it worth investigating more on this as soon as
they
will release a new beta.
Agreed. :-)
Thanks.
Guillermo
I checked the glassfish project and I found that they already released a
new beta a couple of weeks ago, so I ran a few tests and updated our
code to test it: the result is the build above.
Hope this fix you issue,
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!EXCUBATOR:1,4524357953072053517846!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
