Stephane, On 15 Jan 2003, Stephane wrote:
> I think most companies are afraid of implementing opensource software as > a component for an important service such as email. I think that > generally even though people know email has not been designed to be a > 100% reliable protocol they still make business with it. Quickly look at the headers of the emails received (and sent) by these companies. They will probably find that most email is routed by open source software. Also, have a look at these surveys, which indicate that most mail servers run open source software: http://www.ornl.gov/cts/archives/mailing-lists/qmail/1997/08/msg00005.html http://www.linuks.mine.nu/smtp/ http://www.ohse.de/uwe/surveys/smtpserver19971031.html http://cr.yp.to/surveys/smtpsoftware6.txt http://cr.yp.to/surveys/smtpsoftware5.txt http://cr.yp.to/surveys/smtpsoftware4.txt http://cr.yp.to/surveys/smtpsoftware3.txt http://cr.yp.to/surveys/smtpsoftware2.txt http://cr.yp.to/surveys/smtpsoftware.txt > The major fears are: > - opensource software is often made by hobbyists and these people do not > have the structure to provide software support/bugfixes, or quick > response to a big problem incurring financial losses (no emails go > through for example!) This may be true. But the decision should be made on a case-by-case (per software) basis. Nevertheless, commercial support contracts are always available (even if by unrelated third-party), from companies like Red Hat and Puget Sound Technology. > - are upgrades straightfoward and not causing problems to the existing > running system, are they well tested. Not applicable. Because this also applies to proprietary, commercial, closed-source software. On the other hand, with open source, if you are qualified (or if you pay someone who is qualified), you can review, audit and/or test for yourself. > - what if the SA project is abandoned, what if the source is bought by a > commercial vendor, in other words, what if SA as it exists today > disappears ? With opensource you cannot have a contractual engagement to > provide support or updates, nor can you really know the roadmap for a > product and what is planned for future development So find a tech support company that will give you a contractual agreement for maintaining the particular open source software. (Anecdote: I helped revive dead gnu-pop3d and I am often paid to install, maintain, and support the forked version of it.) > I am desperate to get SA implemented (I just love it!!) but we wouldn't > like to reinvent the wheel if someone else did a similar implementation I am not sure what you mean. There are similar tools and filters. > I appreciate this is a very long email (apologies), if this post has got > nothing to do with this mailing list, I am more than happy to carry the > discussion off it with anyone who feels they are in the same position as > me, as my company. If you have any questions about open source advocacy, professional support for open source software, feel free to email me off-list or visit http://www.pugetsoundtechnology.com/ . Jeremy C. Reed http://www.isp-faq.com/ ------------------------------------------------------- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
