>> I'll tell you one thing. SHIT happens, whether you use Qmail, Notes
>> or James. And unfortunately YOU are not the ones who get paged at
>> 11:30 pm out on a dinner date because the friggin's server has
>> gone down...
No ... but I have had my cell phone called from the data center when a
system failed, and have to decide about abandoning my vacation and driving
back 300 miles to deal with it.
So far the only break-in I've ever had on a system came courtesy of a PHP 3
vulnerability caused by the one site I allowed to use it. Fortunately, it
was limited by other security precautions, and the exploit has since been
patched by both belts and suspenders.
> > IMO Don't use James in critical heavy traffic scenarios. Do use james
where
> > having a java mail API in the server gives your business a real
advantage.
> > In part I agree this discussion addresses James' competitor in one
field, but
> > don't forget the whole other half of James' uphill struggle is our other
> > competitor, M$ Exchange.
> James, then, is addressing concerns different from mine: you're playing
the
> Notes/iPlanet/Exchange game, a sector of the market I don't care about.
I would not put Notes and James in the same category. James and Exchange
maybe, in the sense of James wanting to offer an IMAP service, which would
support IMAP-based groupware. In many respects, James and qmail seem more
similar: they are built from modular services, a pipeline and message
stores. Other than feature differences (James lacks ezmlm's functionality
right now), the significant difference is that currently James has its
analogues to qmail, ezmlm and qmail-pop3d all in one JVM. That is the only
similarity to Notes that I see, and it is superficial, in my view.
>> Now, I _know_ that Qmail gives me a very good chance to finish my dinner,
>> get back home and have a good night of sleep. Will James do the
>> same thing?
It does for me. Don't use it until it you feel that it would for you, too.
> Turns out that our bandwidth is saturated by Sobig/E messages,
> our front-exchanger sendmails and qmails have no whatsoever
> problem in handling that ...
What allows them to keep up? Are they fast enough to rejecting messages in
real-time, or is it simply a much better pipeline, with rejection happening
on the backend(s) independent of the frontend?
Notes wasn't designed to be a high throughput MTA. A lot of newer Notes
features (we were using Notes 4.x and 5, if I recall correctly), always felt
like misplaced hacks bolted onto the core. I'm amazed that Notes still
holds up as well as it does. It ought to have been ditched in the original
Domino timeframe, re-architected from the ground up, and built using a real
database, real MTA, real web server, etc., in a modular fashion. Which is
why I would not want to add Notes features to James. In my view, it would
be better to facilitate integration between James, web app servers, and
other applications; and let James do what it does best.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
