Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.scribe-mail.com/llms.txt

Use this file to discover all available pages before exploring further.

Centralized one-click installation. No teammate action needed. Users don’t see signatures when composing emails. Your emails are processed through Scribe’s secure servers for signature injection.
Supported platforms: Web, Desktop, Apple Mail, iOS, Android

​
Installation guide

This is an advanced user feature. IT support is required to set up this integration.
  • Users don’t see signatures when composing an email.
  • Your emails are processed through Scribe’s secure servers to install signatures. Scribe cannot read or edit your emails.
  • You can combine cloud-based integration with server-side integration. If both are connected, Scribe defaults to cloud-based integration so users can see their signatures when composing emails.
1

Add host

To route emails through Scribe’s secure servers, create a host in Google Workspace Gmail. In Google Admin, go to Apps → Google Workspace → Gmail, then click ‘Hosts’.
Google Admin Gmail Hosts section
2

Click the "ADD ROUTE" link and fill in the form

Fill in the form with the following info:a. Name: Scribeb. Select: “Single host”c. Host name or IP:
smtp.server.scribe-mail.com
d. Port: 25e. Select: the options like in the screenshot below
Edit mail route form with Scribe host configuration
3

Configure the SMTP relay service

To receive emails back from Scribe for routing to recipients, go to Apps → Google Workspace → Gmail in Google Admin, then click ‘Routing’.
Google Admin Gmail Routing section
4

Click Configure under "SMTP relay service"

On the next page, click Configure under “SMTP relay service”.
SMTP relay service Configure button
5

Fill in the SMTP relay form

Fill in the form with the following information:a. Description: Receive from Scribeb. Authentication: Check “Only accept mail from the specified IP addresses” Add:
15.236.243.144
and
51.44.50.107
c. Select: “Require TLS encryption”d. Click: “Save”
SMTP relay service configuration form
6

Route your emails through the created Host

In Google Admin, go to Apps → Google Workspace → Gmail, then click ‘Compliance’.
Google Admin Gmail Compliance section
7

Click Configure under "Content compliance"

On the next page, click Configure under “Content compliance”.
Content compliance Configure button
8

Fill in the Content compliance form

Fill in the form as shown in the screenshot:a. Description: Route to Scribeb. Select: “Outbound” and “Internal - sending” in “Email messages to affect”c. In the second configuration item, add an expression with: Location: Full headers, Match type: Does not contain text, Content: X-Scribe-Processed. This prevents processing your email multiple times.d. In the third configuration item, change the route to the host you created in part 1 of this guide.e. Select: “Require secure transport (TLS)”f. Click: “Save”
Content compliance form configuration
9

Add the compliance rule expression

In the Compliance rule expression modal, add the info as shown in the screenshot:Advanced content match:
  • Location: Full headers
  • Match type: Not contains text
  • Content: X-Scribe-Processed
Compliance rule expression modal with X-Scribe-Processed header check
10

Configure DKIM

Configure DKIM for your sending domains to keep emails out of spam folders and avoid missing assets such as images and links.Click Configure DKIM in Scribe to start the configuration.
Configure DKIM button in Scribe
11

Install team signatures

From your signatures list, install all signatures at once for your teammates or install them one by one for a progressive rollout.
Scribe signatures list with Install Signatures button