Updated test case Zone09#870
Conversation
|
Should Z09_ARPA_MAIL_DOMAIN_NOT_REQUIRED and Z09_TLD_MAIL_DOMAIN_NOT_REQUIRED be INFO or WARNING ? Maybe tests should be added to report Z09_NULL_MX_FOUND_WITH_NON_ZERO_PREFERENCE, Z09_NULL_MX_FOUND_WITH_OTHER_MX. |
INFO. They are outputted if an ARPA domain or TLD, respectively, has no MX or an Null MX, which should be considered to be normal.
Good proposal. I will add that. |
|
Should a warning be emitted if an arpa domain or TLD has an MX (except NULL_MX) ? In my opinion, Z09_NULL_MX_WITH_NON_ZERO_PREFERENCE and Z09_NULL_MX_WITH_OTHER_MX should be WARNING |
I think a WARNING or even NOTICE would definitely be too strong. I cannot see that an MX there would create a problem. See Severity Level Definitions. I noticed that .ax has an MX. According to RFC 5321 a TLD can be used as mail domain, and then it should be OK to have MX.
I cannot see that non-zero preference could create such a problem. A second MX could possibly fool a non-compliant SMTP client (i.e. a client that does not understand "Null MX") into sending the mail to the secondary MX. I will raise the second to WARNING. |
|
I found, or was sent, a reference on using dotless domains as mail domains, "Dotless Domains Considered Harmful". I will update the specification with a message on level WARNING if a TLD has an non-Null MX. |
1d5024f to
d4532a1
Compare
|
@vlevigneron, any comment on this PR before I merge? |
mattias-p
left a comment
There was a problem hiding this comment.
This rewrite is quite an expansion! All in all it looks very good. I have a few suggestions.
0f64ef2 to
2eab47d
Compare
* Adapts to draft template (zonemaster#971) * Messages are updated. * Informational messages removed to keep down the amount of messages.
* Adds reference to "Query and responds defaults". * Updates the message tags to make them shorter. * Updates the message tag table to make it follow proposed updates to the specification template. * Adds message ID * Adds arguments to message ID * Editorial updates.
|
@PNAX, please re-review. |
ghost
left a comment
There was a problem hiding this comment.
Just one last comment, otherwise this is good to me
| 1. *Child Zone* is the root zone ("."), or | ||
| 1. *Child Zone* is a [TLD], or | ||
| 2. *Child Zone* is a zone in the .ARPA tree. | ||
|
|
There was a problem hiding this comment.
I realize we are not outputting the list of found MX records at the end of this test anymore. This would be nice to list all found MX as NOTICE as before. This can be of value to know how the domain is configured to handle mails.
Re-written test case Zone09
This PR will resolve issue #841 and include some validation of "Null MX" (issue #754).
Further updates:
When this update has been merged, the implementation must also be updated.
Updates 2022-07-15
The PR was rebased on latest develop branch. All commits before 12085c1 are the same changes that were done 2022-01-17 and earlier.
Added updates:
updates to the specification template.