Skip to content

Commit 1e82538

Browse files
authored
Clarify ESP-delivered email validation (#6885)
Some developers are apparently confused by the instruction here and tested the validation by sending the email from, for example, the Gmail playground. That defeats the purpose of the validation mentioned in this section, because the playground skips any ESP-specific post-processing of the AMP email authored by the developer. The purpose is to catch issues sent by the ESP which may not reproduce when using the playground.
1 parent 1d53be5 commit 1e82538

File tree

1 file changed

+5
-4
lines changed
  • pages/content/amp-dev/documentation/guides-and-tutorials/learn/validation-workflow

1 file changed

+5
-4
lines changed

pages/content/amp-dev/documentation/guides-and-tutorials/learn/validation-workflow/validate_emails.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,15 +54,16 @@ If the email is valid the command-line tool will result in a `PASS`. If invalid,
5454

5555
You can also validate AMP Emails using the [AMP playground](https://playground.amp.dev/?runtime=amp4email). Similar to the web-based validator, paste your AMP Email into the tool, and the playground will flag any validator errors directly inline.
5656

57-
### Validate delivered emails
57+
### Validate emails delivered by ESPs
5858

5959
Sometimes your delivered AMP Emails may be invalid even though the email markup you authored has already been validated by tools documented in this page. The most common reason for this to happen is that your [ESP](https://amp.dev/support/faq/email-support/) modified your email markup and made it invalid after you have sent your email to your ESP for delivery. For example, if your ESP is SparkPost and you haven't configured HTTPS tracking pixels with SparkPost, then SparkPost will add an insecure HTTP tracking pixel to your email. Since AMP Emails only allow HTTPS images, this will make your AMP Email invalid.
6060

61-
To check whether an email delivered to your inbox is valid AMP:
61+
To check whether an email that your ESP delivered to your inbox is valid AMP:
6262

63+
1. Deliver the AMP email via your ESP. Do **not** deliver the email from any email-client-specific playground.
6364
1. [download the AMP Email as an `.eml` file](https://www.codetwo.com/kb/export-email-to-file) from your email client.
64-
2. Open the [AMP playground](https://playground.amp.dev/?runtime=amp4email).
65-
3. Click on "IMPORT EMAIL", and select the `.eml` file you just downloaded.
65+
1. Open the [AMP playground](https://playground.amp.dev/?runtime=amp4email).
66+
1. Click on "IMPORT EMAIL", and select the `.eml` file you just downloaded.
6667

6768
The playground will import the AMP email you downloaded into the inline editor and flag any validation errors.
6869

0 commit comments

Comments
 (0)