Re: [qmailtoaster] how to stop a same spam
On Wed, 3 Jan 2007 19:41:52 +0700, Firdaus Tjahyadi wrote:
i have configure my /usr/share/spamassassin/70_sare_stocks.cf file like this
bodySARE_PHYA /Physicians Adult Daycare/i
describeSARE_PHYA PHYA
score SARE_PHYA 2.66
but it did'nt work, what is the best solution for kill that kind of spam
First of all, don't edit files under /usr/share/spamassassin. Your
customizations must go into /etc/mail/spamassassin/ (into a file ending with
.cf, like rules.cf for example). The rules under /usr/share/spamassassin will
be overwritten when you upgrade SA.
The best defense against stock-pushing stocks is to use sa-update nightly to
keep your rules updated from both the default spamassassin channel and the SARE
channels. Follow the instructions at:
http://wiki.apache.org/spamassassin/RuleUpdates
http://saupdates.openprotect.com/
Add something like this to cron (should be all on line line):
sa-update --channel updates.spamassassin.org --gpgkey
D1C035168C1EBC08464946DA258CDB3ABDE9DC10 --channel saupdates.openprotect.com
svc -h /var/qmail/supervise/spamd{,/log};
And you might want to automatically run lint to be sure nobody f'ed up:
spamassassin --lint || echo ERROR: Spamassassin lint failed.;
(Assuming the echo goes somewhere you'll see it, i.e. the emailed output from
cron.)
Quinn
-
Strangecode :: Internet Consultancy
http://www.strangecode.com/
+1 530 624 4410
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] how to stop a same spam
Don't forget
wget http://saupdates.openprotect.com/pub.gpg
sa-learn pub.gpg
Erik
On 1/4/07, Quinn Comendant [EMAIL PROTECTED] wrote:
On Wed, 3 Jan 2007 19:41:52 +0700, Firdaus Tjahyadi wrote:
i have configure my /usr/share/spamassassin/70_sare_stocks.cf file like this
bodySARE_PHYA /Physicians Adult Daycare/i
describeSARE_PHYA PHYA
score SARE_PHYA 2.66
but it did'nt work, what is the best solution for kill that kind of spam
First of all, don't edit files under /usr/share/spamassassin. Your
customizations must go into /etc/mail/spamassassin/ (into a file ending with
.cf, like rules.cf for example). The rules under /usr/share/spamassassin will
be overwritten when you upgrade SA.
The best defense against stock-pushing stocks is to use sa-update nightly to
keep your rules updated from both the default spamassassin channel and the SARE
channels. Follow the instructions at:
http://wiki.apache.org/spamassassin/RuleUpdates
http://saupdates.openprotect.com/
Add something like this to cron (should be all on line line):
sa-update --channel updates.spamassassin.org --gpgkey
D1C035168C1EBC08464946DA258CDB3ABDE9DC10 --channel saupdates.openprotect.com
svc -h /var/qmail/supervise/spamd{,/log};
And you might want to automatically run lint to be sure nobody f'ed up:
spamassassin --lint || echo ERROR: Spamassassin lint failed.;
(Assuming the echo goes somewhere you'll see it, i.e. the emailed output from
cron.)
Quinn
-
Strangecode :: Internet Consultancy
http://www.strangecode.com/
+1 530 624 4410
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] how to stop a same spam
that should be sa-update --import pub.gpg
Erik
On 1/4/07, Erik Espinoza [EMAIL PROTECTED] wrote:
Don't forget
wget http://saupdates.openprotect.com/pub.gpg
sa-learn pub.gpg
Erik
On 1/4/07, Quinn Comendant [EMAIL PROTECTED] wrote:
On Wed, 3 Jan 2007 19:41:52 +0700, Firdaus Tjahyadi wrote:
i have configure my /usr/share/spamassassin/70_sare_stocks.cf file like this
bodySARE_PHYA /Physicians Adult Daycare/i
describeSARE_PHYA PHYA
score SARE_PHYA 2.66
but it did'nt work, what is the best solution for kill that kind of spam
First of all, don't edit files under /usr/share/spamassassin. Your
customizations must go into /etc/mail/spamassassin/ (into a file ending with .cf,
like rules.cf for example). The rules under /usr/share/spamassassin will be
overwritten when you upgrade SA.
The best defense against stock-pushing stocks is to use sa-update nightly to
keep your rules updated from both the default spamassassin channel and the SARE
channels. Follow the instructions at:
http://wiki.apache.org/spamassassin/RuleUpdates
http://saupdates.openprotect.com/
Add something like this to cron (should be all on line line):
sa-update --channel updates.spamassassin.org --gpgkey
D1C035168C1EBC08464946DA258CDB3ABDE9DC10 --channel saupdates.openprotect.com
svc -h /var/qmail/supervise/spamd{,/log};
And you might want to automatically run lint to be sure nobody f'ed up:
spamassassin --lint || echo ERROR: Spamassassin lint failed.;
(Assuming the echo goes somewhere you'll see it, i.e. the emailed output from
cron.)
Quinn
-
Strangecode :: Internet Consultancy
http://www.strangecode.com/
+1 530 624 4410
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
