Hallo,
wo kann ich das Limit für Nachrichten einstellen.
Ich erhalte immer mehr Spam-Nachrichten wo eine Grafik mit ca 800kb enthalten ist und diese wird demzufolge nicht rausgefiltert. Spamassassin Plugin ist installiert.
-
-
-
-
Error after plugin update:
Code- systemctl status spamassassin.service● spamassassin.service - Perl-based spam filter using text analysis Loaded: loaded (/lib/systemd/system/spamassassin.service; enabled) Active: failed (Result: exit-code) since Mon 2017-06-19 10:07:55 CEST; 51s ago Process: 26537 ExecStart=/usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid $OPTIONS (code=exited, status=64) Main PID: 1023 (code=exited, status=0/SUCCESS)Jun 19 10:07:55 mail spamd[26537]: (filename) of a Unix socket. If port is omitted it defaults to --port orJun 19 10:07:55 mail spamd[26537]: to 783. Option --ssl implies a prefix 'ssl:'. An IPv6 address should beJun 19 10:07:55 mail spamd[26537]: enclosed in square brackets, e.g. [::1]:783, an IPv4 address may be butJun 19 10:07:55 mail spamd[26537]: need not be enclosed in square brackets. An asterisk '*' in place of aJun 19 10:07:55 mail spamd[26537]: hostname implies an unspecified address, ('0.0.0.0' or '::'), i.e. itJun 19 10:07:55 mail spamd[26537]: binds to all interfaces. An empty option value implies '*'. A default isJun 19 10:07:55 mail spamd[26537]: '--listen localhost', which binds to a loopback interface only.Jun 19 10:07:55 mail systemd[1]: spamassassin.service: control process exited, code=exited status=64Jun 19 10:07:55 mail systemd[1]: Failed to start Perl-based spam filter using text analysis.Jun 19 10:07:55 mail systemd[1]: Unit spamassassin.service entered failed state.
syslog:
Code- Jun 19 10:06:31 mail systemd[1]: Stopping Perl-based spam filter using text analysis...
- Jun 19 10:06:31 mail spamd[1023]: spamd: server killed by SIGTERM, shutting down
- Jun 19 10:06:31 mail systemd[1]: Starting Perl-based spam filter using text analysis...
- Jun 19 10:06:32 mail spamd[26070]: Unknown option: max-size
- Jun 19 10:06:32 mail spamd[26070]: Usage:
- Jun 19 10:06:32 mail spamd[26070]: spamd [options]
-
-
-
Ok, I've been bad in my previous post.. Options in /etc/default/spamassassin are for spamd and not spamc. Thus, we need to pass the option through spamass-milter. Give me few minutes to give your the right directives. And please, for now, revert
-
Display MoreCode
- # /etc/default/spamassassin
- # Duncan Findlay
- # WARNING: please read README.spamd before using.
- # There may be security risks.
- # If you're using systemd (default for jessie), the ENABLED setting is
- # not used. Instead, enable spamd by issuing:
- # systemctl enable spamassassin.service
- # Change to "1" to enable spamd on systems using sysvinit:
- ENABLED=1
- # Options
- # See man spamd for possible options. The -d option is automatically added.
- # SpamAssassin uses a preforking model, so be careful! You need to
- # make sure --max-children is not set to anything higher than 5,
- # unless you know what you're doing.
- OPTIONS="--max-size=1000000 --max-children=5 --sql-config --nouser-config --username=debian-spamd --port=783 --helper-home-dir=/var/lib/spamassassin"
- # Pid file
- # Where should spamd write its PID to file? If you use the -u or
- # --username option above, this needs to be writable by that user.
- # Otherwise, the init script will not be able to shut spamd down.
- PIDFILE="/var/run/spamd.pid"
- # Set nice level of spamd
- #NICE="--nicelevel 15"
- # Cronjob
- # Set to anything but 0 to enable the cron job to automatically update
- # spamassassin's rules on a nightly basis
- CRON=1
-
-
-
So, I've done a little test before writing some bullshit again (setting max size to 10 bytes max
). Result:
So how to process finally? As stated above, the parameter must be passed to spamc through spamass-milter service. So in the plugin configuration file you'll find the spamassMilterOptions configuration parameter. You must modify it as folllow:
Once done, don't forget to trigger a plugin list update, else your changes won't be taken into account.You must remember that any option appearing after -- are passed to spamc. Regarding this, there is a bug in the plugin because it also add -- to pass flags to spamc without further checking. You must wait next SpamAssassin plugin version.
-
-
-
A new version is available which fix the problem described above.
In order, you must:
- Upload the new version (1.2.0)
- Edit the plugin configuration file and change:
by
And finally, you must trigger a plugin list update through the plugin management interface.
Thank you for your report.
Thread closed. -