~~ Sending this again, as the previous message got horribly mangled!
Apologies for the noise! ~~
Hello all!
I am trying to implement §12 of spec-03 in PhoenixDKIM (an OpenDKIM fork
— milter plus library), and my question is where DSN generation is
supposed to live.
A milter cannot do it, I think: Once we've answered `250`, the session
is gone and there is no milter in the async bounce path. And the MTA's
own bounce generator knows nothing about DKIM2— it won't undo recipe
changes or sign the DSN as a fresh message with `mf=<>`.
It was suggested earlier on this ML (Bron?) that you can do this on
Postfix today without core changes, presumably a pipe/ transport that
shells out to a DKIM2 library and re-injects. This seems to be what the
reference implementation on github is doing?
That would work, but is the expectation indeed that every operator wires
their own pipe, per MTA? That feels fragile and inefficient, if everyone
is supposed to go that way with DKIM2. Is the intent that this
eventually lands in the MTAs (Postfix/ Exim/ Sendmail), with the pipe
just a stopgap?
Thank you for your time, sharing of knowledge, and energy!
Kind regards,
Edmund Lodewijks
--
Edmund Lodewijks <[email protected]>
TZ: UTC+2 / GMT+2
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
