28 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Re: Spelling and othe...
FromSent OnAttachments
oth...@freeshell.orgDec 21, 2004 1:57 pm 
Brian CandlerDec 28, 2004 3:11 am 
Sam VarshavchikDec 28, 2004 4:16 am 
Paul L. AllenDec 28, 2004 11:32 am 
oth...@freeshell.orgDec 28, 2004 7:45 pm 
oth...@freeshell.orgDec 28, 2004 8:45 pm 
oth...@freeshell.orgDec 28, 2004 9:02 pm 
Paul L. AllenDec 29, 2004 3:28 am 
oth...@freeshell.orgDec 29, 2004 11:39 am 
Paul L. AllenDec 29, 2004 1:18 pm 
oth...@freeshell.orgDec 29, 2004 2:34 pm 
Paul L. AllenDec 29, 2004 4:50 pm 
oth...@freeshell.orgDec 29, 2004 9:08 pm 
Brian CandlerDec 30, 2004 1:10 am 
Brian CandlerDec 30, 2004 2:29 am 
Paul L. AllenDec 30, 2004 9:56 am 
Paul L. AllenDec 30, 2004 12:15 pm 
oth...@freeshell.orgDec 30, 2004 2:39 pm 
oth...@freeshell.orgDec 30, 2004 3:14 pm 
Paul L. AllenDec 30, 2004 4:07 pm 
Brian CandlerDec 31, 2004 2:40 am 
Laurent WacrenierDec 31, 2004 3:00 am 
Paul L. AllenDec 31, 2004 3:41 am 
Brian CandlerDec 31, 2004 4:11 am 
Pawel TeczaDec 31, 2004 4:47 am 
Laurent WacrenierDec 31, 2004 5:22 am 
Brian CandlerJan 1, 2005 4:45 am 
Brian CandlerJan 1, 2005 5:17 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] Re: Spelling and other templates (Was: stale processes and m17n)Actions...
From:Brian Candler (B.Ca@pobox.com)
Date:Dec 31, 2004 2:40:50 am
List:net.sourceforge.lists.courier-sqwebmail

On Fri, Dec 31, 2004 at 12:07:38AM +0000, Paul L. Allen wrote:

I'm serious. We're getting a lot of people who insist on switching their dedicated mail servers to Exchange to get the functionality that Exchange offers and which is not yet available in the alternatives (at least not without each user installing custom connectors in Outlook). We're losing ground here.

This isn't a race you know, and even if it were, it wouldn't be against Exchange - it would be against other open source software products.

Let people install Exchange if they want to. Each person has to make their own decision as to what meets their performance/price/supportability needs sufficiently. But for someone who wants to build a mailserver with 100,000 (or even 10,000) mailboxes, Exchange simply won't cut it.

The "competition", if you want to look at it like that, is against other open source packages. If someone writes a free IMAP server which is more robust, more featureful and more scalable than courier-imap, then I'll probably switch to it. Having comprehensive documentation and good support would be factors in that switch, but only minor ones. If I find a really well documented IMAP server which doesn't work as well as courier-imap, I'm not going to switch.

Not because the alternative is superior or because its additional features are actually useful but because we can't match the tick list. People are willing to pay big money for Exchange just so that webmail looks exactly like Outlook because they can't cope with the unfamiliar.

Good, then let them.

If we cannot at least make it relatively painless for people to find a readme in sqwebmail about adding extra dictionaries we're going to lose ground even faster. "Let me see. I can pay an expensive programmer to spend a day learning about sqwebmail and figuring out how to add stuff like dictionaries for French, or I can pay a point-and-click-monkey to spend an hour installing Exchange and get all that and more. Decisions, decisions."

You can't be serious. Anyone in that category won't even be looking at Unix-based solutions. Perhaps if sqwebmail were offered as a one-click install for Windows then it would be different (bundled with Apache and an MTA, of course)

writing something from scratch. If you're really big and owned by Microsoft, like Hotmail, you can run Exchange and glibly ignore the per-seat licence fees because they don't apply.

Sorry? I thought that Hotmail doesn't use Exchange at all. That's simply because it can't scale that far.

The harder it is then the more likely that eventually Sqwebmail usage will decline to the point where Sam can no longer afford to work on it, and it dies.

That is a risk, but mitigated by the open source licence. The project can fork and/or be taken over by new maintainers (as has just happened with fetchmail)

I don't know if Sam receives any income for courier-related work. I suspect he writes these packages mainly for his own usage, so as long as he uses them, he will maintain them - in a way which suits his own needs primarily. He has strong opinions as to what should or should not be in there, and is the only person who commits changes.

Having said that, if someone wants to *volunteer* to write a decent handbook for courier (say in docbook format), which mops up all the scattered READMEs and FAQs into a single place and includes step-by-step guides for installers and admins, I'm sure he wouldn't object as long as the information it gives is accurate. And even if it doesn't make it into the official release, they can always host it separately.

Regards,

Brian.