No, you have incorrect config, as pointed out by Graeme. I trimmed, credit
to him.
>> i only add this config:
>>
>>spamd_address = x.x.x.x 11333 variant=rspamd
>>
>>denymalware = */defer_ok
>>message = This message contains a virus ($malware_name).
> *You are defining a spam scanner, then
Did you generate the CSR for that certificate yourself? The CSR is
generated from the private key, you don't get it from the authority.
On Mon, Apr 30, 2018 at 2:58 PM, Gary Stainburn via Exim-users
wrote:
> This has to be so simple but I can't get my head round it.
>
> I
The rspamd integration guide lists the variables that are set when
rspamd is called:
# This will set variables as follows:
# $spam_action is the action recommended by rspamd
# $spam_score is the message score (we unlikely need it)
# $spam_score_int is spam score multiplied by 10
#
I confess to not know 100% if this is possible with native config options,
indeed the link you seems to suggest no.
If you have some way though, of telling programmatically that clam is
unresponsive then of course there's a way to skip clam checks and therefore
not defer.
I did this for a
The Exim SPF docs page on Github describes how to handle perm errors
amongst others.
On Friday, December 15, 2017, Jonathan Gilpin via Exim-users <
exim-users@exim.org> wrote:
> Now that explains why this hasn’t come up before, thanks a lot. Their SPF
> record was indeed invalid.
>
> I can’t
Mike has hit the nail on the head.
As an additional tip, I found for those cheap domains (like .win, .top
etc), using a combination of slightly weighted scoring on the domain
name and SpamAssassins relay geoip module, I was able to eliminate
most spam relatively easily. You'll probably notice