[Koha-bugs] [Bug 34927] Adding DMARC compatibility to mailing lists

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34927

--- Comment #11 from Thomas Dukleth <td-koha-bugs at agogme.com> ---
> Sidenote on ARC Support.

If Gmail, etc. would still require ARC support for mailing lists despite
mailing list use of DMARC, I have verified that OpenARC works in my own build
from the development branch at least sufficiently well to satisfy Gmail
currently.  There are no designated release branches and people build from the
OpenARC development branch especially given that the last commit to the
development branch was three years ago and the development branch has some
important bug fixes.

[...]

> current testing of my source build, Postfix has a socket permissions error
> for OpenARC

OpenARC lacks a umask configuration setting, which exists for OpenDKIM, even if
other means should be available for controlling OpenDKIM socket permissions. 
Setting a chmod command to run following the start of the OpenARC daemon
service is a simple workaround to add group write permission to the OpenARC
socket fixing the Postfix permission problem for the OpenARC socket.  On some
other system other than my own mailserver, which I used for testing, the socket
permission problem may not have appeared.

I noticed that someone had filed an OpenARC bug requesting a umask
configuration setting like the feature in OpenDKIM and with unimplemented
supporting code present in the development branch.

There are other helpful OpenDKIM features which are missing from OpenARC or
only partly implemented with much less development work for OpenARC than
OpenDKIM.  Workarounds for the incomplete feature of supporting multiple
domains or subdomains for OpenARC matching OpenDKIM with OpenARC using KeyTable
and SigningTable with OpenARC do not seem as simple as adding a script for the
startup service.  Containerisation or additional VPS servers may be possible
workarounds for multiple domains or subdomains but both workarounds may need
additional IP addresses with good email reputation which are not readily
available from most hosting providers.

-- 
You are receiving this mail because:
You are watching all bug changes.