Also, the EXIM reference of opendmarc_policy_store_dkim its in
https://github.com/Exim/exim/blob/e3e281ccf9d8777d0df98ddd644720573e0343d1/src/src/dmarc.c
“
libdm_status = opendmarc_policy_store_dkim(dmarc_pctx, US sig->domain, dkim_result, US"");
"
While following new OpenDMARC method
"
opendmarc_policy_store_dkim(dmarc_pctx, US sig->domain, “OpenDMARC expects u_char *selector here” , dkim_result, US"”);
“
I think its DKIM selector, can be found in DNS records, and I presume it must be already retrieved yet couldn’t find in which variable its stored and would it be accessible.
Someone fully understanding EXIM, should be able to determine.
I think this is my stride end, hopefully its help at least to Jeremy, anyone can take on from here?
With thanks :)
> On 9 Jan 2022, at 11:44, Jeremy Harris via Exim-users <exim-users@???> wrote:
>
> On 08/01/2022 18:30, Edwin Balani via Exim-users wrote:
>> Can't you rely on OPENDMARC_LIB_VERSION? It's defined in dmarc.h:
>
> Quite possibly. Now, is the changed API documented? Or are we
> supposed to inspect the libdmarc code and watch for API-breaking
> changes, evermore? And *guess* from the variable names used
> what the new semantics might be? Or read deeply enough into the
> libdmarc implementation to verify the changed behaviour?
>
> Who will put this effort in?
>
> What about exim regression testsuite support for dmarc, something
> we currently don't have? And the maintenance of that, and the the
> ongoing monitoring of testsuite runs and fixing of things found?
>
> Volunteers? I'm expecting a deathly hush, as usual.
>
> --
> Cheers,
> Jeremy
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
