Send and Receive Emails in SIMISE with an Email Server¶
If you are a user of SIMISE Online or SIMISE.sh…¶
You have nothing to do! SIMISE sets up its own mail servers for your database. Outgoing and incoming emails work out-of-the-box!
Unless you plan to send large batches of mass mailing that could require the use of an external mail server, simply enjoy your new SIMISE database.
Scope of this documentation¶
If no one in your company is used to manage email servers, we strongly recommend that you opt for those SIMISE hosting solutions. 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 some useful information on how to integrate your own email solution with SIMISE.
Office 365 email servers don’t easily allow to send external emails from hosts like SIMISE. Refer to Microsoft’s documentation to make it work.
How to manage outbound messages¶
As a system admin, go toand 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.
If you get a
[AUTHENTICATIONFAILED] Invalid credentials (Failure) warning when you Test
Connection on a Gmail address, activate the Less secure app access option. A direct link can
be accessed here.
In addition to that, enable the IMAP setting on your Gmail account.
Can I use an Office 365 server¶
You can use an Office 365 server if you run SIMISE on-premise. Office 365 SMTP relays are not compatible with SIMISE Online unless you configure SIMISE to force the outgoing “From” address .
Please refer to Microsoft’s documentation to configure a SMTP relay for your SIMISE’s IP address.
How to use a G Suite server¶
You can use an G Suite server for any SIMISE hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in Google documentation.
Please note that port 25 is blocked for security reasons on our SaaS and SIMISE.sh platform. Try using 465, 587, or 2525.
Use a default “From” email address¶
Sometimes, an email’s “From” (outgoing) address can belong to a different domain, and that can be a problem.
For example, if a customer with address email@example.com responds to a message, SIMISE will try to redistribute that same email to other subscribers in the thread. But if the domain customer.example.com forbids that kind of usage for security, the SIMISE’s redistributed email would get rejected by some recipients’ mail servers.
To avoid those kind of problems, you should make sure all emails use a “From” address from your authorized domain.
If your MTA supports SRS (Sender Rewriting Scheme), you can enable it to handle these situations. However, that is more complex and requires more technical knowledge that is not meant to be covered by this documentation.
Instead, you can also configure SIMISE to do something similar by itself:
Set your domain name in the General Settings.
In developer mode, go to.
Add one system parameter from these:
If you want all your outgoing messages to use the same “From” address, use the key
mail.force.smtp.fromand set that address as value (such as
If you want to keep the original “From” address for emails that use your same domain, but change it for emails that use a different domain, use the key
mail.dynamic.smtp.fromand set as value the email address that should be used in those cases (such as
How to manage inbound messages¶
SIMISE relies on generic email aliases to fetch incoming messages.
Reply messages of messages sent from SIMISE 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 SIMISE. This is especially used in SIMISE Email Marketing to opt-out invalid recipients.
Original messages: Several business objects have their own alias to create new records in SIMISE from incoming emails:
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 SIMISE 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 SIMISE on-premise, create an Incoming Mail Server in SIMISE 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 SIMISE Online or SIMISE.sh, We do recommend to redirect incoming messages to SIMISE’s domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, SIMISE Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to SIMISE’s domain name in your email server (e.g. firstname.lastname@example.org to catchall@mycompany.SIMISE.com).
- All the aliases are customizable in SIMISE.
Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode.
Then go toto customize the aliases (mail.catchall.alias & * mail.bounce.alias*).
By default inbound messages are fetched every 5 minutes in SIMISE on-premise. You can change this value in developer mode. Go to and look for Mail: Fetchmail Service.
Set up different dedicated servers for transactional and mass mails¶
SIMISE is subject to a daily email limit to prevent abuse. However, if needed, you can use a separate Mail Transfer Agent (MTA) servers for transactional e-mails and mass mailings. Example: use SIMISE’s own mail server for transactional e-mails, and Sendgrid, Amazon SES, or Mailgun for mass mailings. Another alternative is to use Postmark for transactional e-mails, and Amazon SES or Sendgrid for mass mailings.
A default outgoing email server is already configured. You should not create an alternative one unless you want to use a specific external outgoing email server for technical reasons.
To do this, you should first activate the developer mode and then go to e-mail servers. There you have to create two e-mail MTA server settings. One for transactional e-mails and one for mass mail servers. Be sure to mark the priority of transactional e-mail servers as low as the mass email servers.
Now, go toand enable Dedicated Server. With these settings, SIMISE uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, you have to set your domain’s Sender Policy Framework (SPF) records to include both transactional and mass mail servers. If your server resides with xxxx.SIMISE.com, the available options are Sendinblue and Mailchimp, as your e-mails would be originated from the xxxx.SIMISE.com domain.