Mark wrote: > Luke,
>> I am having problems with spamassassin and amavisd on openbsd 3.7. >> Basically the mta accepts mail and checks it for viruses using clamav >> but it doesn't register any hits for spam. >> Amavis version: amavisd-new-2.3.2 >> Spamassasin vers: p5-Mail-SpamAssassin-3.0.2 >> Razor version: razor-agents-2.40 >> Clamav version: clamav-0.85.1 >> >> When I run the amavisd debug-sa it stops at debug: tests= >> debug: subtests=. > ... >> debug: bayes: 5651 untie-ing db_seen >> debug: metadata: X-Spam-Relays-Trusted: >> debug: metadata: X-Spam-Relays-Untrusted: >> debug: decoding: no encoding detected >> debug: is spam? score=0 required=5 >> debug: tests= >> debug: subtests= > See what happens if you do it manually, e.g.: > su vscan -c 'spamassassin -D -t < message.msg' > Could be a DNS problem. Use a recent version of Net::DNS > and check that resolver works. > Mark Luke's debug output showed SpamAssassin is expecting: using "/usr/share/spamassassin" for default rules dir So as a test I created an empty /usr/share/spamassassin directory and started up 'amavisd debug-sa'. I got the exact same error Luke shows here. "By default, configuration data is loaded from the first existing directory in: @@DEF_RULES_DIR@@; @@PREFIX@@/share/spamassassin; /usr/local/share/spamassassin; /usr/share/spamassassin ." To me this could indicate that at one time, the rules files were placed in /usr/share/spamassassin. Upon subsequent removal of that installation, and upon installation of another version, the rules were possibly placed in /usr/local/share/spamassassin but the empty /usr/share/spamassassin directory was left behind. Sounds good anyway. So, in this case, possibly simply deleting the empty /usr/share/spamassassin directory may solve the problem. At this point I imagine one could optionally create a symlink from /usr/share/spamassassin to the directory where the rules are currently stored. This may avoid issues like this in the future (or create new ones!). For the config files, it looks like there are a lot more places to look: "Site-specific configuration data is used to override any values which had already been set. This is loaded from the first existing directory in: @@LOCAL_RULES_DIR@@; @@PREFIX@@/etc/mail/spamassassin; @@PREFIX@@/etc/spamassassin; /usr/local/etc/spamassassin; /usr/pkg/etc/spamassassin; /usr/etc/spamassassin; /etc/mail/spamassassin; /etc/spamassassin ." I managed to ask Luke last night to tell me what was in /etc/mail/spamassassin. There is local.cf and nothing else. Local.cf is not configured. The absence of the init.pre file makes me think the installation is either incomplete or the config files from this particular installation are also somewhere else and /etc/mail/spamassassin/local.cf is also a leftover from a previous installation. Gary V ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
