-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extra space after"d="tag use ccTLD(.co.jp etc)domain #30
Comments
Mail::DKIM Ver 202401 and202406 tested |
I'm sorry. I found a point of misunderstanding and would like to correct it. I mentioned that a space like "d= " would be inserted in the D tag when sent with a ccTLD. However, upon reviewing the original unencoded text, I found that it was not "d= domain name" but "d= newline tab domain name." This means that it is not related to whether it is a ccTLD or not, but that a long domain name causes a newline and a tab to be inserted after "d=." In other words, it was FWS rather than WSP as per RFC. Like WSP, FWS is also prohibited at the start and end of tag values. |
From my reading of rfc6376 this is valid. FWS is allowed around the tag-value, and within the tag-value, but not at the beginning or end of the tag-value.
and later specifically detailing the d= tag
|
Thanks a lot Marc Bradshaw. |
The outgoing headers from the hogehoge-kk.com domain are respectively
DKIM-Signature:
v=1; a=rsa-sha256; c=relaxed/relaxed; d=hogehoge-kk.com;
It is correctly sent, but
The outgoing headers from the hogehoge-kk.co.jp domain are respectively
DKIM-Signature:
v=1; a=rsa-sha256; c=relaxed/relaxed; d= hogehoge-kk.co.jp;
which is one extra space after"d=".
If extra spaces are added to the d tag, some MTAs, such as outlook.com, may receive a DKIM fail decision.
The text was updated successfully, but these errors were encountered: