How to Whitelist by IP Address in Google Workspace
In this article, you can learn how to whitelist KnowBe4's emails by IP address in Google Workspace. Whitelisting can help you ensure that your users receive our simulated phishing tests and training notifications.
We only recommend whitelisting by IP address if you don't have a cloud-based spam filter. If you have a cloud-based spam filter, we recommend whitelisting by email header instead. For more information, see our Whitelisting by Header in Google Workspace or Whitelisting Data and Anti-Spam Filtering Information articles.
Jump to:
Add KnowBe4's IP addresses to Email Whitelist
Add KnowBe4's IP addresses as Inbound Gateways
Add KnowBe4's IP addresses to Email Whitelist
To whitelist our IP addresses, you'll need to add our IP addresses to your email whitelist in Google Workspace.
To add our IP addresses to your email whitelist, follow the steps below. These steps are based on Google's Email Whitelist in Google Workspace page.
- Log in to your Google Workspace Admin console and click Apps.
- Click Google Workspace.
- In the Showing status for apps in all organizational units area, click Gmail.
- Click Spam, phishing, and malware.
Tip: If you use an older version of Google Workspace, you may need to click the Advanced settings button to see this option.
- In the Organizational Unit section of the page, select your domain.
Note: Google Workspace only allows whitelisting by IP address for an entire domain, so you're unable to whitelist by IP Address for individual organizational units (OUs).
- In the Email whitelist section, enter our IP addresses separated by commas. For the most up-to-date list of our IP addresses, see the IP Addresses, Hostnames, and Header Information section of our Whitelisting Data and Anti-Spam Filtering Information article.
- Click SAVE.
Next, see the section below to add our IP addresses as inbound gateways.
Add KnowBe4's IP addresses as Inbound Gateways
When your users receive a simulated phishing email from KnowBe4, banners may display in Gmail to say "This message seems dangerous" (click to view) or "Be careful with this message" (click to view).To prevent these banners from displaying, we recommend that add our IP addresses as inbound gateways.
To add our IP addresses as inbound gateways, follow the steps below:
- Log in to your Google Workspace Admin console.
- Follow step 2 through step 4 in the Add KnowBe4's IP addresses to Email Whitelist section above. These steps will take you to your Spam, phishing, and malware settings.
- In the Organizational Unit section of the page, select your domain.
- Click Inbound Gateway.
- Select the Enable check box to open the Inbound gateway page.
- Configure the Inbound gateway. For more information, see the screenshot and list below:
- Gateway IPs: Enter KnowBe4's IP addresses. For the most up-to-date list of our IP addresses, see the IP Addresses, Hostnames, and Header Information section of our Whitelisting Data and Anti-Spam Filtering Information article.
- Don't select the Reject all mail not from gateway IPs check box.
Note: The Automatically detect external IP setting may interfere with whitelisting for KnowBe4. Unless you use other IP addresses that require you to enable this setting, we recommend that you don't select the Automatically detect external IP check box. For more information, see Google's Set up an inbound mail gateway article.
- Select the Require TLS for connections from the email gateways listed above check box.
- In the Message Tagging field, enter a Spam Header Tag that is unlikely to be found in a PST email. For example, you could enter random letters such as "kzndsfgklinjvsdnfioasm".
- Select the Disable Gmail spam evaluation on mail from this gateway; only use header value check box.
- Click the SAVE button.
This setting may take up to an hour to deploy to all of your users. After at least an hour, we recommend that you set up a test phishing campaign for yourself or a small group of users. This test phishing campaign can help you make sure that your whitelisting was successful.
Comments
0 comments
Article is closed for comments.