Gene

Right so sorry about that. - tool versions ``` Archlinux kernel : 6.7.4-stable gcc: 13.2.1 gcc-libs: 13.2.1 pcre2: 10.42-2 python: 3.11.8 pytest: 7.4.4 openssl: 3.2.1 ``` - package build environment...

build log - I changed the build to not run all tests since only 1 failed. i.e. pytest -k 'test_access_log' [build-unit.log](https://github.com/nginx/unit/files/14313983/build-unit.log)

For completeness here is the archlinux default /etc/makepkg.conf file. Seems the build ignores LDFLAGS which is why I used ld-opt in configure. [makepkg.conf.txt](https://github.com/nginx/unit/files/14314054/makepkg.conf.txt)

FYI - tag 1.32.0 has few additional fails now - build log attached. ``` =========================== short test summary info ============================ FAILED test/test_tls.py::test_tls_certificate_chain - ssl.SSLCertVerification... FAILED test/test_tls.py::test_tls_certificate_chain_long - ssl.SSLCertVerific... FAILED test/test_tls_sni.py::test_tls_sni...

Confirm the tls-related ones are fixed. Now only the test_access_log_keepalive remains. thanks!

Thank you for working on this - I gave up on Thunderbird earlier this year and moved to Evolution - so unfortunately I am no longer in position to test...

this is a zombie project - i gave up on opendkim a couple years ago. I've switched to dkimpy which not only works well and is properly maintained but also...

Yes - i use postfix and once config set up changing milters is straightforward.

I'm still seeing this problem with Google Failing ARC while [email protected] says all is fine. Code Used: Develop branch 20190808 commit 56b22d8 Problem persists with or without SigningHeaders in config...

Google Header has: Authentication-Results: mx.google.com; ... arc=fail (test pass); .. dkim, dmarc and spf all pass ok according to google. Just ARC has the fail.