[
https://issues.apache.org/jira/browse/JDKIM-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980057#action_12980057
]
Stefano Bagnara commented on JDKIM-7:
-------------------------------------
Please note that DKIM is an enabling feature: failing to verify a signature
should be treated as a missing signature not something negative. So I see no
point in being "resilient" to errors. If myspace wants to take advantage from
signature verification they will take the time to fix their record. Otherwise
they will simply waste time by signing stuff that won't be verified ;-)
Try to send a message from myspace mail to gmail and you will see that gmail
don't like their record too.
Who needs to care of this common issue is the record publisher. If libraries
author start ignoring the rfc in order to help people that didn't read the RFC
then we would create complete caos.
What if a future RFC will say that "rsa\" is a very special algorythm that
needs to be interpreted in a very specific way?
We implement a library and we should implement the RFC without guess or
deviation. RFC are there because of this. If the DKIM group thinks a "relaxed"
parsing is needed then the place to work is the DKIM group and an update to the
RFC to explain how the parsing can be relaxed.
As you can see from the page you linked the myspace issue is probably listed as
"Inappropriate key algorithm" (I think k is parsed as "rsa\" so invalid
algorythm): 0.5% domains. It is not so common, and it takes one second for
myspace to fix it if they care of being verified.
15 months ago I wrote about this (it is italian, but you can see the myspace
key in red:
http://emailmarketingblog.it/blog/2009/10/01/dkim-troppo-complicato-adottarlo)
and I sent a message to myspace too (ignored).
> Check escaping behaviour of dns retrieved TXT records (changed from dnsjava
> 2.0.6 to 2.0.7)
> -------------------------------------------------------------------------------------------
>
> Key: JDKIM-7
> URL: https://issues.apache.org/jira/browse/JDKIM-7
> Project: JAMES jDKIM
> Issue Type: Bug
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
>
> Changelog for dnsjava 2.0.7 includes something about escaping of chars in TXT
> records.
> As we had a workaround in the code maybe it should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
