f | Skip to main content | f | Skip to main content |
| | | |
| [](/?tab=uu) | | [](/?tab=uu) |
| | | |
| [Google Workspace Admin Help](/a) | | [Google Workspace Admin Help](/a) |
| | | |
| [](https://www.google.co.jp/intl/en/about/products?tab=uh) | | [](https://www.google.co.jp/intl/en/about/products?tab=uh) |
| | | |
| [Sign | | [Sign |
| in](https://accounts.google.com/ServiceLogin?hl=en&passive=true&c | | in](https://accounts.google.com/ServiceLogin?hl=en&passive=true&c |
| ontinue=http://support.google.com/a/answer/14229414&ec=GAZAdQ) | | ontinue=http://support.google.com/a/answer/14229414&ec=GAZAdQ) |
| | | |
| [](/?tab=uu) | | [](/?tab=uu) |
| | | |
| [Google Help](/) | | [Google Help](/) |
| | | |
| [ | | [ |
| | | |
| * Help Center | | * Help Center |
| ](/a/?hl=en)[ | | ](/a/?hl=en)[ |
| | | |
| * Community | | * Community |
| ](/a/community?hl=en&help_center_link=\[14229414,%22Email%20sende | | ](/a/community?hl=en&help_center_link=\[14229414,%22Email%20sende |
| r%20guidelines%20FAQ%22\])[ | | r%20guidelines%20FAQ%22\])[ |
| | | |
| * Google Workspace Admin | | * Google Workspace Admin |
| ](//admin.google.com/) | | ](//admin.google.com/) |
| | | |
| [ | | [ |
| | | |
| * Privacy Policy | | * Privacy Policy |
| ](//www.google.com/intl/en/privacy.html)[ | | ](//www.google.com/intl/en/privacy.html)[ |
| | | |
| * Terms of Service | | * Terms of Service |
| ](https://www.google.com/accounts/TOS)[ | | ](https://www.google.com/accounts/TOS)[ |
| | | |
| * Submit feedback | | * Submit feedback |
| ](about:invalid#zjslayoutz) | | ](about:invalid#zjslayoutz) |
| | | |
| Send feedback on... | | Send feedback on... |
| | | |
| This help content & information | | This help content & information |
| | | |
| General Help Center experience | | General Help Center experience |
| | | |
| Next | | Next |
| | | |
| * [Help Center](/a/?hl=en) | | * [Help Center](/a/?hl=en) |
| * [Community](/a/community?hl=en&help_center_link=\[14229414,%2 | | * [Community](/a/community?hl=en&help_center_link=\[14229414,%2 |
| 2Email%20sender%20guidelines%20FAQ%22\]) | | 2Email%20sender%20guidelines%20FAQ%22\]) |
| * | | * |
| | | |
| [Google Workspace Admin](//admin.google.com/) | | [Google Workspace Admin](//admin.google.com/) |
| | | |
n | * [Contact support / fix a problem](/a/topic/10029062?hl=en&ref | n | |
| _topic=4388346) | | |
| * [Fix a problem](/a/topic/2412034?hl=en&ref_topic=10029062) | | |
| * [Gmail issues](/a/topic/1258984?hl=en&ref_topic=2412034) | | * [Gmail](/a/topic/9202?hl=en&ref_topic=9197) |
| * [Problems with sending ](/a/topic/1354753?hl=en&ref_topic=125 | | * [Gmail limits and policies](/a/topic/28609?hl=en&ref_topic=92 |
| 8984) | | 02) |
| | | * [Bulk email sending guidelines & tools](/a/topic/7279058?hl=e |
| | | n&ref_topic=28609) |
| * [Email sender guidelines FAQ](/a/answer/14229414) | | * [Email sender guidelines FAQ](/a/answer/14229414) |
| | | |
| # Email sender guidelines FAQ | | # Email sender guidelines FAQ |
| | | |
| This FAQ provides additional, detailed information about our [Ema | | This FAQ provides additional, detailed information about our [Ema |
| il sender | | il sender |
| guidelines](/mail/answer/81126) (previously called _Bulk sender | | guidelines](/mail/answer/81126) (previously called _Bulk sender |
| guidelines)_ | | guidelines)_ |
| , which describe Google's requirements for sending email to perso | | , which describe Google's requirements for sending email to perso |
| nal Gmail | | nal Gmail |
| accounts. Google updates this page periodically, so check back re | | accounts. Google updates this page periodically, so check back re |
| gularly to | | gularly to |
| get the latest information and requirements for bulk email sender | | get the latest information and requirements for bulk email sender |
| s. | | s. |
| | | |
| **Important:** Starting February 2024, Gmail will require the fol | | **Important:** Starting February 2024, Gmail will require the fol |
| lowing for | | lowing for |
| senders who send 5,000 or more messages a day to Gmail accounts: | | senders who send 5,000 or more messages a day to Gmail accounts: |
| Authenticate | | Authenticate |
| outgoing email, avoid sending unwanted or unsolicited email, and | | outgoing email, avoid sending unwanted or unsolicited email, and |
| make it easy | | make it easy |
| for recipients to unsubscribe. [Get the detailed requirements for | | for recipients to unsubscribe. [Get the detailed requirements for |
| sending | | sending |
| 5,000 or more emails per day](/mail/answer/81126#requirements-5k) | | 5,000 or more emails per day](/mail/answer/81126#requirements-5k) |
| . | | . |
| | | |
| Expand all | [Collapse all](?) | | Expand all | [Collapse all](?) |
| | | |
| ## Bulk senders | | ## Bulk senders |
| | | |
| What is a bulk sender? | | What is a bulk sender? |
| | | |
| A _bulk sender_ is any email sender that sends close to 5,000 or | | A _bulk sender_ is any email sender that sends close to 5,000 or |
| more messages | | more messages |
| to personal Gmail accounts within a 24-hour period. Messages sent | | to personal Gmail accounts within a 24-hour period. Messages sent |
| from the | | from the |
| same primary domain count toward the 5,000 limit. | | same primary domain count toward the 5,000 limit. |
| | | |
| **Sending domains:** When we calculate the 5,000-message limit, w | | **Sending domains:** When we calculate the 5,000-message limit, w |
| e count all | | e count all |
| messages sent from the same primary domain. For example, every da | | messages sent from the same primary domain. For example, every da |
| y you send | | y you send |
| 2,500 messages from solarmora.com and 2,500 messages from | | 2,500 messages from solarmora.com and 2,500 messages from |
| promotions.solarmora.com to personal Gmail accounts. You’re consi | | promotions.solarmora.com to personal Gmail accounts. You’re consi |
| dered a bulk | | dered a bulk |
| sender because all 5,000 messages were sent from the same primary | | sender because all 5,000 messages were sent from the same primary |
| domain: | | domain: |
| solarmora.com. Learn about [domain name basics](/a/answer/2573637 | | solarmora.com. Learn about [domain name basics](/a/answer/2573637 |
| ). | | ). |
| | | |
| Senders who meet the above criteria at least once are permanently | | Senders who meet the above criteria at least once are permanently |
| considered | | considered |
| bulk senders. | | bulk senders. |
| | | |
| Does bulk sender status expire? Can I change my sending practices | | Does bulk sender status expire? Can I change my sending practices |
| to remove my | | to remove my |
| bulk sender status? | | bulk sender status? |
| | | |
| Bulk sender status doesn’t have an expiration date. Email senders | | Bulk sender status doesn’t have an expiration date. Email senders |
| that have | | that have |
| been classified as bulk senders are permanently classified as suc | | been classified as bulk senders are permanently classified as suc |
| h. Changes in | | h. Changes in |
| email sending practices will not affect permanent bulk sender sta | | email sending practices will not affect permanent bulk sender sta |
| tus once it’s | | tus once it’s |
| assigned. | | assigned. |
| | | |
| How can bulk senders make sure they’re meeting the sender guideli | | How can bulk senders make sure they’re meeting the sender guideli |
| nes? | | nes? |
| | | |
| Bulk senders should use Postmaster Tools to check that their emai | | Bulk senders should use Postmaster Tools to check that their emai |
| l practices | | l practices |
| are following our [Email sender guidelines](/mail/answer/81126). | | are following our [Email sender guidelines](/mail/answer/81126). |
| To learn | | To learn |
| more, visit our [Email sender requirements & Postmaster Tools | | more, visit our [Email sender requirements & Postmaster Tools |
| FAQ](/mail/answer/14289100). | | FAQ](/mail/answer/14289100). |
| | | |
| ## Google Workspace accounts | | ## Google Workspace accounts |
| | | |
| Do the sender guidelines apply to messages sent to Google Workspa | | Do the sender guidelines apply to messages sent to Google Workspa |
| ce accounts? | | ce accounts? |
| | | |
| The [Email sender guidelines](/mail/answer/81126) don’t apply to | | The [Email sender guidelines](/mail/answer/81126) don’t apply to |
| messages sent | | messages sent |
| to Google Workspace accounts. Sender requirements and Google enfo | | to Google Workspace accounts. Sender requirements and Google enfo |
| rcement apply | | rcement apply |
| only when sending email to personal Gmail accounts. | | only when sending email to personal Gmail accounts. |
| | | |
| Do the sender guidelines apply to messages sent from Google Works | | Do the sender guidelines apply to messages sent from Google Works |
| pace | | pace |
| accounts? | | accounts? |
| | | |
| All senders, including Google Workspace users, must meet the requ | | All senders, including Google Workspace users, must meet the requ |
| irements in | | irements in |
| our [Email sender guidelines](/mail/answer/81126) when sending me | | our [Email sender guidelines](/mail/answer/81126) when sending me |
| ssages to | | ssages to |
| personal Gmail accounts. The requirements don’t apply to Google W | | personal Gmail accounts. The requirements don’t apply to Google W |
| orkspace | | orkspace |
| inbound and intra-domain messages. | | inbound and intra-domain messages. |
| | | |
| ## Sender guidelines enforcement | | ## Sender guidelines enforcement |
| | | |
| What is the timeline for enforcement of sender guidelines? | | What is the timeline for enforcement of sender guidelines? |
| | | |
| Enforcement for bulk senders that don’t meet our [Email sender | | Enforcement for bulk senders that don’t meet our [Email sender |
| guidelines](https://support.google.com/mail/answer/81126) will be | | guidelines](https://support.google.com/mail/answer/81126) will be |
| gradual and | | gradual and |
| progressive. | | progressive. |
| | | |
| In February 2024, bulk senders who don’t meet sender requirements | | In February 2024, bulk senders who don’t meet sender requirements |
| will start | | will start |
| getting temporary errors (with error codes) on a small percentage | | getting temporary errors (with error codes) on a small percentage |
| of their | | of their |
| non-compliant email traffic. These temporary errors are meant to | | non-compliant email traffic. These temporary errors are meant to |
| help senders | | help senders |
| identify email traffic that doesn’t meet our guidelines so that s | | identify email traffic that doesn’t meet our guidelines so that s |
| enders can | | enders can |
| resolve issues that result in non-compliance. | | resolve issues that result in non-compliance. |
| | | |
| In April 2024, we’ll start rejecting a percentage of non-complian | | In April 2024, we’ll start rejecting a percentage of non-complian |
| t email | | t email |
| traffic, and we’ll gradually increase the rejection rate. For exa | | traffic, and we’ll gradually increase the rejection rate. For exa |
| mple, if 75% | | mple, if 75% |
| of a sender’s traffic meets our requirements, we’ll start rejecti | | of a sender’s traffic meets our requirements, we’ll start rejecti |
| ng a | | ng a |
| percentage of the remaining 25% of traffic that isn’t compliant. | | percentage of the remaining 25% of traffic that isn’t compliant. |
| | | |
| Bulk senders have until June 1, 2024 to implement one-click unsub | | Bulk senders have until June 1, 2024 to implement one-click unsub |
| scribe in all | | scribe in all |
| commercial, promotional messages. | | commercial, promotional messages. |
| | | |
| We’ll prioritize technical support for email delivery issues for | | We’ll prioritize technical support for email delivery issues for |
| bulk senders | | bulk senders |
| that meet all the requirements described in our [Email sender | | that meet all the requirements described in our [Email sender |
| guidelines](/mail/answer/81126). | | guidelines](/mail/answer/81126). |
| | | |
| What happens if senders don’t meet the requirements in the sender | | What happens if senders don’t meet the requirements in the sender |
| guidelines? | | guidelines? |
| | | |
| To ensure messages are delivered as expected, bulk senders should | | To ensure messages are delivered as expected, bulk senders should |
| comply with | | comply with |
| our [Email sender guidelines](/mail/answer/81126). If senders don | | our [Email sender guidelines](/mail/answer/81126). If senders don |
| ’t meet these | | ’t meet these |
| requirements, messages might be rejected or delivered to recipien | | requirements, messages might be rejected or delivered to recipien |
| ts’ spam | | ts’ spam |
| folders. | | folders. |
| | | |
| If messages are rejected because they don’t meet the sender guide | | If messages are rejected because they don’t meet the sender guide |
| lines, do you | | lines, do you |
| send an error message or other alert? | | send an error message or other alert? |
| | | |
| Yes, when messages are rejected, we send a rejection code and a r | | Yes, when messages are rejected, we send a rejection code and a r |
| eason for the | | eason for the |
| rejection. You can also see this information in [Postmaster | | rejection. You can also see this information in [Postmaster |
| Tools](https://postmaster.google.com/managedomains?pli=1). | | Tools](https://postmaster.google.com/managedomains?pli=1). |
| | | |
| ## Spam rate | | ## Spam rate |
| | | |
| What time range or duration is used when calculating spam rate? | | What time range or duration is used when calculating spam rate? |
| | | |
| Spam rate is calculated daily. To help ensure messages are delive | | Spam rate is calculated daily. To help ensure messages are delive |
| red as | | red as |
| expected, senders should keep their spam rate below 0.1% and shou | | expected, senders should keep their spam rate below 0.1% and shou |
| ld prevent | | ld prevent |
| spam rates from ever reaching 0.3% or higher, as described in our | | spam rates from ever reaching 0.3% or higher, as described in our |
| [Email | | [Email |
| sender guidelines](/mail/answer/81126#spam-rate). | | sender guidelines](/mail/answer/81126#spam-rate). |
| | | |
| What happens when sender spam rate exceeds the maximum spam rate | | What happens when sender spam rate exceeds the maximum spam rate |
| allowed by | | allowed by |
| the guidelines? | | the guidelines? |
| | | |
| To comply with the sender guidelines, keep your spam rate below 0 | | To comply with the sender guidelines, keep your spam rate below 0 |
| .1% and | | .1% and |
| prevent spam rates from ever reaching 0.3% or higher. | | prevent spam rates from ever reaching 0.3% or higher. |
| | | |
| Spam rate impact is graduated, and spam rates of 0.3% or higher h | | Spam rate impact is graduated, and spam rates of 0.3% or higher h |
| ave an even | | ave an even |
| greater negative impact on email inbox delivery. Even today, spam | | greater negative impact on email inbox delivery. Even today, spam |
| rates | | rates |
| greater than 0.1% have a negative impact on email inbox delivery | | greater than 0.1% have a negative impact on email inbox delivery |
| for bulk | | for bulk |
| senders. When we begin enforcing sender guidelines, messages from | | senders. When we begin enforcing sender guidelines, messages from |
| bulk senders | | bulk senders |
| with a spam rate higher than 0.3% can be sent to spam or they can | | with a spam rate higher than 0.3% can be sent to spam or they can |
| be rejected. | | be rejected. |
| | | |
| You can monitor your spam rate with [Postmaster | | You can monitor your spam rate with [Postmaster |
| Tools](https://postmaster.google.com/managedomains). | | Tools](https://postmaster.google.com/managedomains). |
| | | |
| Starting February 2024, senders with a user-reported spam rate gr | | Starting February 2024, senders with a user-reported spam rate gr |
| eater than | | eater than |
| 0.3% will be ineligible for | | 0.3% will be ineligible for |
| [mitigation](/mail/contact/gmail_bulk_sender_escalation). Message | | [mitigation](/mail/contact/gmail_bulk_sender_escalation). Message |
| s from | | s from |
| senders that don’t meet sender guidelines aren’t automatically re | | senders that don’t meet sender guidelines aren’t automatically re |
| jected as | | jected as |
| part of enforcement. | | part of enforcement. |
| | | |
| ## Unsubscribe links | | ## Unsubscribe links |
| | | |
| Do all messages require one-click unsubscribe? | | Do all messages require one-click unsubscribe? |
| | | |
| No. One-click unsubscribe is required only for commercial, promot | | No. One-click unsubscribe is required only for commercial, promot |
| ional | | ional |
| messages. Transactional messages are excluded from this requireme | | messages. Transactional messages are excluded from this requireme |
| nt. Some | | nt. Some |
| examples of transactional messages are password reset messages, r | | examples of transactional messages are password reset messages, r |
| eservation | | eservation |
| confirmations, and form submission confirmations. | | confirmations, and form submission confirmations. |
| | | |
| Senders that already include an unsubscribe link in their message | | Senders that already include an unsubscribe link in their message |
| s have until | | s have until |
| June 1, 2024 to implement one-click unsubscribe in all commercial | | June 1, 2024 to implement one-click unsubscribe in all commercial |
| , promotional | | , promotional |
| messages. | | messages. |
| | | |
| If the list header is missing, is the message body checked for a | | If the list header is missing, is the message body checked for a |
| one-click | | one-click |
| unsubscribe link? | | unsubscribe link? |
| | | |
| No. One-click unsubscribe should be implemented according to [RFC | | No. One-click unsubscribe should be implemented according to [RFC |
| 8058](https://www.rfc-editor.org/rfc/rfc8058.txt). Including a ma | | 8058](https://www.rfc-editor.org/rfc/rfc8058.txt). Including a ma |
| ilto link in | | ilto link in |
| the body of your messages doesn’t meet our one-click unsubscribe | | the body of your messages doesn’t meet our one-click unsubscribe |
| requirement. | | requirement. |
| | | |
| If unsubscribe links are temporarily unavailable due to maintenan | | If unsubscribe links are temporarily unavailable due to maintenan |
| ce or other | | ce or other |
| reasons, are messages flagged as spam? | | reasons, are messages flagged as spam? |
| | | |
| If your unsubscribe link isn’t working for an extended period of | | If your unsubscribe link isn’t working for an extended period of |
| time, your | | time, your |
| messages won’t meet our one-click unsubscribe requirement. These | | messages won’t meet our one-click unsubscribe requirement. These |
| messages | | messages |
| won’t be marked as spam, but senders aren’t eligible for | | won’t be marked as spam, but senders aren’t eligible for |
| [mitigation](/mail/contact/gmail_bulk_sender_escalation) for emai | | [mitigation](/mail/contact/gmail_bulk_sender_escalation) for emai |
| l delivery | | l delivery |
| issues. | | issues. |
| | | |
| Can a one-click unsubscribe link to a landing or preferences page | | Can a one-click unsubscribe link to a landing or preferences page |
| ? | | ? |
| | | |
| We recommend senders follow the specifications for one-click unsu | | We recommend senders follow the specifications for one-click unsu |
| bscribe that | | bscribe that |
| are defined in [RFC 8058](https://www.rfc-editor.org/rfc/rfc8058. | | are defined in [RFC 8058](https://www.rfc-editor.org/rfc/rfc8058. |
| txt). Email | | txt). Email |
| admins should use this specification as the reference for impleme | | admins should use this specification as the reference for impleme |
| nting one- | | nting one- |
| click unsubscribe. One-click unsubscribe links that link to a lan | | click unsubscribe. One-click unsubscribe links that link to a lan |
| ding or other | | ding or other |
| type of web page don’t comply with RFC 8058. | | type of web page don’t comply with RFC 8058. |
| | | |
| ## Email authentication | | ## Email authentication |
| | | |
| What is the DMARC alignment requirement for bulk senders? | | What is the DMARC alignment requirement for bulk senders? |
| | | |
| For messages sent directly to personal Gmail accounts, the organi | | For messages sent directly to personal Gmail accounts, the organi |
| zational | | zational |
| domain in the sender From: header must be aligned with either the | | domain in the sender From: header must be aligned with either the |
| SPF | | SPF |
| organizational domain or the DKIM organizational domain. Although | | organizational domain or the DKIM organizational domain. Although |
| we require | | we require |
| bulk senders to set up both SPF and DKIM authentication, only one | | bulk senders to set up both SPF and DKIM authentication, only one |
| of these | | of these |
| needs to be aligned to meet the sender alignment requirements. | | needs to be aligned to meet the sender alignment requirements. |
| | | |
| DMARC alignment isn’t required for forwarded or mailing list mess | | DMARC alignment isn’t required for forwarded or mailing list mess |
| ages | | ages |
| (sometimes referred to as _indirect messages_ ), however we requi | | (sometimes referred to as _indirect messages_ ), however we requi |
| re that these | | re that these |
| types of messages have ARC headers. Learn more about [ARC authent | | types of messages have ARC headers. Learn more about [ARC authent |
| ication and | | ication and |
| headers](/a/answer/13198639). | | headers](/a/answer/13198639). |
| | | |
| To ensure reliable authentication, we recommend all senders fully | | To ensure reliable authentication, we recommend all senders fully |
| align DMARC | | align DMARC |
| to both SPF and DKIM. It’s likely that DMARC alignment with both | | to both SPF and DKIM. It’s likely that DMARC alignment with both |
| SPF and DKIM | | SPF and DKIM |
| will eventually be a sender requirement. Learn more about [DMARC | | will eventually be a sender requirement. Learn more about [DMARC |
| alignment](/a/answer/10032169#alignment). | | alignment](/a/answer/10032169#alignment). |
| | | |
| If messages fail DMARC authentication, can they be delivered usin | | If messages fail DMARC authentication, can they be delivered usin |
| g IP allow | | g IP allow |
| lists or spam bypass lists? Or will these messages be quarantined | | lists or spam bypass lists? Or will these messages be quarantined |
| ? | | ? |
| | | |
| If messages fail DMARC because of authentication or alignment iss | | If messages fail DMARC because of authentication or alignment iss |
| ues, the | | ues, the |
| enforcement defined in the sending domain’s DMARC policy generall | | enforcement defined in the sending domain’s DMARC policy generall |
| y applies. If | | y applies. If |
| the sending domain doesn’t have a DMARC policy, the messages migh | | the sending domain doesn’t have a DMARC policy, the messages migh |
| t be rejected | | t be rejected |
| or sent to spam. Failing DMARC authentication is one of several f | | or sent to spam. Failing DMARC authentication is one of several f |
| actors that | | actors that |
| determine whether messages are rejected, sent to spam, or deliver | | determine whether messages are rejected, sent to spam, or deliver |
| ed as | | ed as |
| expected. DMARC authentication is an important determining factor | | expected. DMARC authentication is an important determining factor |
| , and so | | , and so |
| these messages are typically handled based on the enforcement set | | these messages are typically handled based on the enforcement set |
| ting in the | | ting in the |
| sending domain’s DMARC policy. | | sending domain’s DMARC policy. |
| | | |
| Learn more about [DMARC policies and enforcement options](/a/answ | | Learn more about [DMARC policies and enforcement options](/a/answ |
| er/10032169). | | er/10032169). |
| | | |
| ## Support & escalation | | ## Support & escalation |
| | | |
| Can bulk senders get technical support for email delivery issues? | | Can bulk senders get technical support for email delivery issues? |
| | | |
| Bulk senders that meet all requirements described in our [Email s | | Bulk senders that meet all requirements described in our [Email s |
| ender | | ender |
| guidelines](/mail/answer/81126)can submit an escalation for email | | guidelines](/mail/answer/81126)can submit an escalation for email |
| delivery | | delivery |
| issues. Before contacting tech support, make sure you’re followin | | issues. Before contacting tech support, make sure you’re followin |
| g all sender | | g all sender |
| guidelines. Starting in February 2024, we won’t provide | | guidelines. Starting in February 2024, we won’t provide |
| [mitigation](/mail/contact/gmail_bulk_sender_escalation) for emai | | [mitigation](/mail/contact/gmail_bulk_sender_escalation) for emai |
| l delivery | | l delivery |
| issues to senders that don’t meet the guidelines. For details abo | | issues to senders that don’t meet the guidelines. For details abo |
| ut mitigation | | ut mitigation |
| requests, visit the [Sender contact | | requests, visit the [Sender contact |
| form](/mail/contact/gmail_bulk_sender_escalation). | | form](/mail/contact/gmail_bulk_sender_escalation). |
| | | |
| ## Related topics | | ## Related topics |
| | | |
| [Email sender guidelines](/mail/answer/81126) | | [Email sender guidelines](/mail/answer/81126) |
| | | |
| ## Was this helpful? | | ## Was this helpful? |
| | | |
| How can we improve it? | | How can we improve it? |
| | | |
| YesNo | | YesNo |
| | | |
| Submit | | Submit |
| | | |
| ## Need more help? | | ## Need more help? |
| | | |
| ### Try these next steps: | | ### Try these next steps: |
| | | |
| [ Post to the help community Get answers from community members | | [ Post to the help community Get answers from community members |
| ](/a/community?hl=en&help_center_link=\[14229414,%22Email%20sende | | ](/a/community?hl=en&help_center_link=\[14229414,%22Email%20sende |
| r%20guidelines%20FAQ%22\]) | | r%20guidelines%20FAQ%22\]) |
| [ Contact us Tell us more and we’ll help you get there ](/a/gethe | | [ Contact us Tell us more and we’ll help you get there ](/a/gethe |
| lp) | | lp) |
| | | |
| true | | true |
| | | |
n | ## [Problems with sending ](/a/topic/1354753?hl=en&ref_topic=1258 | n | ## [Bulk email sending guidelines & |
| 984) | | |
| | | tools](/a/topic/7279058?hl=en&ref_topic=28609) |
| | | |
n | * 1 of 11 | n | * 1 of 4 |
| | | |
n | [Fix bounced or rejected emails](/a/answer/6596?hl=en&ref_topic=1 | n | [Email sender guidelines](/a/answer/81126?hl=en&ref_topic=7279058 |
| 354753) | | ) |
| | | |
n | * 2 of 11 | n | * 2 of 4 |
| | | |
| [Fix email bounces due to blocked IP | | |
| address](/a/answer/27642?hl=en&ref_topic=1354753) | | |
| | | |
| * 3 of 11 | | |
| | | |
| [Messages from a bulk sender bounce](/a/answer/168383?hl=en&ref_t | | |
| opic=1354753) | | |
| | | |
| * 4 of 11 | | |
| | | |
| [Message bounced due to a policy | | |
| rule](/a/answer/7282433?hl=en&ref_topic=1354753) | | |
| | | |
| * 5 of 11 | | |
| | | |
| [Email bounces with error message](/a/answer/1071514?hl=en&ref_to | | |
| pic=1354753) | | |
| | | |
| * 6 of 11 | | |
| | | |
| [Avoid email bouncing from new MX | | |
| records](/a/answer/45679?hl=en&ref_topic=1354753) | | |
| | | |
| * 7 of 11 | | |
| | | |
| [Best practices for forwarding email to | | |
| Gmail](/a/answer/175365?hl=en&ref_topic=1354753) | | |
| | | |
| * 8 of 11 | | |
| | | |
| [Some recipients don't get my | | |
| email](/a/answer/7675859?hl=en&ref_topic=1354753) | | |
| | | |
| * 9 of 11 | | |
| | | |
| [SMTP relay spam policy in Gmail](/a/answer/6389191?hl=en&ref_top | | |
| ic=1354753) | | |
| | | |
| * 10 of 11 | | |
| | | |
| Email sender guidelines FAQ | | Email sender guidelines FAQ |
| | | |
n | * 11 of 11 | n | * 3 of 4 |
| | | |
t | [Email sender guidelines](/a/answer/81126?hl=en&ref_topic=1354753 | t | [Feedback Loop](https://support.google.com/a/answer/6254652) |
| ) | | |
| | | |
| | | * 4 of 4 |
| | | |
| | | [Postmaster Tools](/a/topic/6259779?hl=en&ref_topic=7279058) |
| | | |
| [ | | [ |
| ![](https://lh3.googleusercontent.com/exxMjxadqER4Ie3_TMeBqZfSwNB | | ![](https://lh3.googleusercontent.com/exxMjxadqER4Ie3_TMeBqZfSwNB |
| fL_3tU0Xvn4tJ3_POtw4haXNbIx7OL7v52_DcaBpe=w96) | | fL_3tU0Xvn4tJ3_POtw4haXNbIx7OL7v52_DcaBpe=w96) |
| ](https://workspace.google.com/signup/businessstarter/welcome) | | ](https://workspace.google.com/signup/businessstarter/welcome) |
| | | |
| [Start your free 14-day trial | | [Start your free 14-day trial |
| today](https://workspace.google.com/signup/businessstarter/welcom | | today](https://workspace.google.com/signup/businessstarter/welcom |
| e) | | e) |
| | | |
| Professional email, online storage, shared calendars, video meeti | | Professional email, online storage, shared calendars, video meeti |
| ngs and more. | | ngs and more. |
| [Start your free Google Workspace trial | | [Start your free Google Workspace trial |
| today](https://workspace.google.com/signup/businessstarter/welcom | | today](https://workspace.google.com/signup/businessstarter/welcom |
| e). | | e). |
| | | |
| * ©2023 Google | | * ©2023 Google |
| * [Privacy Policy](//www.google.com/intl/en/privacy.html) | | * [Privacy Policy](//www.google.com/intl/en/privacy.html) |
| * [Terms of Service](https://www.google.com/accounts/TOS) | | * [Terms of Service](https://www.google.com/accounts/TOS) |
| | | |
| DeutschespañolfrançaisIndonesiaitalianoNederlandspolskiportuguês | | DeutschespañolfrançaisIndonesiaitalianoNederlandspolskiportuguês |
| (Brasil)svenskaTiếng | | (Brasil)svenskaTiếng |
| ViệtTürkçeрусскийукраїнськаעבריתالعربيةไทย中文(简体)中文(繁體)日本語한국어 Engl | | ViệtTürkçeрусскийукраїнськаעבריתالعربيةไทย中文(简体)中文(繁體)日本語한국어 Engl |
| ish | | ish |
| | | |
| Enable Dark Mode | | Enable Dark Mode |
| | | |
| Send feedback on... | | Send feedback on... |
| | | |
| This help content & information General Help Center experience | | This help content & information General Help Center experience |
| | | |
| Search | | Search |
| | | |
| Clear search | | Clear search |
| | | |
| Close search | | Close search |
| | | |
| Google apps | | Google apps |
| | | |
| Main menu | | Main menu |
| | | |
| | | |
| | | |
| true | | true |
| | | |
| Search Help Center | | Search Help Center |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| | | |
| | | |
| false | | false |
| | | |
| false | | false |
| | | |
| | | |