Hi Andres
> Thanks for the explanation. What happens if you run chromium with
> --tls1 ? That sets the min SSL version to TLSv1.0, although I'm not
> sure what changed within chromium to actually drop TLSv1 support; if
> it's a third party library, then the code to support it might just be
> gone.
, but that
equipment is in a corporate lan, not reachable from the internet
protected by additional ACL. IMHO chromium should somehow provide an
option to specify 'yes I know the risk, create an exception' to still
access such sites.
--
Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice u
Dear Maintainer
I think I got it. Maybe updating the manpage would be very helpfull for
other people who stumble over the same problem.
DMARC needs to do an SPF check.
Well I have milter-greylist already performing SPF check, so I
configured what I tought would make opendmarc ignore the SPF chec
Additional Infos:
History file entry of such an failing email:
job 055AOEWZ026900
reporter magma.woody.ch
received 1591352655
ipaddr 2a00:1450:4864:20::52c
from gmail.com
mfrom gmail.com
spf -1
pdomain gmail.com
policy 18
rua mailto:mailauth-repo...@google.com
pct 100
adkim 114
aspf 114
p 110
sp
4 matches
Mail list logo
