Package: spamc
Version: 3.4.2-1+deb10u2
Severity: normal
Tags: upstream

When we ran mail servers on 32bit systems a default of skipping spam checks on
the rare messages that were more than 500k in size made sense.

Nowadays messages larger than that are normal and scanning a 10MB message is
not a problem for CPU use or memory allocation on most systems.

I believe that the default should just work for most people who don't have
unusual needs.  Running spamassassin on a 32bit system nowadays is an
unusual situation that the users could be expected to tune for.  Running it
on a system with many gigs of RAM is more the usual case.

For the benefit of other people with this issue, a line like the following in
/etc/default/spamass-milter will make it take 10MB messages (the "--" and
following is the relevant part).

OPTIONS="-u spamass-milter -i 127.0.0.1 -r 5 -- -s 10485760"

-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages spamc depends on:
ii  libc6      2.28-10
ii  libssl1.1  1.1.1d-0+deb10u2

spamc recommends no packages.

Versions of packages spamc suggests:
ii  spamassassin  3.4.2-1+deb10u2

-- no debconf information

Reply via email to