Hello Johann, Sunday, February 13, 2005, 11:07:01 PM, you wrote:
This should not have anything to do with your problem, but from your debut listing I noticed, JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj0.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj1.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj3.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj_arc.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj_eng.cf JS> debug: config: read file /etc/spamassassin/70_sare_genlsubj_x30.cf 70_sare_genlsubj.cf is just a concat of the next 3 files (and genlsubj2.cf, which is largely a no-op). If you're going to use genlsubj.cf, remove those next three. If you're using those three and don't want genlsubj2, remove genlsubj without the suffix. Since you're running SA 3.0, remove the x30 file, which has rules implemented in 3.0. JS> debug: config: read file /etc/spamassassin/70_sare_header.cf JS> debug: config: read file /etc/spamassassin/70_sare_header0.cf JS> debug: config: read file /etc/spamassassin/70_sare_header1.cf JS> debug: config: read file /etc/spamassassin/70_sare_header2.cf JS> debug: config: read file /etc/spamassassin/70_sare_header3.cf JS> debug: config: read file /etc/spamassassin/70_sare_header_arc.cf JS> debug: config: read file /etc/spamassassin/70_sare_header_eng.cf JS> debug: config: read file /etc/spamassassin/70_sare_header_x264_x30.cf JS> debug: config: read file /etc/spamassassin/70_sare_header_x30.cf Likewise, header.cf is a concat of the next four files. There's no harm in specifying a rule twice, but it is overhead during the SA startup. Use either header, or header0-3, but not both. And since you're running 3.0, remove the x264_x30 and x30 files. Bob Menschel
