You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Examining the code with help from the backtrace from the DEBUG information I think the bug could be in the pattWSP regexp [ \t] in dkimVerifier.jsm:101 which is misrepresenting the whitespace in the z= tag becasue the space in the z= tag is converted to =20 which is the Unicode cahracter value of the space \u0020.
But I might be wrong ;)
The text was updated successfully, but these errors were encountered:
The problem is the space in the encoded space =20 which is not allowed
( ... |Subject:=20Het=2 0weer=20te=20 ...).
If I remove it the add-on no longer gives this error.
So this seems not to be an error in the add-on, but a problem at the signer or in the transport
I had a second lock at the RFC, and came to the conclusion that I was probably wrong. As long as it was not just a space, but a folding whitespace (multiple lines separated by CRLF followed by at least one whitespace) it is probably allowed.
The behavior of the add-on will be changed in version 1.6.2.
Emails sent to myself get an error: Invalid (Copied header fields tag ill-formed)
Investigating I foud this DEBUG in console:
So it's the
z=
tag. Removing my personal information thez=
tag from this email looks likeExamining the code with help from the backtrace from the DEBUG information I think the bug could be in the pattWSP regexp
[ \t]
in dkimVerifier.jsm:101 which is misrepresenting the whitespace in thez=
tag becasue the space in thez=
tag is converted to=20
which is the Unicode cahracter value of the space\u0020
.But I might be wrong ;)
The text was updated successfully, but these errors were encountered: