Thursday, September 23, 2004, 2:01:58 PM, Theo responded: TVD> On Thu, Sep 23, 2004 at 09:35:39AM -0400, Rob Kudyba wrote: >> /etc/mail/spamassassin root# /usr/bin/spamassassin --lint -D >> debug: config: read file //etc/mail/spamassassin/70_sare_html.cf >> debug: config: read file //etc/mail/spamassassin/70_sare_oem.cf >> debug: config: read file //etc/mail/spamassassin/70_sare_random.cf >> debug: config: read file //etc/mail/spamassassin/70_sare_ratware.cf >> debug: config: read file //etc/mail/spamassassin/70_sare_specific.cf >> debug: config: read file //etc/mail/spamassassin/70_sare_spoof.cf >> debug: config: read file //etc/mail/spamassassin/72_sare_bml_post25x.cf >> debug: config: read file //etc/mail/spamassassin/99_FVGT_Tripwire.cf >> debug: config: read file //etc/mail/spamassassin/99_sare_fraud_post25x.cf >> debug: config: read file //etc/mail/spamassassin/99_sare_fraud_pre25x.cf TVD> can't help you with these.
However, 99_sare_fraud_post25x.cf and 99_sare_fraud_pre25x.cf are CONFLICTING files. pre25x is supposed to be used only for SA 2.4x and older, while post25x is supposed to be used for 2.5x, 2.6x, 3.xx.xx Get rid of the bad file. >> warning: description exists for non-existent rule SARE_SUB_CASINO_OB1 TVD> all third party rules -- go talk to the people who wrote them. There is no current SARE rule with this name. SARE_SUB_CASINO_OB (without any digit at the end) is in 70_sare_genlsubj1.cf, which you do NOT list in your list of custom files above. I scan all current SARe files and I do not find any rule or description with the name your system is complaining about. Find out where that is and get rid of it. (Simply refreshing your files from the current SARE rules might do the trick.) Bob Menschel
