In article <20201106180019.12e27320...@apps1.cs.toronto.edu> you write:
> One thing to be aware of when writing DKIM related rules is that
>it's quite possible (and in some environments routine) for legitimate
>incoming email to have multiple DKIM signatures, some of which fail to
>validate and
On 06/11/2020 18:00, Chris Siebenmann via Exim-users wrote:
One thing to be aware of when writing DKIM related rules is that
it's quite possible (and in some environments routine) for legitimate
incoming email to have multiple DKIM signatures, some of which fail to
validate and some of which
> Thanks Jeremy, fair enough comment.
>
> For now, I'd like to accept anything - just have the Data about
> whether an incoming email was compliant or not - with the option of
> then moving to become more strict. I guess I'd like to be more like
> gmail - which actually seems to be quite lenient.
On 06/11/2020 14:02, Mark Elkins via Exim-users wrote:
For now, I'd like to accept anything - just have the Data about whether
an incoming email was compliant or not - with the option of then moving
to become more strict.
So, just replace your deny & defer with accept, and add into each
(and
Thanks Jeremy, fair enough comment.
For now, I'd like to accept anything - just have the Data about whether
an incoming email was compliant or not - with the option of then moving
to become more strict. I guess I'd like to be more like gmail - which
actually seems to be quite lenient.
I'll
On 06/11/2020 11:53, Mark Elkins via Exim-users wrote:
I've got the following in exim.conf
acl_check_dkim:
...
This is breaking some of my customers...
First define your required policies. We can't really do that
for you. The obvious response is "do not use DKIM" - but I suspect
that
I've got the following in exim.conf
acl_check_dkim:
deny dkim_status = fail
message = DKIM validation failed: $dkim_verify_status
log_message = DKIM validation failed: $dkim_verify_status \
(address=$sender_address, domain=$dkim_cur_signer), \
