Skip to content
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

update referenced link in paragraph 1, using dkim #746

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

svalsdottir
Copy link
Contributor

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

  • Give your pull request a meaningful name.
  • Use lowercase filenames.
  • Apply at least one team label according to which team is the content expert (ie. team-FE or team-SAZ)
    (How do I do this?...)
  • Pull request approval from the FE team or content experts (see label applied above) that isn't the content creator.

Content Changes Checklist

  • Check that your article looks correct in the preview here or in a Netlify deploy preview.
  • Check the links in your article.
  • Check the images in your article (if there are any)
  • Check to make sure you are using markdown appropriately as outlined in examples/article.md in the root of the project directory and on the momentum doc's preface article
  • Check to make sure the Copy and Tone Guidelines are followed.

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).
@netlify
Copy link

netlify bot commented Aug 2, 2023

👷 Deploy request for support-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 9869525

@seewerah seewerah added the team - SD SMTP Delivery team is the subject matter expert and need to approve this PR label Aug 2, 2023
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..."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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".

Copy link
Contributor Author

@svalsdottir svalsdottir Aug 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like your new version, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team - SD SMTP Delivery team is the subject matter expert and need to approve this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants