byterazor/qpsmtpd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

New size_limit param for spamassassin plugin

Browse Source 
Allow setting the size limit to handle by the plugin, instead of the hardcoded 500_000 value
This commit is contained in:
Daniel Berteaud 2016-04-19 18:37:42 +02:00
parent 43020a8041
commit 4a6ce830b3
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
plugins/spamassassin
View File

@ -96,6 +96,11 @@ scores because their dynamic IP space is properly listed on DUL blocking lists.
If the user is authenticated or coming from a trusted IP, odds are we don't If the user is authenticated or coming from a trusted IP, odds are we don't
want to be reject their messages. Especially when running qpsmtpd on port 587. want to be reject their messages. Especially when running qpsmtpd on port 587.
=item size_limit [limit]
Set the maximum email size in bytes to scan. Above this limit, no scan will be
done by spamd. The default value is 500_000
=back =back
With both of the first options the configuration line will look like the following With both of the first options the configuration line will look like the following
@ -172,7 +177,8 @@ sub data_post_handler {
return DECLINED if $self->is_immune(); return DECLINED if $self->is_immune();
if ($transaction->data_size > 500_000) { my $limit = $self->{_args}->{size_limit} || 500_000;
if ($transaction->data_size > $limit) {
$self->log(LOGINFO, $self->log(LOGINFO,
"skip, too large (" . $transaction->data_size . ")"); "skip, too large (" . $transaction->data_size . ")");
return DECLINED; return DECLINED;