You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2011/05/09 11:21:46 UTC

[Bug 6582] need to have some limits on scanned data size

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6582

Henrik Krohns <he...@hege.li> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|text/* attachments end up   |need to have some limits on
                   |in rendered body            |scanned data size

--- Comment #10 from Henrik Krohns <he...@hege.li> 2011-05-09 09:21:46 UTC ---
So here some observations:

- Less difference with scantime for more varied corpus (anyway the goal was
just to limit the "bad cases")
- Limit of 30000 actually helped with FPs vs 100000
- MPART_ALT_DIFF (and possible others) can be fixed simply by making it call
rendered() without limits
- Nothing really changed dramatically
- My corpus is pretty old, but it shouldn't matter..

I changed to subject to something more generic. Will make a first patchset
proposal now..

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.