Questions
Emails received from the business system are being excluded from the archive.
Answer
When emails are sent to Gmail from the following environments, they may be excluded from the archive.
- The domain used in the Header From address is the same as the domain used in Gmail (including subdomains)
- The domain used in the Envelope From is the same as the domain used in Gmail (including subdomains)
- The Source IP address of the business system is included in the domain's SPF record or registered in Gmail's receiving gateway settings.
This is because Gmail mistakenly recognizes these emails as being received internally. If this issue occurs, add an individual archive setting for the business system.
※ If the email itself cannot be received, please check that it is not being judged as spam by adding it to the "Receiving Gateway" or "Whitelist".
Pre-check
1. Prepare the HENNGE One Connection Settings Sheet provided by us in advance.
2. Check the global IP address of the sending server of the business system.
※ If the sending system uses IPv6, also check the IPv6 format IP address.
Procedure
1. Access the Google Workspace admin console.
https://admin.google.com/AdminHome
2. Click [Apps] - [Google Workspace] - [Gmail].
3. Click [Compliance].
4. Scroll down and click [Settings] or [Add another rule] under the [Content Compliance] section.
5. Enter a description of the rule in the [Required] field.
Example) HENNGE Email Archive (rsmtpd_inbound) for Business System
6. Set [Affected Emails] as follows.
Check "Internal - Receiving".
7. Select [If any of the following match the email] and click [Add].
8. Select [Match Metadata].
9. Set [Attribute] and [Match Type] as follows, and click [Save].
※ If the sending system uses IPv6, also register the IPv6 format IP address.
- Attribute: Source IP
- Match Type: Source IP is within the following range
- Enter the IP address of the sending server of the business system in the field below
10. Confirm that the Search Conditions have been registered, then scroll down the screen.
11. Check [Add Recipient] under [Other Destinations] and click [Add].
12. Select [Details] from the dropdown.
13. Check [Change Route] and change [Normal Routing] to [HENNGE Email Archive (rsmtpd_inbound)].
14. Check [Add Custom Header] and click [Add].
15. Set as follows and click [Save].
- Header Key: Hdems-Archive-Domain
- Header Value: Refer to the "HENNGE Email Archive Connection Settings" sheet in the HENNGE One Connection Settings Sheet and enter the common header value used in the forwarding settings.
16. Confirm that the value set in step 15 is entered, then click [Save].
17. Scroll down the screen and click [Show Options].
18. Set [Types of Affected Accounts] as follows and click [Save].
- User: Check
- Group: Check
- Unrecognized, Catch-all: Uncheck
19. Click [Add another rule].
20. Repeat steps 5 to 18 to register content compliance with the following details.
|
Step |
Item Name |
Setting Value |
|
5 |
Name |
HENNGE Email Archive (bsmtpd_inbound) for Business System |
|
6 |
Effect on email |
□ Receive □ Send □ Internal & Send ■ Internal & Receive |
|
7 |
Add expressions representing content to search in each message |
Select "If part of the following matches the email" |
|
8 |
Simple Content Match / Advanced Content Match / Metadata Match |
Select "Metadata Match" |
|
9 |
Attribute |
Select "Source IP" |
|
9 |
Match Type |
Select "Source IP is within the following range" and enter the source IP address of the business system in the field below |
|
11 |
Other Recipients |
■ Add Recipient |
|
12 |
Basic / Advanced Settings |
Select "Advanced" |
|
13 |
Route |
■ Change Route HENNGE Email Archive (bsmtpd_inbound) |
|
14 |
Header |
□ Add X-Gm-Original-To Header □ Add X-Gm-Spam Header and X-Gm-Phishy Header |
|
15 |
Add Custom Header → Header Key |
X-Hdems-Archive-Domain ※ Enter only the underlined part |
|
15 |
Add Custom Header → Header Value |
Refer to the "HENNGE Email Archive Connection Settings" sheet in the HENNGE One Connection Settings Sheet |
|
18 |
Options → B. Type of Affected Account |
■ User ■ Group □ Unrecognized, Catch-all |
21. Confirm that two settings have been added in the [Content Compliance] section.