Set up routing for your domain or organization

Check this box to add a header tag if the recipient is changed. That way, the downstream server will know the original envelope recipient. An example of the header tag format is X-Gm-Original-To: user@solarmora.com. 

Headers are useful if you're rerouting a copy of the message to another recipient. In this case, you're changing the recipient address, but the new recipient can still see the address of the original envelope recipient. They can see the original envelope recipient by checking the X-Gm-Original-To header in the message.

Gmail messages are automatically filtered for spam and phishing. Check the Add X-Gm-Spam and X-Gm-Phishy headers box to add these headers to indicate the spam and phishing status of the message. For example, an administrator at a downstream server can use this information to set up rules that handle spam and phishing differently from clean mail.

• X-Gm-Spam: 0 indicates the message isn't spam.
• X-Gm-Spam: 1 indicates the message is spam.
• X-Gm-Phishy: 0 indicates the message is not phishing.
• X-Gm-Phishy: 1 indicates the message is phishing.

Any message marked phishy is automatically marked spam as well.

If you add X-Gm-Spam and X-Gm-Phishy headers to your messages, consider where the message is being routed to next. A rerouted message is often no longer classified as spam when it reaches its destination because elements of the message, such as the sending IP address, have changed.

If your messages are rerouted to your downstream server, set up rules on that server to read these headers and prevent messages with X-Gm-Spam: 1 or X-Gm-Phishy: 1 tags from being delivered to users’ inboxes.

If your messages are rerouted back to Google, create an Inbound gateway setting to mark tagged messages as spam, or a Content compliance setting to send them to the Admin Quarantine for review.

Note: If the Account types to affect is set to Groups, the X-Gm-Spam and X-Gm-Phishy header tag values are always set to 0. See Account types to affect, below, for information on the account types.

• Change route—Changes the destination of the message. By default, the Gmail server is the primary delivery location. However, you can change it to route messages to a different mail server, such as Microsoft^® Exchange.
  
  Note: Before you can change the route, you need to add the route using the Hosts tab. After it's added, it'll appear in the Change route list.

• Also reroute spam—Appears if you select Change route. Also reroute spam lets you route all email that matches the criteria of the setting, including messages marked as spam. 
  
  If you don't check the Also reroute spam box, then normal messages are rerouted, but spam messages aren't.

Notes:

• Whether or not you select Also reroute spam, blatant spam is not rerouted because it’s dropped instantly at delivery time.

• If a message is classified as spam but one of the G Suite email settings overrides it (for example, due to a sender whitelist), then the message isn't considered to be spam for this purpose and it's routed as a normal message.

You can change the envelope recipient in one of the following ways:

• To replace the recipient’s entire email address, after Replace recipient, enter the full email address, such as user@solarmora.com.

• To replace just the username of the recipient's email address and keep the domain the same, before @existing-domain, enter the username, such as user.

• To replace just the domain of the recipient's email address and keep the username the same, after existing-username@, enter the domain, such as solarmora.com.

Changing the envelope recipient for a message on the primary address is equivalent to forwarding a message to a different recipient. The message bypasses the original recipient’s mailbox and is routed back to the internet for delivery to the new recipient. The To: address remains the original recipient address, even though the envelope recipient is replaced.

The destination server is determined by an MX lookup on the new recipient's domain. Or, if you’re using the Change route control, the destination server determined by the specified route.

If you'd rather Bcc an additional recipient, use the Add more recipients option, described below.

Check this box to deliver incoming messages to recipients even if the spam filter identifies them as spam. This option applies to incoming messages only—you can’t bypass spam filters for outgoing messages.

Note: This option applies to the Users and Unrecognized / Catch-all account types, and not the Groups account type. See Account types to affect, below, for information on the account types.

1. Check the Add more recipients box and then click Add to set up dual delivery or multiple delivery.

2. Select Basic from the list to add individual email addresses and then click Save. Click Add to add more addresses.

3. Select Advanced from the list to choose advanced options for your secondary delivery. Similar to the settings for primary delivery, you can change the envelope recipient, add headers, prepend a custom subject, and remove attachments for secondary deliveries.

Notes:

• A limit of 100 additional recipients applies for each rule. For this reason, consider using groups for large lists.

• Any settings that you configure for the primary delivery also affect the secondary deliveries. For example, if you change the envelope recipient, prepend a custom subject, and add custom headers to the primary delivery, the same configuration is applied to the secondary deliveries. If you change the envelope recipient, the To: address still remains the original recipient address.

• For secondary deliveries, the Do not deliver spam to this recipient and Suppress bounces from this recipient boxes are checked by default. If the message is spam, this option discards the copy of the message being sent to the additional recipient. Suppress bounces from this recipient prevents bounces from going back to the original sender.

By default, Gmail always attempts to deliver messages using secure transport (TLS). If secure transport isn’t available, the message is delivered over a nonsecure connection.

Check the Require secure transport (TLS) box to include secure delivery as part of content compliance for outbound messages. This requires all messages meeting the conditions in the setting (such as match expressions, account types, and envelope filters) to be transmitted via a secure connection. If TLS isn't available on the sending or receiving side, the message won't be sent.

Check the Encrypt message if not encrypted (S/MIME) box to make sure that certain messages can’t be sent unless they are S/MIME encrypted. See note below.

Also check the Bounce message if unable to encrypt box to bounce messages that aren’t S/MIME encrypted.

Learn more about enhancing message security with hosted S/MIME.

Select one or more account types that the setting applies to. The account types are Users, Groups, and Unrecognized / Catch-all. You can't save the setting if you haven't selected an account type.

If you’re configuring the setting for the top-level organization and you select the Modify message or Reject message action, all 3 account types are available. If the action is Quarantine message, just the Users account type is available.

If you’re configuring a sub-level organization, the only available account type is Users, regardless of the action.

The Groups account type doesn't apply to the Add X-Gm-Spam and X-Gm-Phishy headers control. If the account type is Groups, the headers are always X-Gm-Spam: 0 and X-Gm-Phishy: 0. The Groups account type also doesn't apply to the Bypass spam filter for this message control.

By default, Users is selected, because it's the most common use case. You can select more than one. For example, you can configure an inbound setting that only applies to the Groups account type, and the group must be the recipient. If you’re configuring an outbound setting, the account type must match the sender.

When you're done:

1. (Optional) Specify an envelope filter.

2. Go to Save the configuration.