您必須遵守「避免寄給 Gmail 使用者的郵件遭到封鎖或歸類為垃圾郵件」指南，我們可能會不另行通知而變更這項指南。您有責任確保遵守現行指南。如果我們發現您濫用服務或違反政策，或基於 Google 的判斷，我們可能隨時撤銷您的參與資格。我們可能會在註冊過程中或註冊完成後，要求您提供其他資訊，以便確認您的合規性。
[null,null,["上次更新時間：2025-03-24 (世界標準時間)。"],[],[],null,["# Register with Google to send dynamic emails\n\nWhen you are ready to launch your dynamic emails to your users, you must\nregister with Google for each sender email address that you use. You only\nneed to register the email once even if your email content changes or the same\nsender email address is used for another use case in the future.\n\nTo register a sender email, complete the following steps:\n\n1. Make sure that you meet all the [guidelines and requirements](#registration_guidelines) listed below.\n2. Send a real, production-ready email coming from your production servers\n (or a server with similar SPF/DKIM/DMARC/`From:`/`Return-Path:` headers)\n including the dynamic email MIME part to\n `ampforemail.whitelisting@gmail.com`. We need this in order to check that you\n comply with all the [guidelines and requirements](#registration_guidelines).\n As you send this email, do the following:\n\n 1. Make sure that the AMP version of the email is correct prior to sending the email by [testing it in Gmail](/workspace/gmail/ampemail/testing-dynamic-email)\n 2. Send the email directly instead of forwarding it. Gmail removes AMP MIME parts when forwarding an email.\n\n | **Caution:** Google will reject your registration application if you don't send an email for review, if you send a test (blank) email, or if you send an email that doesn't contain an AMP MIME part. Don't add `ampforemail.whitelisting@gmail.com` to your mailing list because it might cause many static HTML emails to be sent, which don't contain AMP MIME parts. At the time of review, Google only opens the most recently received email from the sender email address to register.\n3. Fill out the [registration form](https://forms.gle/fDqLE1gh4wMB6BeQ6)\n and await our response. We aim to respond to most requests within 5 working\n days.\n\nYour participation as a sender of dynamic email is subject to compliance with\nthe [Prevent mail to Gmail users from being blocked or sent to\nspam](https://support.google.com/mail/answer/81126) guidelines, which are\nsubject to change without notice. You are responsible for ensuring compliance\nwith the current guidelines. Your participation may be revoked at any time if\nabuse or policy violations are discovered, or at Google's discretion. We may\nrequest additional information during the registration process or after\nregistration is complete to verify your compliance.\n\nRegistration guidelines\n-----------------------\n\nYou must meet the following guidelines in order to successfully register with\nGoogle:\n\n- You must send a real, production-quality example email, not a demo or \"Hello World\" example. Don't put placeholder strings like `{name}` and `{count}` or test strings like `[Test]`, `[Proof mail]` and `[Sample]` in your subject or body.\n- Emails must have a similar HTML or text MIME part. There are many instances where this is shown instead, such as when the user has disabled dynamic email.\n- The email must have no bugs.\n- You must authenticate the emails using SPF, DKIM and DMARC as detailed in the [Security\n requirements](/workspace/gmail/ampemail/security-requirements).\n- Ensure that you have reviewed the AMP for Email best practices, and that your email conforms to the suggestions there.\n- Registration works on a per-sender-email-address basis. If you want to\n register more than one sender email address, each address needs to be\n registered separately and needs to send its own production-quality email.\n\n This is true even if the separate email addresses have the same domain, as\n the registration doesn't work on a per-sender-email-domain basis.\n- You mustn't allow third parties, such as users or the general public, to\n directly author and send emails. The emails you send can contain\n user-generated content, such as posts or comments. Testing tools and \"email\n playgrounds\" can't be whitelisted and should instead rely on the steps\n outlined in [Test your AMP emails in\n Gmail](/workspace/gmail/ampemail/testing-dynamic-email).\n\n- Emails must follow the [Prevent mail to Gmail users from\n being blocked or sent to spam](https://support.google.com/mail/answer/81126)\n guidelines.\n\n- A low rate of spam complaints from users.\n\n- The [eTLD+1](https://developer.mozilla.org/en-US/docs/Glossary/eTLD)\n of the sender email address to be registered must serve or redirect to a\n valid website (e.g., not a parked domain) that belongs to the sender. For\n example, if the sender email address is `noreply@mail.example.com`, then\n `https://example.com` must serve the website. The website must be accessible\n worldwide without needing an IP filter."]]
