Google Workspace (Server Side)

Server-side installation automatically adds signatures to emails from any device or client.

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’.

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

   Fill in the form with the following info:

   a. Name: Scribe

   b. Select: “Single host”

   c. Host name or IP:

   smtp.server.scribe-mail.com
   

   d. Port: 25

   e. Select: the options like in the screenshot below

   
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’.

   
4. Click Configure under "SMTP relay service"

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

   
5. Fill in the SMTP relay form

   Fill in the form with the following information:

   a. Description: Receive from Scribe

   b. 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”

   
6. Route your emails through the created Host

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

   
7. Click Configure under "Content compliance"

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

   
8. Fill in the Content compliance form

   Fill in the form as shown in the screenshot:

   a. Description: Route to Scribe

   b. 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”

   
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

   
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.

    
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.