update referenced link in paragraph 1, using dkim #746
Conversation
I've updated the link in the first paragraph as suggested by Twinkle in Support. I also made some minor wording edits, and removed where the diagram was described as being "to the right" (it's in the middle in my screen, and probably varies based on the screen and browser you view the article in).
👷 Deploy request for support-docs pending review.Visit the deploys page to approve it
|
seewerah
added
the
team - SD
seewerah
requested review from
cjarnold,
seewerah,
rafaelmatsumotomb,
PauloJeunonSousa and
a team
| title: "Using DomainKeys Identified Mail (DKIM) Signatures" | ||
| description: "Domain Keys Identified Mail DKIM is a mechanism that allows verification of the source and contents of email messages Using DKIM sending domains can include a cryptographic signature in outgoing email messages A message's signature may be verified by any or all MT As during transit and by the Mail..." | ||
| description: "Domain Keys Identified Mail DKIM lets a receiving email server verify of the source and content of an email message. This is an anti-spoofing (and anti-phishing) measure. Using DKIM sending domains can include a cryptographic signature in outgoing email messages A message's signature may be verified by any or all MT As during transit and by the Mail..." |
There was a problem hiding this comment.
lets a receiving email server verify of the source and content of an email message.
Maybe it's necessary to remove the of? verify the source and content
|
|
||
| To determine subsequent handling of incoming email messages, service providers may use the success/failure of DKIM signature verification or the lack of a DKIM signature. The provider can drop invalid messages without impacting the final recipient, exposing the results of DKIM verification directly to the recipient, or exposing the lack of a signature directly to the recipient. Additionally, service providers may use signature verification as the basis for persistent reputation profiles to support anti-spam policy systems or to share with other service providers. | ||
| To determine how to handle incoming email messages, service providers may use the success/failure of DKIM signature verification or the lack of a DKIM signature. The provider can drop invalid messages without impacting the final recipient, exposing the results of DKIM verification directly to the recipient, or exposing the lack of a signature directly to the recipient. Service providers could also use signature verification as the basis for persistent reputation profiles to support anti-spam policy systems, or to share with other service providers. |
There was a problem hiding this comment.
To determine how to handle incoming email messages...
I think here the original text had the meaning of "to determine if the incoming email message was manipulated while in transit", and not "to find a way to do it".
There was a problem hiding this comment.
"subsequent handling of" means "how to handle the message next"... like "do I mark this as spam or deliver it to the inbox". That's how I understood it.
In any case, the fact that we're talking about it means this content needs to be made more clear! How about:
Email service providers can use the DKIM signature to decide what to do with an incoming email. For example, if the DKIM signature fails because it doesn't match the sending domain's DNS records, the email could be dropped, quarantined, or delivered with a warning message. Service providers can also use the signature verification in anti-spam systems.
^ I don't think we need to include all the nitty gritty details.
There was a problem hiding this comment.
I like your new version, thank you.
I've updated the link in the first paragraph as suggested by Twinkle in Support. I also made some minor wording edits, and removed where the diagram was described as being "to the right" (it's in the middle in my screen, and probably varies based on the screen and browser you view the article in).
All PRs Checklist
team-FEorteam-SAZ)(How do I do this?...)
Content Changes Checklist
examples/article.mdin the root of the project directory and on the momentum doc's preface article