Replies: 4 comments 1 reply
-
The sieve script was used before version 0.11 had built-in greylist support. Try removing the greylist sieve script, enable the built in greylist module and reload the configuration. |
Beta Was this translation helpful? Give feedback.
-
What exactly refers the |
Beta Was this translation helpful? Give feedback.
-
@mdecimus Thanks for the answer If I need to enable a module, I don't know how to do that (I have the docker version) |
Beta Was this translation helpful? Give feedback.
-
Thanks @mdecimus it works fine Is there a way to correct that? |
Beta Was this translation helpful? Give feedback.
-
Hello there,
I tryed to setup greylist by enabling it, in webadmin, with 5mn in the field Spam Filter Settings > Greylisting > Duration
But I have this warning:
WARN Sieve script not found (sieve.script-not-found) listenerId = "smtp", localPort = 25, remoteIp = xxx.xxx.xxx.xxx, remotePort = 60626, id = "greylist"
(of course remoteIp is not xxx.xxx.xxx.xxx)
Following this documentation: https://stalw.art/docs/spamfilter/greylist/
So I tryed to add the script greylist like discribed here:
https://stalw.art/docs/sieve/examples/
But the warning is still there
And of course, no mail pass to users
Any idea how to setup Greylist?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions