I am able to use double dkim but getting the error that dkim sign-in is in alphabetical order,
example if my selectors are aaec01 and ac01 and i desc the order ac01 to be first shown aac01 in the first.
So my question is how to set the order
Can you expand a bit more about the error you are seeing? That doesn’t sound like something from inside kumomta. Where is it coming from? Please also share the relevant kumomta configuration that is in use.
We’re going to need more information here, what does your configuration look like? What is the full authentication-results header you’re referring to?
this is my configuration
now when i am checking my email header the set order should reflect but that’s seems not to be happening
Ok, post headers?
ok
ARC-Authentication-Results: i=1; mx.google.com;
dkim=temperror (no key for signature) header.i=@ header.s=5nXKKHgBnyGAcLwvMLZIq header.b=BWs7+J1e;
dkim=temperror (no key for signature) header.i=@acl.pinchappmails.com header.s=aace01 header.b=sg7+W0h0;
dkim=pass header.i=@ header.s=acls01 header.b=fYbdXIqc;
this the email header I have received
Note that, per the DKIM RFC, DKIM at signing time, each signature is added at the top of the message. So if you sign multiple times the order of the headers in the message will be to have the most recent signature at the top, then the one before it, and so on.
You also have mag instead of msg multiple times.
that is correct i have just missed that point to make it correct
sp in this case what needs to be done
The order of the signatures shouldn’t matter, but if you want them to be in a different order, you can change the order of the msg:dkim_sign calls to be the other way around
Why are you sigfning the same domain with three different selectors?
the domains are different
I have just called the key which are being placed
Not according to the sample you have provided, you passed the from_header().domain in each.
ok it should be the domain instead of from.header()
At any rate, based on the paths in your pseudocode, I’m not seeing any of those keys passing the DKIM tester at MX Toolbox, so you may have DNS issues more than signing order issues.
only 1 key will pass the dkim tester acls01