> James v2.1.2 has been released.  This release fixes a critical bug that
> could result in a loss of messages from the outgoing spool under
> a specific
> set of circumstances.  Users should upgrade to James v2.1.2 as soon as
> possible.
>
> The bug was discovered Thursday afternoon, with a nightly build to fix it
> available Thursday evening.
>
> James v2.1.2 can be downloaded immediately.  Some mirrors sites
> have already
> picked up the new release.  Make sure that you download v2.1.2.
>
>  mirrors: http://www.apache.org/dyn/closer.cgi/jakarta/james
>
> James v2.1.2 also has improved MIME encoding of bounce messages,
> and better
> handling of SMTP transport errors.
>
>       --- Noel
>

Noel,

I had planned to upgrade last friday (February 21) my James server from
2.1.1a5 to 2.1.1, when I read your message about the critical bug fixed in
the 2.1.2a2 nightly release, so I upgraded to 2.1.2a2.
Now, having 2.1.2 been released immediately after on saturday 22, I wonder
if I should plan to upgrade to 2.1.2 shortly or if I can stay safely on
2.1.2a2 until either 2.1.3 comes out or some important bug fix is released:
in other words, which are the differences between 2.1.2a2 and 2.1.2 (I can't
see them from the changelog)?

Moreover, as today is one month since I switched the mail service of my
company to James, and I'm very happy of that, I want to take the opportunity
of this message to thank you and the other developers for the job you are
doing and the time you spend on it. It gives me the desire to contribute
somehow to it in the future. My appreciation goes also to the care given to
this list and its politeness.
If I had to summarize the reasons of my satisfaction with James, I would
mention the true simplicity, the flexibility allowed, the ability to keep
control of things happening, and the speed in finding and fixing problems.

Congratulations and thank you all,

Vincenzo


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to