Ok, just understood the reason of the warnings : I
found a no_osiru.cf file in my
/etc/mail/spamassassin
no-osiru.cf:score RCVD_IN_OSIRUSOFT_COM 0
no-osiru.cf:score X_OSIRU_DUL 0
no-osiru.cf:score X_OSIRU_DUL_FH 0
no-osiru.cf:score X_OSIRU_OPEN_RELAY 0
no-osiru.cf:score X_OSIRU_SPAM_SRC 0
no-osiru.cf:score X_OSIRU_SPAMWARE_SITE 0
and these rules aren't defined anywhere
else.
It seems ilke it's a prety old file (2003) but I really
don't know why it's here... espacialy because I can't found the same one on my
main server !
I've moved this file somehere else and now the spamassassin
--lint doesn't give any waning
De : Stéphane LEPREVOST [mailto:stephane.leprevost (at) soget.fr]
Envoyé : vendredi 13 octobre 2006 09:44
À : 'users@spamassassin.apache.org'
Objet : Upgrading to 3.1.7
I'm planning to
upgrade my server from SA 3.1.5 to SA 3.1.7 and want to be sure that I had well
understood about theses warnings :
spamassassin
--lint
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_DUL
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_SPAM_SRC
[19969] warn: config: warning: score set for non-existent rule RCVD_IN_OSIRUSOFT_COM
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_OPEN_RELAY
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_DUL_FH
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_SPAMWARE_SITE
[19969] warn: lint: 6 issues detected, please rerun with debug enabled for more information
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_DUL
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_SPAM_SRC
[19969] warn: config: warning: score set for non-existent rule RCVD_IN_OSIRUSOFT_COM
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_OPEN_RELAY
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_DUL_FH
[19969] warn: config: warning: score set for non-existent rule X_OSIRU_SPAMWARE_SITE
[19969] warn: lint: 6 issues detected, please rerun with debug enabled for more information
I've already made
the upgrade on a test server and it seem to works
fine1
Can someone confirm
me that on one hand SA 3.1.6 was considering this as a blocking error and
on the other hand that the reason of realising à 3.1.7 version was to consider
this just like a warning ?
May I upgrade
without risks despite these messages ?