SpamAssassin Debug Level

[MindStar]

The SpamAssassin daily rules updates switched back to verbose/DEBUG level reporting a couple of weeks ago.

Considering that this is on the STABLE branch, is it appropriate to be reporting DEBUG information?

I'm agreement with the other customers in this thread that 920 lines of "spurious information" is drowning out the other update reports.

This excess reporting increases the overall length of the cPanel daily update report so that it now exceeds what GMail will show in the message window, resulting in me having to view the entire message in another tab, so that I can read down to the end and to see that everything is (hopefully) OK.

Could you guys either switch it back to exception reporting (i.e. turn off debug level reporting) or provide a WHM option to set the reporting level?

Thanks

[cPanelTristan]

Hello MindStar,

Would you like me to move your post to our feature request area?

Thanks!

[MindStar]

Hi Tristan,

if it will result in the swift removal of SpamAssassin debug information from daily update reports then carry on.

Regards,

Mark.

[MindStar]

Hi,

any progress on this?

A brief explanation of why debug information is being dumped into the stable/production series cPanel daily update logs would be suffice.

Thanks,

Mark (paying customer)

[cPanelDavidG]

Hi,

any progress on this?

A brief explanation of why debug information is being dumped into the stable/production series cPanel daily update logs would be suffice.

Thanks,

Mark (paying customer)

Looking at this thread, only one person has requested this functionality. We will need to see more widespread support for this functionality before it is considered for implementation.

[Kent Brockman]

Hi there people. I'd rather prefer a Tweak Settings option to enable or disable SpamAssassin logs. Then, as a secondary option,be able to select the log level.

[MindStar]

Looking at this thread, only one person has requested this functionality. We will need to see more widespread support for this functionality before it is considered for implementation.

Not entirely true. There is another thread in the cPanel and WHM discussion form (started by another cPanel customer) which requested this change (and from where this change request was spawned). Several other customers said that they would also like this feature added to cPanel, and this was acknowledged / discussed by several cPanel Staff.

http://forums.cpanel.net/f5/spamassa...ot-164370.html

If you have a threshold for the number of customers who must request a change for it to be actively considered for development, then please advise. Although this does seem somewhat overkill for a simple function to remove debug information which (IMNSHO) should not be present in a stable/release of software.

* This debug reporting is randomly enabled and disabled by updates to the stable/release build of cPanel (it seems to spend most of the time turned ON), suggesting that someone in the development team is actively toggling this level of reporting - although it could be one of the spamassasin devs which could be a whole new can of worms...

HTH, HAND.

Mark.