EMP Body filter does not accept Whitelisting

[jrehmer]

I am seeing a high volume of things like FAQs and the like being filtered when trying to run an old unfiltered spool through pyClean with the EMP Body filter. I assumed a solution would be to use good_posthost, for example, in order to whitelist what I want. The log reports it being Whitelisted, but the EMP Body filter still rejects the articles. Do any of the "good_" whitelists have impact on the EMP Body filter?

2022-06-18 14:37:55 INFO Whitelisted posting. host=penguin-lust.mit.edu, msgid=model-rockets/internet_1268543810@rtfm.mit.edu
2022-06-18 14:37:55 INFO reject: mid=model-rockets/internet_1268543810@rtfm.mit.edu, reason=EMP Body Reject

[Julien-Elie]

When re-injecting an old spool, and wanting to filter it at the same time, I am unsure Cleanfeed or PyClean work fine because of the period of time they retain seen articles. If tons of similar articles arrive within 5 seconds, they would get rejected...
The body_timed_trim parameter could be reduced to 1 second but even with that configuration, maybe some articles would still get rejected.

As for the good_posthost file, some filters are still triggered for all hosts: bad_groups_dizum file takes precedence, misplaced binary check, misplaced HTML check, symbol ratio test check, and... the EMP check!
Maybe all of these checks should then be by-passed? (easy fix - I can provide a patch)

[jrehmer]

@Julien-Elie that would be fantastic! In my case, I do want good_posthost to 'override' any additional checks. It is primarily due to the large number of FAQ messages that were (maybe still are) generated from a few mit.edu hosts.

There are probably some other legitimate cases being caught by the EMP filter, and is beyond the scope of my original "problem", but it would be nice to have other 'whitelist' options available too (From, Subject, etc.).