I have developed a hypothesis, which could explain eventually this strange phenomenon:
spamassassin reads the configuration files directly, but not spamd --- during installation the rules were compiled by the Debian postinstall script into a format, which is read exclusively by spamd during launch, ignoring all changes to the configuration files without recompiling them. (that seems to me the only logical explanation, so don't laugh, if this sounds really strange) If this keen hypothesis should be true: how can I find resp. execute the compilation and what is the best way, to debug/trace the actual run of spamd after invocation by amavis? (the debug option and strace were no great help so far). Sorry, but I'm considerably confused meanwhile! -- Registered Linux-User #169380 on http://counter.li.org/ ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
