Bug 6765

Summary:	Add option to spamassasin script to report from which .cf file messages were generated from when running -D --lint
Product:	Spamassassin	Reporter:	simon
Component:	spamassassin	Assignee:	SpamAssassin Developer Mailing List <dev>
Status:	RESOLVED WONTFIX
Severity:	enhancement	CC:	apache
Priority:	P2
Version:	unspecified
Target Milestone:	Undefined
Hardware:	All
OS:	All
Whiteboard:

Description simon 2012-02-24 12:21:07 UTC

Example problem.
An error exists in a .cf file. Spamassassin -D --lint reports a warn and the possible problem.  e.g warn: missing body statement in ruleset.

* One cannot know which .cf file the error came from?  

Solution.
Add option to spamassassin to include the file where the error was found.
e.g. warn: missing body statement in ruleset, found in file myrules.cf
This could simply accessed by adding a -DD option to Spamassassin to increase verbosity.

Comment 1 Henrik Krohns 2019-07-08 09:51:16 UTC

The way SA internally handles all configuration, it would be very painful to implement. Anyway, such vague errors should not even exist anymore. Closing.