Replies: 2 comments 1 reply
-
Here's my first proposal: |
Beta Was this translation helpful? Give feedback.
-
The main reason for the change was that I got the feeling I used the old
In the unlikely case someone publishes a wrong DNS key then yes, this could potentially be fixed by changing the DNS error. What I consider temporary errors here are problems getting the DNS entries from the DNS server. Not a potentially wrongly configured DKIM setup. |
Beta Was this translation helpful? Give feedback.
-
Hi @lieser ,
I guess, I need your assistance again.
In the 5.x branch, you removed the DKIM_InternalError and added DKIM_TempError and DKIM_Error
I‘d like to backport this to the 2.x branch - to have the error types consistent.
While DKIM_Error should be an „general DKIM error“, as I understand, you replaced DKIM_InternalError with plain Error and are using Error also in various places.
In which cases should I use Error and when DKIM_Error?
DKIM_TempError should mean „temporary DKIM signature error“; therefore I probably need to use it for any DNS problem, even if it’s not a signature problem. But fixing DNS might help fixing verification. Am I right?
(Especially in some places you’re checking for instanceof DKIM_InternalError to decide, if it’s a TEMPFAIL.)
DKIM_InternalError, DKIM_TempError and DKIM_Error all take different parameters. While it’s easy to build a string for DKIM_Error beforehand and switching the params (and put the error message in an array) for DKIM_TempError - should I do it?
I‘d implement the new errors more like DKIM_InternalError and not like the new ones.
Could you guide me a little?
Kind regards
Beta Was this translation helpful? Give feedback.
All reactions