Skip to content

Commit 0943989

Browse files
committed
(Google) "Guidelines for email display names" added in Email Sender Guidelines: https://support.google.com/mail/answer/81126
1 parent 8f0439d commit 0943989

File tree

1 file changed

+56
-1
lines changed

1 file changed

+56
-1
lines changed

google-81126-email-sender-guidelines.txt

Lines changed: 56 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -327,7 +327,6 @@ delivered as expected:
327327
□ Web links in the message body should be visible and easy to understand.
328328
Recipients should know what to expect when they click a link.
329329
□ Sender information should be clear and visible.
330-
331330
• Format the following international domains according to Section 5.2 of
332331
Unicode Technical Standard #39. An international domain is also called an ;
333332
internationalized domain name (IDN), and is a URL that is specific to a
@@ -338,6 +337,62 @@ delivered as expected:
338337
□ Reply-to domain
339338
□ Sender domain
340339

340+
Guidelines for email display names
341+
342+
Misuse of display names can impact email deliverability when sending to
343+
personal Gmail accounts. When you send commercial or bulk email, it’s important
344+
to follow the Email sender guidelines and to respect recipients’ inboxes.
345+
Follow the display name guidelines here to help ensure your messages are
346+
delivered as expected.
347+
348+
Display name guidelines
349+
350+
Sender display names should be used exclusively to identify the sender.
351+
352+
Display names should reflect a consistent, clear, and accurate statement of the
353+
sender's identity, name and/or organization.
354+
355+
Don’t include subject or message content in display names.
356+
357+
Display names should never be used to attempt to deceive the recipient of the
358+
email.
359+
360+
Avoid misleading or deceptive display names by following these guidelines:
361+
362+
• Identify the sender first and don’t include subject or message content in
363+
this display name. For example, don’t use display names like these:
364+
□ Important Update ---------- From [Company Name]
365+
□ TIME IS RUNNING OUT (SALE)
366+
□ [Product/News] Alert
367+
□ URGENT REQUEST
368+
□ Last Chance
369+
• The display name should not include the recipient’s name and should not
370+
imply a message reply or threaded conversation. For example, don’t use
371+
display names like these:
372+
□ [recipient’s first name] <[email protected]>
373+
□ User (2)
374+
• The display name should clearly identify the sender and shouldn't include
375+
emojis or other non-standard characters to imitate graphic elements. For
376+
example, don’t use display names like these:
377+
□ [v] LATEST UPDATE
378+
□ MAIL, ME [2]
379+
□ [z]
380+
□ [1] New Message
381+
382+
Spoofing and display names
383+
384+
Avoid these types of spoofing, which are deceptive display name practices:
385+
386+
• Using an @gmail.com domain as the display name for bulk email
387+
• Using characters that imply the mail is part of threaded conversation, for
388+
example: User (2)
389+
• Using the name of the recipient in the display name
390+
391+
To manage an effective email campaign, your messages should connect you and
392+
your recipients in a meaningful way. Be sure to follow all Email sender
393+
guidelines to improve your email delivery and effectiveness. Senders who fail
394+
to follow best practices may not be considered for deliverability mitigations.
395+
341396
Sending practices requirements and guidelines
342397

343398
To reduce the chances that messages from your domain are sent to spam or

0 commit comments

Comments
 (0)