Here is something I want to give your guys. I am not a programmer, you are welcome that this script I wrote add to open suse as a cron job so that spamassassin always up-to-date. I might create a rpm for later when I learn how. Any cheers and enjoy. Free Back is Welcome. http://www.magidesign.com/index.php?option=com_content&task=view&id=45&Itemid=62 -- -- Command, n.: Statement presented by a human and accepted by a computer in such a manner as to make the human feel as if he is in control. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chuck Payne wrote:
Here is something I want to give your guys. I am not a programmer, you are welcome that this script I wrote add to open suse as a cron job so that spamassassin always up-to-date. I might create a rpm for later when I learn how.
Any cheers and enjoy. Free Back is Welcome.
http://www.magidesign.com/index.php?option=com_content&task=view&id=45&Itemid=62
Hi Chuck, one mistake I see in the script is that it starts both amavisd and spamd. If you're running amavis, you should not start spamd, since it's a duplication and a waste of resources at best. amavis essentially takes the place of spamd. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-11-17 at 10:29 -0800, J Sloan wrote:
Hi Chuck, one mistake I see in the script is that it starts both amavisd and spamd. If you're running amavis, you should not start spamd, since it's a duplication and a waste of resources at best. amavis essentially takes the place of spamd.
That's generally not true. You can, for instance, disable spam checking in amavis, and use spamc later, with per-user bayesian databases, which is a more powerful configuration than amavis. In fact, I don't know how to use per-user bayes databases with amavis-new: it uses a global, system-wide, database. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFXmcktTMYHG2NR9URAjScAJ4lOHRozhLwBA7SoMUg2gVpYu5HSwCePjCs xAF8CPbv5ag/ZhwYwYAHNMg= =Reb0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Friday 2006-11-17 at 10:29 -0800, J Sloan wrote:
Hi Chuck, one mistake I see in the script is that it starts both amavisd and spamd. If you're running amavis, you should not start spamd, since it's a duplication and a waste of resources at best. amavis essentially takes the place of spamd.
That's generally not true.
You can, for instance, disable spam checking in amavis, and use spamc later, with per-user bayesian databases, which is a more powerful configuration than amavis. In fact, I don't know how to use per-user bayes databases with amavis-new: it uses a global, system-wide, database.
In general, spam is spam. In the odd case that someone wants spam, there are mechanisms within amavis to allow a user increased spam, up to allowing all spam to that user. While in some cases I suppose one might use amavis for virus only and use spamc/spamd for spam detection, that is the exception, and I've never seen anybody purposely use both spamd and amavisd to run spam assassin. Loading the sa perl classes via amavis is very efficient. For any serious spam fighting scenario though, we run maia mailguard, which uses a specially modified version of amavisd-new. In mailguard, the per user white/blacklists, and SA thresholds can be set by each user for himself in the web interface. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-11-17 at 18:04 -0800, J Sloan wrote:
In general, spam is spam. In the odd case that someone wants spam, there are mechanisms within amavis to allow a user increased spam, up to allowing all spam to that user.
While in some cases I suppose one might use amavis for virus only and use spamc/spamd for spam detection, that is the exception, and I've never seen anybody purposely use both spamd and amavisd to run spam assassin. Loading the sa perl classes via amavis is very efficient.
I do, and I did tell you why. I'll try again because you do not understand. Amavis uses one single bayes database for all the users in the system, whereas spamc called from each user procmail uses an independently trained database for each user. This type of setup can be individually tailored to the type of spam received by each one. My system is small, so I can get away with that. So, I have disabled spam scanning in amavis, it doesn't load that part. I would like to know how to tell amavis-new to use a different bayes database for each user, but I don't know how. So I can't dispense with spamd, unfortunately: the bayes spam checking method is the one that makes here the biggest contribution, so I need it. The mail setup at SuSE is of the amavis-new type you propose, with one global bayes database. It doesn't work well, it has had to be disabled for the lists because lots of mails were marked as spam and were not. That proves that is not a good method.
For any serious spam fighting scenario though, we run maia mailguard, which uses a specially modified version of amavisd-new. In mailguard, the per user white/blacklists, and SA thresholds can be set by each user for himself in the web interface.
Seems nice. What about the bayes database? I know that amavis can be independently configured for each user. But I haven't read about doing the same with the bayes database. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFXuMLtTMYHG2NR9URAmEEAJsH6EgImbJeSI2RPs8362MKtLaVtQCglCck dxqP/XVku6XqYZ9y/jpI5KQ= =IA7v -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
I do, and I did tell you why. I'll try again because you do not understand.
Actually I do understand, as I noted before. I have even run a system in the very way you described, using amavis only for virus, and using spamc/spamd for spam detection. I still say this is an odd corner case. I'm not saying it won't work.
Amavis uses one single bayes database for all the users in the system, whereas spamc called from each user procmail uses an independently trained database for each user. This type of setup can be individually tailored to the type of spam received by each one. My system is small, so I can get away with that.
So, I have disabled spam scanning in amavis, it doesn't load that part. I would like to know how to tell amavis-new to use a different bayes database for each user, but I don't know how. So I can't dispense with spamd, unfortunately: the bayes spam checking method is the one that makes here the biggest contribution, so I need it.
The mail setup at SuSE is of the amavis-new type you propose, with one global bayes database. It doesn't work well, it has had to be disabled for the lists because lots of mails were marked as spam and were not. That proves that is not a good method.
I'm currently supporting a number of sites that use suse mail servers with the single bayes database for all the users. The largest site has 13,000 users, and in practice there doesn't seem to be a problem with, as you say, one man's spam being another man's treasure. For the most part spam is spam. *everyone* thinks the viagra ads are spam. For the case where someone might want to get viagra adds, that is why the per-user whitelists exist; the individual user can exempt specific senders or domains from spam checking entirely, for messages sent to him.
Seems nice. What about the bayes database?
I know that amavis can be independently configured for each user. But I haven't read about doing the same with the bayes database.
It's a single bayes database, but the individual whitelists and per-user thresholds help make that not a problem in practice. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Carlos E. R.
-
Chuck Payne
-
J Sloan