Everyone who has a particular favorite OS (or the only one they have ever used) keeps wanting detailed notes on how to use a particular package as a working example....
1) Although people who build from packages MAY need more help than others, it doesn't seem to be in couriers best interest to start documenting a preferred platform. 2) From what I've seen over the years (started with RH, Mandrake moved to OpenBSD, FreeBSD and have tried debian, Solaris, AIX, etc. etc.) MANY problems are caused by people not knowing what they are doing trying to follow a process which by it's nature is dependant on lots of other "packages" which may themselves be broken, incompatible or themselves dependant on other broken packages. If documentation has to reference a single method, going from source is the only way that makes sense ot the entire community... Sam has a lot of good material - if there are holes, or things that are unclear, the time might be better spent improving what we have to start with and ensuring it survives as a living document instead of sidestepping it and allowing it to slide. My 2 cents. m/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Constable Sent: Wednesday, October 08, 2003 6:32 AM To: [EMAIL PROTECTED] Subject: Re: [courier-users] Full courier Howto On Wed, 2003-10-08 at 22:40, Peter Holm wrote: > On Thu, 02 Oct 2003 21:17:37 +1000, you wrote: > > >Would anyone be interested in co-writting a full courier-only Howto > >similar in scope to this article ? > > If you do something like that please focus on things that are not > written [clearly enough] in the documentation. This could include > detailed explanations on setting up mailing lists with virtual > mysql-user accounts and mailman and detailed instructions for > amavisd-new, clamav and spamassassin or similar (free, of course) > antispam-/antivir combos. I only have a minimal subset of experience with mysql, and virtual hosting in general, so a lot of the really interesting anti-virus material I'd have to leave to someone else anyway. > Especially the last point should be made somehow easier for new > mailadmins (or people that DO have a fulltime job and must do all that > server stuff in the evenings... ;() Some docs for the rest of us would be great. > Also I vote for Debian as a base system with a hint on backports.org > to state clearly, where people can get new, working packages... I agree with that but RH packages and from-source are also popular. > I am certainly not skilled enough to act as a co-author but could give > comments from a dumbo-user point of view like "following this article > does not work for me because blabla..." Hey, you might surprise yourself :) I think the best way forward all around is to have a Wiki and let's see what happens... http://courier.opensrc.org Nothing there yet... everyone/anyone, please just paste notes or comments any which way and the RecentChanges junkies will take care of the rest and refactor it into something half sensible. --markc ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
