On the GUI, you could say the same about Samba, but you're never going
to convince the GUI-centric hoardes of movers and shakers
I don't know any UNIX administator worth his salt who uses a GUI to admin a
server. Only Windows users are GUI-centric.
Sorry but small companies can't afford to have developers or admins all the time
around. Usually admins/developers are used once at install, and than a "little
more educated worker" does the rest. This is how it works in 90% of the small
companies and ignoring this won't change the situation.
That said, there are JAMES configuration tools out there.
Really :).
You mean something that's not PHP, not Telnet, and not cr.. (e.g. ajaconsole) ?
Well if so why don't you share this valuable information with the rest of the
world
hanging around here :) ?
If anyone wanted
to make a concerted effort to maintain one as part of JAMES, we'd be happy
for it.
No one I talked to has an idea about how do things work at Apache(especially
JAMES).
What are the process, who does what and when (or it would be supposed to), and why TF is so
complicated to make things move compared to other projects (also by Apache) ?
My impression and all other potential users I talked to was that this project is just "dragging
itself" till it will totally stop.
Even the "Feature Status" on the first page seems to be more than 3 years old.
Every time I tried to convince a manager to give JAMES a try, they look at the
first page, see the
"Feature Status" and ask:
- "Uh, no IMAP?".
- "How do I administrate it?" "Can my best employee do maintain it?"
"Well, than it makes no sense for us to drop Exchange".
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
