> The only difficulty I see in this is the vast array of different > configurations that ASSP could be used in... > > eg: Windows, Linux, OSx, with or without SQL support, multiple > ASSP servers with clustered SQL servers, local MTA's, etc etc...
Well... that's a "feature" more than a problem :) - seriously, yes, the wide variety of supported setups/platform and the flexibility of ASSP makes the documentation writing appearing a hard task although imHo a first doc, maybe not covering all aspects but just the main ones (along with the most common/recommended setups) may be a good starting point > Maybe a solution would be for people to write "how-to's" based on > their own particular config, and post them somewhere centrally.... > then maybe someone could write a document based on these various > ways of installing.... <<sigh>> I suspect that was the idea till some time ago, but then the asspsmtp.org site/wiki was ripped off and all the docs and infos got lost :( luckily some of the docs/howtos/snippets were retained and are now on the wiki http://sourceforge.net/apps/mediawiki/assp/index.php?title=Main_Page yet the task of "merging" them to generate a manual isn't simple > Thoughts? Heh... yeah; time ago I started thinking about creating a "virtual appliance" (e.g. vmware or the like) containing a stripped down Linux, ASSP, a DNS (unbound - http://unbound.net seems a good choice) and an SMTP daemon to be used as smarthost/forwarder for incoming/outgoing messages but the lack of time stopped me from progressing; the idea was to have an "image" which one may download and start, at that point, just connecting through SSH to the VM one would be presented with a "setup menu" (just textual stuff) to configure the various "core settings" like the VM IPs, the SMTP, the DNS and so on; at that point all the remainder of the config would be carried on by using the ASSP GUI; that would allow anyone to pick a copy of the appliance and have a "drop in" spamfilter; also, since in such a case the VM ASSP would already be configured with "recommended settings" for the various parameters, the task of customizing the ASSP setup would be easier and less error-prone ... the problem, as I wrote, was the lack of time, otherwise this would be imHo a good way to help spreading ASSP ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
