Package: spamc Version: 3.4.2-1+deb10u2 Severity: normal spamc -u russ...@coker.com.au --max-size=10485760 127.0.0.1 < spam.mbox
The above command will correctly scan a file that's more than 500K in size. spamc -u russ...@coker.com.au 127.0.0.1 --max-size=10485760 < spam.mbox The above command (differing only in the order of 2 parameters) doesn't work, spamc logs "skipped message, greater than max message size (512000 bytes)" to syslog. The man page for spamc doesn't document this, it may be a bug in spamc. Also the latter mode of operation is what you get when spamass-milter calls spamc, so one of the more common programs that calls spamc doesn't do what's expected. If the way spamass-milter is calling spamc is in error then spamc should log the error so it can be noticed by the sysadmin and fixed. If what spamass-milter is doing is ok then spamc should work with it. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952429 Here is the spamass-milter bug I filed about this, I believe that in this situation both spamass-milter and spamc are failing to operate in the desired manner. -- 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
