https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6195
--- Comment #4 from John Hardin <[email protected]> 2009-09-08 16:43:20 PST --- (In reply to comment #3) > (In reply to comment #2) > > Actually, it's in response to a thread currently underway on the users list, > > where the OP was lamenting that SA didn't log the first external IP address > > (among other bits of the message). > > That's an entirely different cattle of fish then. That user is missing the > spamd logs where it does report all rules hit, the score, user and much more. > About all he has are the prefork logs -- a user problem, SA does indeed log > more. I pointed that out to him, I don't know if he picked up on my comment. > So the next stop is a simple, custom logging plugin. Easy to log what he asked > for -- not sure if it also could log arbitrary rules' matches. Probably not, > I'm afraid. That's why I suggested a tflag rather than a plugin. It's more flexible. > Anyway, he first needs to sort out his log issues. That's outside the scope of > this enhancement request. As-is, this cannot possibly help him. Agreed, but it did suggest the idea. > > I was thinking such a tflag would be a more-general solution than playing > > whack-a-mole with hardcoded lists of "what about the message do we want to > > log?" > > My interpretation sounds more like a promising reason to ever implement this. > ;) That, too. :) > > Granted you could easily blow your foot off with it... :) > > Definitely agreed. WRT this reason for the enhancement request, I'd be much > more happy with some options to add logging lines or alter existing ones. And > restrict its scope to the templates, rather than arbitrary RE matches. But what about the Unix philosophy of "here's plenty of rope..." -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
