On 23 Jul 2010, at 19:47, Disconnect wrote: > 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. ... > 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?
I agree. I have Dspam tied in as a mail filter in Postfix and it "works", but it has several problems; it unnecessarily filters outgoing mail and is creating virtual users for every recipient I ever send mail to, for example. I have no idea how to solve those though. The trouble isn't with configuring Dspam, but with how it ties in to mail servers (which are complicated), a database, mail delivery things, etc. I'm no sysadmin, I don't understand everything I need to do to set Dspam up as the little spider between "everything" that it is. Now that it "works", I don't dare to touch it in fear that it'll blow up. I used parts of several "recipes" that were available at the Dspam site back then (nuclearelephant), but none of them exactly matched my situation, so I had to mix and match and ended up with something that mostly works as intended, but not entirely. What's worse, I can't even seem to find any documentation now. If you Google for Dspam you still end up at nuclearelephant, which links to the sourceforge project page that doesn't appear to contain any documentation. Best I could find was a wiki page listing the project goals... That said, upgrading Dspam itself hasn't been any trouble at all, although I seem to have a retraining problem using forwarding (I would prefer having the sig in the headers, but Apple mail drops X-headers when forwarding apparently). I don't want to give off the impression that I'm unhappy with Dspam - I'm not! - but especially at the documentation end it could use some love. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll see there is no forest. !DSPAM:1126,4c4acea4286218343215777! ------------------------------------------------------------------------------ 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
