Let us know if this article was helpful. It would help us improve our content for you and other customers in the future.
Server-side signatures are applied post-send by WiseStamp's cloud service, ensuring consistency across all devices and email clients. This is ideal for multi-device users or those with different email platforms. This article describes how to configure your Google Workspace Admin Console to support WiseStamp’s server-side solution.
!note!This article focuses on the Google Workspace server-side connection. If you are looking to connect WiseStamp with Microsoft Exchange Online, see Server-Side for Microsoft Exchange.!/note!
What is a server-side solution?
WiseStamp's server-side solution is a deployment method that enables you to route your organization's emails through the WiseStamp SMTP server to automatically append signatures to your outgoing messages. WiseStamp's server-side solution ensures a consistent, professional signature for all emails, with no need for extra apps or add-ons. Just some email server configuration. It also ensures the newest signature versions are always used.
How do I benefit by using WiseStamp's server-side solution?
The server-side solution applies your WiseStamp signatures to email messages sent from any device and any mail client. You can therefore ensure consistency and professionalism across all outgoing emails, regardless of which email platform is used to compose them. Furthermore, the server-side solution does not require any additional apps, add-ons, or other changes to your WiseStamp environment. (Some configuration of your email server is necessary.)
Another advantage of the server-side solution is the certainty that the latest changes to your signatures is displayed, as the WiseStamp server-side host checks to ensure that the most recent signatures are added to outgoing messages.
Is the server-side solution secure?
Yes. WiseStamp's method is secure, without storing or reading your email content. Each account is processed in isolation for added security.
What's Hybrid Mode?
WiseStamp's Hybrid mode combines client-side and server-side solutions, offering flexibility. It only applies a server-side signature if a client-side signature is not detected, ensuring consistent delivery and security. It's available for various automatic installations.
Google Workspace server-side configuration is done in the following sequential phases:
- Configure your SPF records to help prevent your messages from being marked as spam,
- Add a new mail host to serve as the outbound connector to the WiseStamp server-side host
- Configure the SMTP relay service to set up routing for the inbound connector
- Configure the compliance rule to ensure that emails are routed to WiseStamp server-side host
- Perform a validity check by sending a test email and establishing the server connection
Additional steps for enhancing efficiency and security are presented in the Post configuration procedures section.
All procedures are performed from the Google Workspace Admin Console. To get started, log in and go to Apps > Google Workspace > Gmail.
In Google Workspace, there are several settings such as Routing, Default Routing, and Content Compliance that can influence the path of an email. Presently, within the Admin Console, Google does not provide a way to prioritize these rules; their processing sequence is determined by the order of their creation.
If you previously configured mail routing for another third-party service, you need to remove those settings. Afterward, recreate the Routing, Default Routing, and Content Compliance rules, particularly once the Content Compliance rule for WiseStamp is established.
1. Configuring your SPF record
For protection against spoofing and phishing and to help prevent your messages from being marked as spam, we recommend adding Sender Policy Framework (SPF) records to your domain.
For more information and instructions, see Setting Up SPF Records for Your WiseStamp Signature.
2. Add a new mail host
The first phase of the configuration involves adding a mail host. This host acts as an outbound connector to allow your emails to route to WiseStamp server-side signatures.
Before you begin, make sure you have access to the routing code provided by WiseStamp. You need it during the configuration.
To locate your unique code, log in to your WiseStamp account, go to the Connectors page and select Connect to Google Workspace. Your unique code is displayed in the popup window that opens.
- Under Settings for Gmail ( Go to Admin - Apps - Google workspace - Gmail - Setting for Gmail), expand the Hosts pane. Then, click Add Route.
- At the top of the popup, enter a name for the new host (e.g., WiseStamp).
- Configure the following settings:
- Under Specify email server, verify that Single host is selected from the dropdown list.
- In the field below, enter your routing code followed by .gw.smtp.wisestamp.net
For example: 2gg2mrqnl6nlx.gw.smtp.wisestamp.net
- Enter 25 as the port number for the host configuration.
- Under Options, select all checkboxes except for Perform MX lookup on host.
- At the bottom of the popup, click Save.
3. Configure the SMTP relay service
This phase involves configuring the routing for the inbound connector to receive the email back from the WiseStamp server.
- Under Settings for Gmail (Apps > Google Workspace > Gmail), expand the Routing pane.
Then, under SMTP relay service, click Add another rule /or Configure.
- At the top of the popup, enter a description for the service (e.g., Receive from WiseStamp).
- From the Allowed Senders list, select Only addresses in my domains.
- Configure authentication settings:
- Under Authentication, select Only accept mail from the specified IP addresses.
- Click Add.
- A popup appears. Perform the following:
- For each IP address, enter a distinct and meaningful description (e.g., WiseStampIP1, WiseStampIP2... up to WiseStampIP7).
- Individually input the following IP addresses:
- Select Enable.
- Click Save,
- Under Encryption, select Require TLS Encryption.
- Click Save.
4. Configure the compliance rule
The next stage of the configuration involves creating a compliance rule to ensure that your emails are routed to your WiseStamp server-side host.
Before you begin, make sure you have access to the routing code provided by WiseStamp. You need it during the configuration. To find your unique routing code, see the instructions above, Adding a new mail host.
- Under Settings for Gmail, expand the Compliance pane. Then, under Content Compliance, click Add another rule/or configure.
- At the top of the dialog that opens, enter a description for the rule (e.g., Route WiseStamp).
- Under Email messages to affect, select the following:
- Internal – Sending
- Under Expressions, verify that the If ALL of the following match the message option is selected. Then, click Add.
- In the popup that opens, select Advanced content match from the dropdown list.
- Configure the following settings:
- Location: Select Full headers.
- Match type: Select Not contains text.
- Content: Copy and paste the following: X-WiseStampHostedSignatures-MessageProcessed
- Click Save.
- Click Add again to add another expression. Under Expression: Select Advance content match and create a rule with the following settings:
- Location: Select Sender header.
- Match type: Set this to Not Matches regex.
- Content: Copy and paste the following text:
- Click Save.
- Click the If the above expressions match dropdown list and select Modify message.
- Under Headers, select Add custom headers and click Add.
- In the pane that opens, create a header with the following parameters:
- Header key ( X- ): Copy the following text: Wisestamphostedsignatures-Auth
- Header value ( : ): Paste the WiseStamp routing code here
- Click Save.
- Under Route, select Change route.
- Click the Normal Routing dropdown list and select the outbound connector route that you created earlier.
- Under Encryption (onward delivery only), select Require secure transport (TLS).
- Click Save.
5. Perform a validity check
After configuring the required connectors and rules, go back to WiseStamp to test your settings and complete the setup.
To test connections and set up your environment:
- Activate your user on WiseStamp.
- From your Gmail, send a test email to yourself or a colleague.
The WiseStamp signature should be displayed on the email received.
- From the Connectors page, click Connect.
!important!IMPORTANT: Make sure that several selected people in your organization have access to the login credentials for the Microsoft Exchange Admin Center. Quick access to the Admin Center is critical for rapid troubleshooting, if email delivery becomes interrupted.!/important!
!note!Once using the server-side solution (not in Hybrid mode), WiseStamp signatures will NOT appear during email composition or in emails in the Sent folder. !/note!
Post configuration procedures
Set up devices and apps
To help ensure maximum efficiency and security we recommend using the SMTP relay service to send emails from devices or apps. For complete details on how to set up your devices and apps to send email through Google Workspace, using the service you configured (Configuring the SMTP Relay Service), refer to the instructions in Option 1 of sending emails in Google Workspace Admin Help.
Manage domains in Google Workspace
When you want to include certain domains for the server-side solution, but not all domains related to your Google Workspace account, follow these steps to include specific domains in Google Workspace for WiseStamp:
- Sign in to your Google Admin Console using your administrator credentials.
- From the Home page, go to Apps > Google Workspace > Gmail > Compliance.
- In the Compliance section, locate Content Compliance.
- Locate the WiseStamp content compliance rule and click Edit.
- In the Edit settings, scroll down and click Show Options.
- Scroll down to C. Enveloper filter and check the Only affect specific envelope senders.
- You can now either specify email addresses or use existing groups.
- To apply your changes, Click Save.
You have now successfully set up WiseStamp's server-side solution to include specific domains in Google Workspace. Only emails from the specified domains are routed through WiseStamp SMTP and have signatures appended.
Troubleshooting server-side configuration issues
The following sections provide guidelines to help handle issues that may occur with server-side configuration.
Server-side connection errors
Sometimes connection errors can prevent your emails from being sent or your signature from appearing in your emails. In such cases, disconnecting and reconnecting your WiseStamp account can resolve the issue.
To disconnect from the server:
- Open your WiseStamp account.
- On the left panel, click Connectors.
- Click Manage on the Connectors page.
- At the upper right corner of the page, click Disconnect.
- Follow the on-screen instructions to confirm the disconnection and complete the process.
- Go to the Connectors page.
- Click the Connect dropdown list and select Google Workspace.
- Follow the on-screen instructions to complete the connection process.
Two WiseStamp signatures are displayed
If you see two signatures at the bottom of your email, it's likely that you have a manually installed signature (copy/paste). WiseStamp cannot recognize manually installed signatures, so they cannot be automatically removed or overwritten. To avoid having duplicate signatures, simply reinstall or remove your copy/paste signature.
Mails not being sent
In rare circumstances, you may encounter a critical issue where your emails are not going through. In such cases, you may need to disable the compliance rule in the Google Workspace Admin Console until further investigation with WiseStamp support team. Disabling the rule ensures that your emails bypass WiseStamp's servers, allowing them to be delivered without any interference.
To disable the compliance rule:
- From the Google Workspace Admin Console, go to Apps > Google Workspace > Settings for Gmail > Compliance.
- Under Content Compliance, in the row of the rule you created for WiseStamp, click Disable.
Please note that as long as the rule is disabled, all emails will bypass WiseStamp's server, even those that may have been previously routed through it. You may need to re-enable the rule at a later time to resume signature deployment.