The server-side setting is designed for Office 365 to catch outgoing email signatures in the mail flow and apply the user’s email signature from your Xink account.
The emails are caught by the Xink server in Windows Azure (same data centers as Office 365) just before they are delivered by Office 365. Once the signature replacement has taken place, the email is delivered back to your Office 365 tenant, which will then be responsible for sending the mail.
Xink is intelligent in the sense that it analyzes emails for known signature patterns with the purpose to find existing signature in outgoing message and replace it with the Xink signature. If known reply/forward pattern is found, it uses Reply signature from Xink, otherwise – Default signature is applied.
Xink Azure server will never deliver any emails, only the signature placement will take place, and hence the customer's Office 365 account will be responsible for the actual delivery. You can be sure that your full branding initiatives are in place and visible, no matter which app, device, or where you sent the email from. Xink Server-Side will work pretty much just out-of-the-box.
When to use Server-Side to get email signature applied?
Server-side is used to apply an email signature when an email is sent from mobile devices.
In addition, the 'Fully server-side' setting', is used when you prefer that all email clients get a signature are applied at the server (incl. Outlook on Windows/Mac/Browser - Not only for mobile devices).
Emails sent from mobile devices will get an email signature applied instead of showing e.g. 'Sent from my iPhone'.
Infographic > Xink Rerouting for Office 365.
Learn more > FAQ for Office 365.
Best practices > Server-Side
All Xink mailservers are located in Azure datacenters, each one in the same datacenter as Xink application server, e.g. United States, European Union, etc. All communications between Office 365 server and Xink servers are encrypted (TLS/SSL).
Xink mail servers do not deliver emails to the final recipients. After processing the messages, they are returned back to Office 365 for further delivery in a regular way.
Xink mail servers handles a very dense stream of emails and can cause delivery delays. Typical delay is about 10 seconds, it can jump up to 30 minutes occasionally. Each signature is cached by the ReRouter for twenty minutes (actual number will change, but the cache will exist always). It means that all changes in a signature (text, field values, anything) propagates to the ReRouter within this period and will not be visible immediately.
How to configure Server-Side using the Web Console?
Web Console is a simple tool to configure Xink server-side.
Technically it is a proxy between Office 365 PowerShell console and the user. Xink web server creates PowerShell remote session and interacts with Office 365 server, then it shows the results back to the user in a form of console-like output.
Alternatively, configure Server-Side via PowerShell without entering Office 365 admin credentials (IT Pro).
Open 'Preferences' menu, select 'Integration' tab.
Click 'Office 365 (Server-Side)' and you will find the 'Open Console' button.
When you click 'Open Console', the popup window appears and you connect using Office 365 admin credentials:
Xink will not save the credential so feel free to enter your Office 365 admin credentials to create remote session between Xink web server and Office 365.
Then exit the window above.
NEXT - Wait for 15-30 minutes and notice the list of discovered domain map.
Apply the email signature when the email is sent (Fully server-side)
Mobile email signatures are always applied at the server. But you can also choose to select server-side for all other email clients (Outlook, Apple Mail, Outlook on the web etc.). Then all emails will get their email signature applied at the server.
The email signature is not visible as the email is composed. Learn more.
Please consult Xink support team before applying 'Fully server-side' setting for recommendations and Best Practices.