GOOGLE-WORKSPACE-ADMINISTRATOR practice question 23 of 25

You are in the middle of migrating email from on-premises Microsoft Exchange to Google Workspace. Users that you have already migrated are complaining of messages from internal users going into spam folders. What should you do to ensure that internal messages do not go into Gmail spam while blocking spoofing attempts?

Full set: 199 questions

Domain Business initiatives

Answer options
A: Train users to click on Not Spam button for emails.
B: Add all users of your domain to an approved sender list.
C: Force TLS for your domain.
D: Ensure that your inbound gateway is configured with all of your Exchange server IP addresses. Correct answer
Correct Answer:
D. Ensure that your inbound gateway is configured with all of your Exchange server IP addresses.
Explanation

In a hybrid email environment during a migration from an on-premises server (like Microsoft Exchange) to Google Workspace, Gmail's spam filters may incorrectly flag emails from your on-premises servers as spoofed. This happens because the emails claim to be from your domain but originate from IP addresses not listed in your domain's SPF record as authorized senders (which typically points to Google's servers). The Inbound gateway setting is designed specifically for this scenario. By adding the IP addresses of your on-premises Exchange servers to this setting, you instruct Google Workspace to trust mail originating from these specific IPs, bypassing SPF checks for them and treating them as internal. This prevents them from being marked as spam while maintaining spoofing protection against all other external sources.

Why Incorrect

A. Train users to click on Not Spam button for emails. This is a reactive, user-dependent approach that does not fix the underlying server configuration issue causing the problem systemically.
B. Add all users of your domain to an approved sender list. This is an inefficient and overly broad solution that could inadvertently allow actual spoofed messages from external attackers to bypass spam filters.
C. Force TLS for your domain. TLS encrypts email connections to prevent eavesdropping but does not authenticate the sending server's identity or its authority to send for your domain. ---

References

1. Google Workspace Admin Help, "Set up an inbound mail gateway."

Section: "Step 2: Add the gateway's IP addresses to the inbound gateway setting"

Content: "The inbound mail gateway setting lets you specify the IP addresses of your mail gateways. Gmail checks incoming messages from these IP addresses to verify that they are authenticated with SPF and DKIM. If messages aren't authenticated, they are rejected. For messages from the gateway IPs, Gmail also bypasses SPF checks." This directly supports using the inbound gateway to have Gmail trust the on-premises server IPs.

2. Google Workspace Admin Help, "Email routing and delivery options for Google Workspace."

Section: "Dual delivery"

Content: This document describes scenarios where mail is delivered to two different mail systems simultaneously, a common practice during migrations. It states, "Use your non-Gmail mail server as the primary server... Configure the primary server to route a copy of every message to a secondary Gmail address." In such a setup, the inbound gateway is essential for the primary (on-premises) server to successfully deliver mail to Gmail mailboxes without being flagged as spam.

3. Google Workspace Admin Help, "Help prevent spoofing and spam with SPF."

Section: "Bypass SPF authentication for internal messages"

Content: "If you route mail through a gateway or server before it's delivered to Google Workspace, add the gateway or server IP address to the inbound gateway setting. The inbound gateway setting bypasses SPF checks for messages received from the gateway." This explicitly states that the inbound gateway is the correct mechanism to bypass SPF checks for trusted internal mail relays, which is the core issue in the question.

Scroll to Top