Rupert
Rupert
> > I do not want them to sign anything, as it is not up to me to decide their policy.... > > Wrong. Please RESET your thinking about this...
> Indeed, it seems I am misunderstanding what it is you think the problem is. Sorry if I have confused things. Perhaps you could clarify what you think OpenDKIM's correct...
Patching against configure instead of configure.ac, so you see how it expands on OpenBSD. ``` --- ./configure.orig 2020-07-09 12:04:31.000000000 +0200 +++ ./configure 2020-07-09 12:24:21.000000000 +0200 @@ -712,6 +712,7 @@ LIBEVENT_LIBDIRS...
I am back on this and my other issues after a while now, and would like to close them all. I git cloned the development branch, and have new issues...
Using /run instead of /var/run breaks compliance with ... Filesystem Hierarchy Standard (FHS) 2.3 2004 http://www.pathname.com/fhs/
``` --- opendkim/opendkim.c.orig 2020-07-09 14:15:55.000000000 +0200 +++ opendkim/opendkim.c 2020-07-09 14:32:00.000000000 +0200 @@ -791,11 +791,12 @@ ** BEGIN private section */ -#ifndef HAVE_SMFI_INSHEADER /* ** SMFI_INSHEADER -- stub for smfi_insheader() which...
+1 On my instance, the recent calls list has huge bold fonts for each item and tiny almost unreadable fonts for item details. There is neither a GUI option nor...
> @hdatma -- the latest version of FHS is at https://refspecs.linuxfoundation.org/fhs.shtml which [includes /run](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s15.html). Still leave it as an option, as systems like OpenBSD do not have /run.
Yes, there is a problem with long SPF policies that I have noted also on other domains. Today I spotted a domain whose DMARC's SPF fails while succeeding by hand...