https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6481
--- Comment #3 from Mark Martinec <[email protected]> 2010-08-10 05:34:09 UTC --- > For anything other that reports and header additions, a second reading > of the file is harmless. There are other settings too that are affected (black/whitelists, trusted/internal/msa_networks, ...). Double reading of a .cf file is not innocent and should not occur unintentionally. I don't think the MIMEDefang does it, nor the SpamAssassin by itself. > I have also queried on MIMEDefang's mailing list, but no replies there yet. Try enabling SA debuging in your mimedefang.cf and grep the output for 'config: read file'. See what files are really being read and when. I don't know if there is a proper way to enable SA debugging under mimedefang.pl, but you can add a 'debug => 1,' into the list of arguments for a SA call in a file mimedefang.pl, e.g.: my $sa_args = { local_tests_only => $SALocalTestsOnly, dont_copy_prefs => 1, userprefs_filename => $config, debug => 1, }; which will let SpamAssassin write its logging to stderr. It's probably necessary to avoid running mimedefang.pl as a server in order not to lose stderr, but you can invoke it manually giving it a directory with its protocol files as the only argument. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
