james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: javamail 1.3.0
Date Thu, 05 Dec 2002 21:46:32 GMT
Serge,

Thanks for that info.  I don't believe that it will impact existing code, so
we'll stick with the release plan unchanged.  As soon as we're shipped, we
can replace the javamail jar in the CVS, if you are representing that you
have tested it (we'll do so again, anyway, of course).

	--- Noel

-----Original Message-----
From: Serge Sozonoff [mailto:serge@globalbeach.com]
Sent: Thursday, December 05, 2002 16:25
To: James Developers List
Subject: Re: javamail 1.3.0


Hi Noel,

> We're all tested and ready to go.  I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.

I understand and agree here. IMHO We just need to make sure that javamail
1.3.0 makes it into the next release.

> What is the nature of the bug?  Is there a workaround?  Does it effect
> normal users with the current set of mailets?

Possibly my current problem is related to this bug which was fixed in 1.3.0:
    - tolerate trailing semicolon in Content-Type header (requires JAF
1.0.2)

I am getting an error message like this when calling multipart.getCount() :
    javax.mail.MessagingException: EOF skipping headers

My solution was to build JAMES 2.1a1cvs replacing javamail 1.2.0 with
javamail 1.3.0 in the build process

I don't know if it effects normal users with the current set of mailets
since I am not familiar with all of the
current mailets. My guess would be that is does not.

Thanks,
Serge


----- Original Message -----
From: "Noel J. Bergman" <noel@devtech.com>
To: "James Developers List" <james-dev@jakarta.apache.org>
Sent: Thursday, December 05, 2002 9:24 PM
Subject: RE: javamail 1.3.0


> Serge,
>
> We're all tested and ready to go.  I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.
>
> What is the nature of the bug?  Is there a workaround?  Does it effect
> normal users with the current set of mailets?
>
> --- Neol
>
> -----Original Message-----
> From: Serge Sozonoff [mailto:serge@globalbeach.com]
> Sent: Thursday, December 05, 2002 13:49
> To: James Developers List
> Subject: javamail 1.3.0
>
>
> Hi All,
>
> I brought this up a while ago and just thought I would mention it again as
a
> little reminder...
> I just ran into another javamail 1.2.0 bug when coding one of my mailets,
we
> really should upgrade to javamail 1.3.0.
>
> I guess this will have to wait till the next release.....?
>
> Serge
>
>
> --
> To unsubscribe, e-mail:
<mailto:james-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:james-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message