Will Nordmeyer wrote: > Matt, > > I ran lint this AM (I frequently forget that part :-)), and only had 2 > issues - > > warn: config: failed to parse line, skipping: use_dcc 1 > warn: config: warning: score set for non-existent rule RAZOR2_CHECK > > I can't find where the use_dcc or the RAZOR2_CHECK are set though. None of > the .cf files in /etc/mail/spamassassin have them.
Perhaps a user_prefs has them. Or if you have "inherited" a system,someone edited the /usr/share/ files? Or maybe someone put it in a .pre file in /etc/mail/spamassassin? grep use_dcc /usr/share/spamassassin/*.cf grep use_dcc /etc/mail/spamassassin/*.cf grep use_dcc /etc/mail/spamassassin/*.pre grep use_dcc ~/.spamassassin/user_prefs > > I tried running the spamassassin --lint --debug and dump the dbg output to a > file, but apparently I'm screwing up the redirect because my output file > always is empty. You can't redirect the debug output with > or |. It is output to stderr, not stdout. In bash type shells you can re-direct stderr using 2> instead of > > > I'm running via spamd and have restarted spamd. By the way, I'm running > V3.1.1 (and for some reason it puts @@CONTACT_ADDRESS@@ in the emails saying > that spam detection software running on blah blah blah - know how I can > easily fix that without having to rebuild?). That makes me fairly concerned about the integrity of the build. I'd strongly suggest rebuilding anyway. That said, you can edit /usr/share/spamassassin/10_misc.cf and edit the report_contact option there. BE VERY careful editing this, and be sure to lint afterwards. Note: In the general case I would advise against editing any of the .cf files in /usr/share/spamassassin. They will all be obliterated and re-written if you upgrade or re-install. In this case, that's perfectly fine.
