FUTATSUKI Yasuhito

Perhaps the commit https://github.com/trusteddomainproject/OpenARC/commit/f6b57dcc85f621c032a60818c2b6dc1f1cfcde6a intended to reject messages with maricious AR header(s), and I agree that it is not good. However, I think the condition `if (arfound > 1)` does...

I'm not okay the PR as it is. Only the basic concept, that we should not regardlessly reject message which have multiple AR headers of ARC result in own Authserve-ID,...

> This is the responsibility of the ADMD border MTA to deal with; as per [RFC 8601](https://datatracker.ietf.org/doc/html/rfc8601#section-5) "any MTA conforming to this specification MUST delete any discovered instance of this...

> ... The only cases where my change disallows an override are explicit cv=fail in an existing seal (doing this creates an invalid seal) or too many ARC sets existing...

While I've making private FreeBSD ports for whoisit, I've just encountered issue and avoid it by (obvious) patch below (Please ignore the timestamp): ``` --- ./setup.py.orig 2025-05-30 16:58:02.421203000 +0900 +++...

Also `rbl_res_nslist()` has same type miss match in `#ifdef HAVE_RES_SETSERVERS` context.

> Also in int dkim_res_nslist(void *srv, const char *nslist) { in libopendkim/dkim-dns.c Ah, I remember they were proposed to be removed in PR #99

The function `dkimf_db_walk()` don't have the code for `db->db_type == DKIMF_DB_TYPE_MEMCACHE`. Function `dkimf_db_walk()` is used for `SigningTable` in `opendkim.c` (opendkim(8)), for `KeyTable` in `opendkim-genzone.c` (opendkim-genzone(8)) and `opendkim-testkey.c` (opendkim-testkey(8)), for `ReputationLimits`...

With the patch in PR #219, opendkim(8) might avoid assertion failure caused by unhandled DB type in `dkimf_db_walk()`. opendkim(8) would not crash on the verification of SigningTable even if it...

Although I've not tested, it is expected that you can use memcached table as Signing Table by using the patch in PR #228 and with suitable config setting or with...