Kenneth P. Turvey wrote:
I'm using a derby database for the spools and such. I think it had a problem with finding a place to put things. I wasn't sure what to do to get it to work, so I turned it off. Should I give it another shot and provide you people with error details? I assumed it wasn't a fully implemented feature yet.
I use MySQL for storage but Derby must be pretty similar. I'm sure if you send a partial stack trace and/or any messages, someone will be able to set you straight.
Just for reference there is more documentation on the James Wiki [1].
I thought spamcop would work better than it does.
Just think of Blacklists as just one of many measures you need to take to reduce spam. It's called 'defense in depth' where you put up as many barriers as you practically can in the hope that spam will fail to get through one of them. I happen to think that Bayesian analysis is one of the more effective measures but it is by no means the perfect solution on its own. For one thing it always needs constant feeding so it can detect the latest style of spam.
Other techniques you may want to research include: Teergrubing[2], VERP[3], Tarpitting[4], Greylisting[5], SPF[6]. The list goes on and on! Luckily, most 'normal' people use major ISPs for their email and the ISPs do the defense in depth thing for them. If 'normal' people were exposed to the fantastic amounts of spam without any form of protection they would be amazed!
Regards, David Legg [1] http://wiki.apache.org/james/Bayesian_Analysis [2] http://www.iks-jena.de/mitarb/lutz/usenet/teergrube.en.html [3] http://cr.yp.to/proto/verp.txt [4] http://www.palomine.net/qmail/tarpit.html [5] http://projects.puremagic.com/greylisting/whitepaper.html [6] http://new.openspf.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
