I was looking into spam solutions for debian's bug processing and list processing systems. Apparently they use some spam processing now but spamassassin seems to be an excellent choice to improve it and bring it up to date. I especially like the inclusion of razor; I believe the debian list processor can be a contributor to the net community by identifying spam early. These processing systems handle hundreds of public addresses. Unfortunately, it's a giant spam magnet -- but we could turn that to our advantage using razor!
I'd like to submit a bug report suggesting spamassassin. The report would have to include any configuration gotchas and probably it would be helpful if it could include setup instructions tailored to that usage. I downloaded the source for debbugs, and I see it is a perl script. So the SpamAssassin module could be called directly from there. But spamd seems like a much better solution because it's a high-volume situation, and we don't want to lose any processing time we don't need to lose. In fact, if the spam processing slows the system appreciably, I'm sure it would be turned off before it got a chance to do any good. Since each message is being processed by a perl program anyway, would spamd really help? Or, should spamd be applied upstream, in procmail (at lease I assume procmail is in use), to be most effective and least intrusive? I noticed DEBBUGS parameters in the standard etc/spamassassin.cf; For usage on the debbugs server itself, those would need to be disabled, right? Security concerns would be paramount in this usage. Would you recommend proceeding with a single spamd user or such, and how would you go about securing things so no one could possibly use debbugs' spam processing to do something untoward? I've only just downloaded spamassassin myself, but I can see right off it's the best of class. Any assistance you can provide to help me write a first-class bug report which has a chance of being adopted would be appreciated. The debian lists are getting several spams per day, and the bugs themselves are filling up with spam. I ran across one bug with 1200 pages of spam in its archive. It's a huge waste of people's time in the bug system; because there's no way to browse the bugs by subject, skipping the spam, one has to plow through it whenever it comes up. And many many people are reading these bugs over and over again, the multiplier effect = lots of wasted volunteer effort. (Please cc me, I'm not on the list.) -- *------v--------- Installing Debian GNU/Linux 3.0 --------v------* | <http://www.debian.org/releases/woody/installmanual> | | debian-imac (potato): <http://debian-imac.sourceforge.net> | | Chris Tillman [EMAIL PROTECTED] | | May the Source be with you | *----------------------------------------------------------------* _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
