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

Posted to dev@community.apache.org by "Kevin A. McGrail (JIRA)" <ji...@apache.org> on 2018/02/04 10:34:00 UTC

[jira] [Created] (COMDEV-259) SpamAssassin Size Check Improvements

Kevin A. McGrail created COMDEV-259:
---------------------------------------

             Summary: SpamAssassin Size Check Improvements
                 Key: COMDEV-259
                 URL: https://issues.apache.org/jira/browse/COMDEV-259
             Project: Community Development
          Issue Type: Project
          Components: GSoC/Mentoring ideas
            Reporter: Kevin A. McGrail


SpamAssassin is a computationally expensive process to run.  It is more costly as emails get larger.

So SA has safety valves to prevent excessive usage and DoS by limiting the maximum size of emails processed.

Spammers sometimes try and get around this with short messages and large attachments to bypass scanning.

There are techniques that exist to truncate emails that are sometimes less effective so this task would be to identify better techniques in order such as:

For example:
 * remove attachments for scanning
 * Check size and scan if small enough
 * Truncate the message after closing any open tags
 * scan



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org