I still see no evidence of a message-id being inserted into debug logs to allow tracking. Or any evidence of time stamping.
This bug was supposed to have been subsumed and corrected by another one, but these two factors have never appeared in my logs as of cvs yesterday (2.40). Maybe I don't understand how to get this information. spamd manpage seems not to mention any of it, other than listing -D as debug flag, and -s about syslog. I'm running spamd like this from /etc/rc.d/init.d/spamassasin (init script) : /usr/bin/spamd -D -L -S >> /var/log/spamd_debug.log 2>&1 & ps shows: root 868 [...] 0:01 /usr/bin/perl -w /usr/bin/spamd -D -L -S What is the trick to get trackable information out of the logging facility? Example: I have a message bearing no sign of having been thru spamc. However my procmail.log indicates it has. 16962 procmail: Executing "/usr/bin/spamc" 16963 procmail: No match on "^X-Spam-Status:[ ]*\/.*" 16964 procmail: No match on "^X-Spam-Status: Yes" [...] 17000 Message-Id: <[EMAIL PROTECTED]> Apparently no X-Spam-Status was inserted. And checking the actual message, yes that is the case. Now ... why. How do I find this message in my debug log? Surely this can be made trackable some how. The prefix debug or logmsg really isn't much to work with. Only this one message seems to have been handled this way. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
