On Sat, Jul 13, 2024 at 09:46:25PM +0200, Wolfgang via Exim-users wrote:
> and all others helping me, to find the problem with my exim not able to
> deliver to the
> https://blog.lindenberg.one/EmailSecurityTest .
It sure looks to my expert eyelike you've still failed to identify the
reason for
--
In Antwort auf die folgende Mail
From: Andrew C Aitchison via Exim-users
To: Wolfgang
Cc: exim-users@lists.exim.org
Subject: [exim] Re: GnuTLS and Dane-Problem finally solved
Date:Sat, 13 Jul 2024 21:08:44 +0100 (BST)
>>
>> Ok, I compared the the certs again and they just look
On Sat, 13 Jul 2024, Wolfgang via Exim-users wrote:
Hello Viktor, Hello Jeremy,
and all others helping me, to find the problem with my exim not able to deliver
to the
https://blog.lindenberg.one/EmailSecurityTest .
I tried now a lot of things, and learned a lot about debugging this kind of
Hello Viktor, Hello Jeremy,
and all others helping me, to find the problem with my exim not able to deliver
to the
https://blog.lindenberg.one/EmailSecurityTest .
I tried now a lot of things, and learned a lot about debugging this kind of
error.
As the biggest problem lies into the test-mecha
On Sat, Jul 13, 2024 at 01:02:41PM GMT, Grand Master via Exim-users wrote:
> goal is blocking spoofing or avoiding wildcard permissions in
> whitelist such as *@company.com
You probably want verify = sender in one of your ACLs, and a SPF check.
Exim has a native SPF condition for ACLs, but due to
thanks for replying, Jeremy
goal is blocking spoofing or avoiding wildcard permissions in whitelist
such as *@company.com
in my option i'd like to check simultaneously on two walues:
$sender_address and $acl_c_reverse_address
сб, 13 июл. 2024 г., 02:41 Jeremy Harris via Exim-users <
exim-users@li
