[Rspamd-Users] 1.9 question on local.d/actions.conf
Sophie Loewenthal
sophie at klunky.co.uk
Sun Mar 31 20:11:34 UTC 2019
Hi, I added this and got this error:
# cat local.d/actions.conf
reject = 16;
add_header = 6;
# /etc/init.d/rspamd status
● rspamd.service - rapid spam filtering system
Loaded: loaded (/lib/systemd/system/rspamd.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-03-31 20:08:52 UTC; 8s ago
Docs: https://rspamd.com/doc/
Process: 19378 ExecStart=/usr/bin/rspamd -c /etc/rspamd/rspamd.conf -f (code=exited, status=1/FAILURE)
Main PID: 19378 (code=exited, status=1/FAILURE)
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Main process exited, code=exited, status=1/FAILURE
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Unit entered failed state.
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Failed with result 'exit-code'.
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Service hold-off time over, scheduling restart.
Mar 31 20:08:52 prd1 systemd[1]: Stopped rapid spam filtering system.
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Start request repeated too quickly.
Mar 31 20:08:52 prd1 systemd[1]: Failed to start rapid spam filtering system.
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Unit entered failed state.
Mar 31 20:08:52 prd1 systemd[1]: rspamd.service: Failed with result 'exit-code'.
#
2019-03-31 20:08:50 #14128(rspamd_proxy) <0c7391>; main; rspamd_worker_term_handler: terminating after receiving signal Terminated
2019-03-31 20:08:50 #14129(controller) <0c7391>; main; rspamd_worker_term_handler: terminating after receiving signal Terminated
2019-03-31 20:08:50 #14129(controller) rspamd_controller_on_terminate: closing rrd file: /var/lib/rspamd/rspamd.rrd
2019-03-31 20:08:50 #14130(normal) <0c7391>; main; rspamd_worker_term_handler: terminating after receiving signal Terminated
2019-03-31 20:08:50 #14130(normal) rspamd_worker_on_terminate: performing finishing actions
2019-03-31 20:08:50 #14131(hs_helper) <0c7391>; main; rspamd_worker_term_handler: terminating after receiving signal Terminated
2019-03-31 20:08:51 #14103(main) <0c7391>; main; wait_for_workers: rspamd_proxy process 14128 terminated softly
2019-03-31 20:08:51 #14103(main) <0c7391>; main; wait_for_workers: controller process 14129 terminated softly
2019-03-31 20:08:51 #14103(main) <0c7391>; main; wait_for_workers: normal process 14130 terminated softly
2019-03-31 20:08:51 #14103(main) <0c7391>; main; wait_for_workers: hs_helper process 14131 terminated softly
2019-03-31 20:08:51 #14103(main) <0c7391>; main; main: terminating…
Bizarre.
> On 31 Mar 2019, at 13:44, B. Reino <reinob at bbmk.org> wrote:
>
> On Sun, 31 Mar 2019, Sophie Loewenthal wrote:
>
>> Hi,
>>
>> My old actions.conf no longer works with rspamd, and it won’t start.
>> I tried these different configs and all broke rspamd
>>
>> # cat actions.conf
>> actions {
>> reject = 14;
>> add_header = 6;
>> rewrite_subject = 6;
>> subject = "***SPAM*** %s";
>> greylist = null;
>> }
>>
>> # cat ~/actions.conf
>> reject = 14;
>> add_header = 6;
>> rewrite_subject = 6;
>> subject = "***SPAM*** %s";
>> greylist = null;
>>
>> I looked at https://rspamd.com/doc/configuration/metrics.html but didn’t really get it.
>>
>> What is the new format?
>>
>
> My /etc/rspamd/local.d/actions.conf looks like this:
>
> reject = 50;
> add_header = 6;
> greylist = 4;
>
> and rspamd works fine.
>
> I also have a /etc/rspamd/local.d/metrics.conf with:
>
> symbol "SUBJ_EXCESS_BASE64" {
> score = 0.0;
> }
>
> symbol "FROM_EXCESS_BASE64" {
> score = 0.0;
> }
>
> ..
>
> and (AFAICT) works fine.
>
> I'm using rspamd 1.9.0-3~stretch, from the rspamd.com/apt-stable repository.
>
> What error message do you get in the log?
>
> Good luck,
> Bernardo.
> --
> Users mailing list
> Users at lists.rspamd.com
> https://lists.rspamd.com/mailman/listinfo/users
More information about the Users
mailing list