Yahoo AMP for Email: sender requirements
Prepare, authenticate and register production AMP email for Yahoo while keeping a normal HTML or text fallback.
Build and test the AMP message
Yahoo supports AMP for Email so recipients can interact with dynamic content inside the message. The AMP MIME part does not replace the normal message. Yahoo requires a similar HTML or text MIME part because the dynamic version is not always shown.
Validate the AMP markup and test the production-ready message before starting Yahoo registration.
Register the sending identity
Yahoo requires senders to register before AMP content is enabled, unless the ESP is already registered and meets Yahoo’s requirements. Yahoo asks for a real production-ready message sent from the production server to its verification address, with valid SPF, DKIM and DMARC, plus the AMP MIME part.
Register the DKIM domains that will sign the AMP mail. Do not forward the verification message, because forwarding changes the message path and can invalidate the evidence Yahoo is asking to inspect.
Meet the authentication conditions
Yahoo requires the AMP message to be DKIM signed, with at least one DKIM domain matching an approved DKIM domain. The message must pass DMARC or pass DKIM with strict domain alignment.
Yahoo currently recommends a DMARC disposition of quarantine or reject for AMP senders and notes that stricter enforcement may be introduced later.
Know the supported Yahoo surfaces
Yahoo states that AMP for Email is supported in Yahoo Webmail and the Yahoo Mail applications on iOS and Android.
Keep the fallback experience complete. A recipient can disable dynamic email, and other clients may ignore the AMP part entirely.