This document is mainly dedicated to Vorlik on-premise users who don’t benefit from an out-of-the-box solution to send and receive emails in Vorlik, unlike in Vorlik Online & Vorlik.sh.
If no one in your company is used to manage email servers, we strongly recommend that you opt for such convenient Vorlik hosting solutions. Indeed their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server’s reputation yourself.
You will find here below some useful information to do so by integrating your own email solution with Vorlik.
How to manage outbound messages
As a system admin, go to
and check External Email Servers. Then, click Outgoing Mail Servers to create one and reference the SMTP data of your email server. Once all the information has been filled out, click on Test Connection.Here is a typical configuration for a G Suite server.
Then set your email domain name in the General Settings.
Can I use an Office 365 server
You can use an Office 365 server if you run Vorlik on-premise. Office 365 SMTP relays are not compatible with Vorlik Online.
Please refer to Microsoft’s documentation to configure a SMTP relay for your Vorlik’s IP address.
How to use a G Suite server
You can use an G Suite server for any Vorlik hosting type. To do so you need to enable a SMTP relay and to allow Any addresses in the Allowed senders section. The configuration steps are explained in Google documentation.
Be SPF-compliant
In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don’t forget to authorize Vorlik as a sending host in your domain name settings. Here is the configuration for Vorlik Online:
- If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.vorlikhq.com ~all
- In case a SPF TXT record is already set, add “include:_spf.vorlikhq.com”. e.g. for a domain name that sends emails via Vorlik Online and via G Suite it could be: v=spf1 include:_spf.vorlikhq.com include:_spf.google.com ~all
Find here the exact procedure to create or modify TXT records in your own domain registrar.
Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly.
Note
Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Vorlik.
Allow DKIM
You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Vorlik Online & Vorlik.sh, you should add a DNS “vorlikhq._domainkey” CNAME record to “vorlikhq._domainkey.vorlikhq.com”. For example, for “foo.com” they should have a record “vorlikhq._domainkey.foo.com” that is a CNAME with the value “vorlikhq._domainkey.vorlikhq.com”.
How to manage inbound messages
Vorlik relies on generic email aliases to fetch incoming messages.
- Reply messages of messages sent from Vorlik are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (catchall@).
- Bounced messages are routed to bounce@ in order to track them in Vorlik. This is especially used in Vorlik Email Marketing to opt-out invalid recipients.
Original messages: Several business objects have their own alias to create new records in Vorlik from incoming emails:
- Sales Channel (to create Leads or Opportunities in Vorlik CRM),
- Support Channel (to create Tickets in Vorlik Helpdesk),
- Projects (to create new Tasks in Vorlik Project),
- Job Positions (to create Applicants in Vorlik Recruitment),
- etc.
Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Vorlik alias in your mail server.
- Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.).
Set your domain name in the General Settings.
- If you use Vorlik on-premise, create an Incoming Mail Server in Vorlik for each alias. You can do it from the General Settings as well. Fill out the form according to your email provider’s settings. Leave the Actions to Perform on Incoming Mails blank. Once all the information has been filled out, click on TEST & CONFIRM.
- If you use Vorlik Online or Vorlik.sh, We do recommend to redirect incoming messages to Vorlik’s domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Vorlik Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Vorlik’s domain name in your email server (e.g. [email protected] to [email protected]).
Tip
All the aliases are customizable in Vorlik. Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode from the Settings Dashboard.
Then refresh your screen and go to
to customize the aliases (mail.catchall.alias & * mail.bounce.alias*).Note
By default inbound messages are fetched every 5 minutes in Vorlik on-premise. You can change this value in developer mode. Go to
and look for Mail: Fetchmail Service.