Bug 6765 - Add option to spamassasin script to report from which .cf file messages were generated from when running -D --lint
Summary: Add option to spamassasin script to report from which .cf file messages were ...
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-24 12:21 UTC by simon
Modified: 2019-07-08 09:51 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.