Bug 6747 - Provide more verbose debug output with sa-update and spamassassin
Summary: Provide more verbose debug output with sa-update and spamassassin
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.3.1
Hardware: PC Linux
: P2 minor
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
Depends on:
Reported: 2012-01-03 03:24 UTC by Nelson A. de Oliveira
Modified: 2012-01-03 14:46 UTC (History)
0 users

Attachment Type Modified Status Actions Submitter/CLA Status
Config File showing locale specific lint issues application/octet-stream None Kevin A. McGrail [HasCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Nelson A. de Oliveira 2012-01-03 03:24:19 UTC
At bug 6746 it's possible to see that by using "spamassassin --lint -D" it's still not possible to see where the real problem is present (or where to search for it).

spamassassin's manpage says that -D "Produce debugging output. If no areas are listed, all debugging information is printed." thus making us understand that we should get all the debug available by using a simple "-D" option.

If something else is necessary to pass to -D then the manpage needs some adjustment. Otherwise, it's seems necessary to have a more verbose option/output for debug.

Using bug 6746 as example, it should say that something was wrong in 30_text_pt_br.cf (with the line number and maybe column/keyword/option of the failed check, if possible).

Also, when using -D it gives a somehow redundant/cyclic message that says "warn: lint: 1 issues detected, please rerun with debug enabled for more information" but we are already running with debug enabled, right?

It at least applies to sa-update and spamassassin.

Thank you!
Comment 1 Kevin A. McGrail 2012-01-03 14:46:05 UTC
Created attachment 5033 [details]
Config File showing locale specific lint issues

The attached cf file (which is resolved), will cause lint errors with the command:

LC_ALL=pt_BR.UTF-8 spamassassin --lint

More information about the lint errors would be useful such as the rules file that has the error.