>From the first paragraph of the James website:
"The Java Apache Mail Enterprise Server (a.k.a. Apache James) is a 100% pure
Java SMTP and POP3 Mail server, and NNTP News server designed to be a
complete and portable enterprise mail engine solution based on currently
available open protocols. "
Not that my opinion matters much, but I am +1 on delaying the release of 2.1
and getting NNTP working as it did in 2.0a3. Incompatibility with OE really
is a showstopper as it is probably the most widely-used NNTP client.
Disabling core functionality is fine for a beta/technical preview, but not
for a final release. If 2.1 is release without NNTP functional, it sends a
bad message to the user base, who expects mail and news to be rock-solid
above all else.
It also reflects badly on the James community and gives the impression that
sloppy coding, QA, and project management are the norm. James won't go
anywhere with that kind of reputation.
This issue may not have been exposed and discussed in the most appropriate
manner, but the passion with which Harmeet pushed this shows that people
rely on James for NNTP service and need it to be functional.
Matt Bishop
[EMAIL PROTECTED]
"We are all here on earth to help others. What I can't figure out is what
the others are here for."
- W. H. Auden
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
