@@ -78,9 +78,9 @@ follow the Requirements for sending 5,000 or more messages per day.
78
78
spam rates
79
79
• Format messages according to the Internet Message Format standard, RFC 5322
80
80
.
81
- • Don’t impersonate Gmail From: headers. Gmail will begin using a
82
- DMARC quarantine enforcement policy, and impersonating Gmail From: headers
83
- might impact your email delivery.
81
+ • Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC
82
+ quarantine enforcement policy, and impersonating Gmail From: headers might
83
+ impact your email delivery.
84
84
• If you manage a forwarding service, including mailing lists or inbound
85
85
gateways, add ARC headers to outgoing email. ARC headers indicate the
86
86
message was forwarded and identify you as the forwarder. Mailing list
@@ -136,7 +136,7 @@ Authenticated messages:
136
136
137
137
• Help protect recipients from malicious messages, such as spoofing and
138
138
phishing messages.
139
- • Help protect you and your organization from being impersonated.
139
+ • Help protect you and your organization from being impersonated.
140
140
• Are less likely to be rejected or marked as spam by Gmail.
141
141
142
142
Set up email authentication for each of your sending domains at your domain
@@ -148,7 +148,7 @@ to Gmail accounts. To improve email delivery, we recommend that you always set
148
148
up SPF, DKIM, and DMARC for your domains. Make sure you're meeting the minimum
149
149
authentication requirements described on this page. Messages that aren’t
150
150
authenticated with these methods might be marked as spam or rejected with a
151
- 5.7.26 error.
151
+ 5.7.26 error.
152
152
153
153
If you use an email service provider, verify that they authenticate your
154
154
domain’s email with SPF and DKIM.
@@ -201,6 +201,10 @@ ARC checks the previous authentication status of forwarded messages. If a
201
201
forwarded message passes SPF or DKIM authentication, but ARC shows it
202
202
previously failed authentication, Gmail treats the message as unauthenticated.
203
203
204
+ When ARC shows that a forwarded message previously passed authentication, Gmail
205
+ doesn’t automatically authenticate the message. Instead, Gmail does its own
206
+ authentication check on the message.
207
+
204
208
We recommend that senders use ARC authentication, especially if they regularly
205
209
forward email. Learn more about ARC authentication.
206
210
@@ -209,7 +213,7 @@ Infrastructure configuration requirements and guidelines
209
213
IP addresses
210
214
211
215
Important: The sending IP address must match the IP address of the hostname
212
- specified in the Pointer (PTR) record.
216
+ specified in the Pointer (PTR) record.
213
217
214
218
The public IP address of a sending SMTP server must have a corresponding PTR
215
219
record that resolves to a hostname. This is called a reverse DNS lookup. The
@@ -234,7 +238,7 @@ If you use a shared IP address for sending email:
234
238
235
239
• Make sure the shared IP address isn’t on any internet blocklist. Messages
236
240
sent from IP addresses on a blocklist are more likely to be marked as spam.
237
- • If you use an email service provider for your shared IP, use Postmaster
241
+ • If you use an email service provider for your shared IP, use Postmaster
238
242
Tools to check the reputation of the shared IP address.
239
243
240
244
Subscription requirements and guidelines
@@ -261,7 +265,7 @@ Make it easy to unsubscribe
261
265
262
266
Always give recipients an easy way to unsubscribe from your messages. Letting
263
267
people opt out of your messages can improve open rates, click-through rates,
264
- and sending efficiency.
268
+ and sending efficiency.
265
269
266
270
Important: If you send more than 5,000 message per day, your marketing and
267
271
subscribed messages must support one-click unsubscribe.
@@ -325,7 +329,7 @@ delivered as expected:
325
329
□ Sender information should be clear and visible.
326
330
•
327
331
• Format the following international domains according to Section 5.2 of
328
- Unicode Technical Standard #39. An international domain is also called an
332
+ Unicode Technical Standard #39. An international domain is also called an ;
329
333
internationalized domain name (IDN), and is a URL that is specific to a
330
334
region or country.
331
335
□ Authenticating domain
@@ -398,11 +402,10 @@ If you send large amounts of email, we recommend you:
398
402
• Send email at a consistent rate. Avoid sending email in bursts.
399
403
• Start with a low sending volume to engaged users, and slowly increase the
400
404
volume over time.
401
- • As you increase the sending volume, regularly monitor server
402
- responses, spam rate, and the sending domain's reputation. Regular
403
- monitoring will allow you to quickly adapt if your sending is rate limited,
404
- if the spam rate is increased, or when the sending domain's reputation
405
- drops.
405
+ • As you increase the sending volume, regularly monitor server responses,
406
+ spam rate, and the sending domain's reputation. Regular monitoring will
407
+ allow you to quickly adapt if your sending is rate limited, if the spam
408
+ rate is increased, or when the sending domain's reputation drops.
406
409
• Avoid introducing sudden volume spikes if you do not have a history of
407
410
sending large volumes. For example, immediately doubling previously sent
408
411
volumes suddenly could result in rate limiting or reputation drops.
@@ -505,7 +508,7 @@ Spam rate
505
508
• Regularly monitor your domain's spam rate in Postmaster Tools.
506
509
507
510
• Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever
508
- reaching a spam rate of 0.30% or higher. Learn more
511
+ reaching a spam rate of 0.30% or higher. Learn more
509
512
• Maintaining a low spam rate helps senders be more resilient to occasional
510
513
spikes in user feedback.
511
514
• Maintaining a high spam rate leads to increased spam classification. It can
0 commit comments