If I misunderstood, then I'm sorry. Your statement (quoted below) was both
dismissive and not in agreement with what I actually said:

Thanks for the feedback. But I am pretty much confident that the user
> "Disconnect" does still not care and will not upgrade.
>

As to the rest of your message, on more useful topics :)

IHMO the documentation can still get some more love. The DSPAM wiki has
> already a bunch of entries that help users installing and configuring DSPAM.
> But none of them is so fool proof. I personally find them all good enough
> but I see so many users out there that have just basic understanding of *nix
> systems, let alone messaging infrastructure. And those users then follow
> some how-to and try to build a mail server including virus scanning,
> anti-spam, etc... and they fail missarably. I really don't know how to make
> the documentation so good that those users would be able to install and
> configure DSPAM without issues?
>

I think the dspam docs could benefit from some basic ingredients, instead of
recipes. (I haven't looked at them in a while, so maybe this is already the
case.) But for example, instead of saying "this is how you install an os,
and a mailserver, and dspam, and amvis, and tie it all togerther, and.."
maybe some much simpler articles.

Documenting postfix/amvis/clamav/sendmail/courier/exim/... is not the job of
the dspam docs. Documenting dspam, preferably with helpful links outward,
should be a lot easier. For example, I would think that this is a fairly
long/mostly complete list of walkthroughs:
 - Installing dspam and using it for a single user, with .forward or
procmail and no database (sqlite).
 - Same, with a database. (Without getting into a lot of db education, just
"create a user 'foo' and put the password here in the dspam config.." and
links to the appropriate database sites.)
 - How to run dspam as a daemon (with the above setups, or just a note that
you can change commandlines from "dspam" to "dspamc" globally to take
advantage)
 - How to run dspam as an LMTP server. Not "how to use it with postfix and
amvis and clamav and .." but just "This is how to start an LMTP server" and
links to the postfix/courier/sendmail/... doc pages for how to make them
talk to an LMTP server.
 - How to tell dspam to send mail to a second LMTP/SMTP server
 - How to run dspam as an SMTP server.

Again, I haven't reread the docs in quite a while, so some of these things
might be irrelevant, incorrectly described or non-sensical. I think the
general idea comes across though. With those docs, the older/more
complicated howtos could be restored as a much simpler set of recipes using
those ingredients:

   - Follow [Installing DSPAM], then [Using a database], then [LMTP].
   - Optionally, now you can [Including antivirus scanning from DSPAM]
   - Congratulations, DSPAM is now available to use as a mail filter!
   - To get your particular mail server talking to it, reference their docs.
   (For example, if you are using postfix, you want to go to [
   postfix.com/docs/foo.html]. For exim, go to [exim.com/...] etc.)

Does that make sense?
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to