Configuring sender accounts

In order to send emails from Synerise, you must create a sender account. For starters, there is always a default sender account that is suitable for sending an email for several recipients for test purposes.

WARNING: We strongly recommend using the default sender account only for testing.

The process requires the following actions:

  1. Outside Synerise:
    1. Create an email account within a domain.
    2. Add DNS entries.
    3. If you don’t have your own SMTP, decide which one to choose (Synerise offers two options).
      Tip: Simple Mail Transfer Protocol (SMTP) is responsible for moving your emails on and across IP networks that are typically only used for sending messages to a mail server for relaying. It’s an internet standard for email transmission and it works closely with Mail Transfer Agent to send your emails to the right email inboxes.
  2. Inside Synerise application:
    1. Select SMTP provider.
    2. Configure SMTP provider.
    3. Create a sender account.

Setting up and email account


Create an inbox within any domain.

Add DNS to your domain


It is your responsibility to make sure the domain you use is safe and protected by adding the DNS entries which ensure satisfying email deliverability.

WHY? These entries allow mail clients to verify that you are the real sender of the message. Messages with those headers may be blocked or treated as spam. This is a widely accepted standard.

Tip:

Before moving on to the further parts of the article, get to know the terms header from and envelope from. Header from (1) is an email address from which an email is sent, whereas envelope from (2) indicates a domain from which the email is sent (it can be a domain of a bulk mailing vendor or third party affiliates).

Examples of header from and envelope from in a Gmail inbox
Examples of header from and envelope from in a Gmail inbox

There are three types of entries which must be added in the given order:

SPF

Sender Policy Framework (SPF) must be added regardless of using a shared or your own SMTP. It is considered to be the standard of authorization. The recipient’s mail server checks whether the sender’s IP is authorized to send emails with a domain in envelope from. The list of the allowed IP addresses is included in the domain’s DNS record.

For users of EmailLabs (sub-account of Synerise's main account)

If you are not sure about the region your EmailLabs sub-account belongs to, contact the Synerise support. Then, follow the procedure with regard to SPF configuration at the links below:

DKIM

Domain Keys Identified Mail (DKIM) is:

An element of the email is encrypted with a private key. The other key, which is public, is contained within the domain an email is sent from. The recipient’s mail server matches the public key with the private one. If the keys match, the email is verified as genuine.

For users of EmailLabs (sub-account of Synerise's main account)

The links below redirect to the instructions on adding the standard DKIM keys. If you want to comply with Gmail and Yahoo! authorization restrictions, add the standard keys and generate custom DKIM for your domain.

If you are not sure about the region your EmailLabs sub-account belongs to, contact the Synerise support. Then, follow the procedure with regard to DKIM configuration at the links below:

Compliance with Gmail and Yahoo! authorization restrictions

From February 2024, Gmail and Yahoo will implement new authentication requirements that enforce usage of:

  • standard DKIM keys
  • custom DKIM for your domain
  • reinforced DMARC.

How to generate custom DKIM for your domain?

  • You can generate it on your provider’s account.
  • If you use EmailLabs as an SMTP provider which isn’t a sub-account of Synerise’s main account, you can generate keys in Admin > Sender Authorization
  • If you have a sub-account of Synerise’s main account in EmailLabs, to generate the keys, contact Synerise support.

I only have standard DKIM keys but I want to comply with Yahoo! and Gmail restrictions

  • If you use a provider other than EmailLabs: Consult the documentation of your SMTP provider to check how to generate custom DKIM for your domain.
  • If you use EmailLabs: generate custom DKIM keys in Admin > Sender Authorization, add the key and the standard keys to your DNS.
  • If you use EmailLabs (a sub-account of Synerise’s main account), contact Synerise support.

DMARC

Domain-based Message Authentication (DMARC) is recommended when you use your own SMTP. Based on the two previous entries (at least one of them must exist), it verifies the domain. To be compliant with Gmail and Yahoo! authorization standards as of February, 2024, it is necessary to implement DMARC.

For users of EmailLabs (sub-account of Synerise's main account)

If you are not sure about the region your EmailLabs sub-account belongs to, contact the Synerise support. Then, follow the procedure with regard to DMARC configuration at the links below:

Important: After adding DNS entries, you must wait at least 24 hours before sending emails because the processing of these entries takes time. Depending on your provider, this may take up to 72 hours.

Select SMTP providers in Synerise


Synerise offers the following SMTP options:

  1. Synerise SMTP email provider
    • No further requirements
    • Recommended only for testing purposes.
    • Not recommended for the production environment because:
      • It is shared with other users - if a user who uses this SMTP is denylisted, it may also affect you.
      • No possibility of retrieving details of single emails
      • The structure of IP addresses is not prepared for sending regular emails
  2. EmailLabs (as a sub-account of Synerise’s main account)
    Synerise requests a paid sub-account on behalf of the user (contact Synerise support before). The infrastructure of such sub-account is customized to meet the user’s demands. It involves gradual preparation of IP addresses for sending large number of emails, otherwise sending many messages in a short time from the same IP may trigger anti-spam mechanisms.
    Important: You can create an account in EmailLabs independently from Synerise. Then, you have access to your hosting provider panel. In the other case (as a sub-account), you don’t have access to it.
    • Prepare the following data for Synerise:
      • shipping address (domain),
      • maximum number of emails you send in a single delivery,
      • maximum number of emails you send in one month,
      • the structure of recipients domains (the percentage distribution of the email domains of recipients, for example gmail.com, yahoo.com, mail.com, and so on).
  3. Integration with Freshmail
    If you have an account in Freshmail, you can integrate it with Synerise by entering the API key.
  4. Integration with ExpertSender If you have an account in Expert, you can integrate it with Synerise by entering the API key.
  5. Integration with SendGrid If you have an account in SendGrid, you can integrate it with Synerise by selecting a security level, port number, and entering the API key.

Configure SMTP in Synerise


  1. Go to Settings icon Settings > Apps & Services.

  2. Select the procedure for the SMTP variant you currently use:

    For users who use EmailLabs or their own SMTP

    1. Click SMTP Servers.
      Result: The list of fields appears.
    2. On the bottom of the list, click Add new account.
    3. In the My server field, enter the name of the server (it will be visible only on the list above the fields and on the list of SMTP providers while selecting the Mail provider in Email Accounts section).
    4. In the Host field, enter the address of the host.
    5. From the Security dropdown list, select the security level.
      • If you use an Email Labs sub-account, select TSL and enter 587 as the port number.
      • If you use any other provider, select SSL.
    6. Fill in the fields: Port number, User name, and Password with data obtained in one of the following ways:
      • If you use an Email Labs sub-account, contact Synerise Support.
      • If you use any other provider, find the data in the provider’s administration panel. For details, refer to the provider’s documentation.
    7. Proceed to step 1 in the Configure a sender account section.

    For users who use Synerise SMTP

    If you use the Synerise SMTP solution (in the application called as Synerise mail provider), skip this part and proceed straight to Configure a sender account section.

    For users who use ExpertSender or Freshmail

    Important: Freshmail integration will be completed soon.
    1. On the list of Integrations, click the ExpertSender sender integration.
      Result: The API Key field appears.
    2. Enter the API key which you can find on your ExpertSender account.
    3. Switch the toggle on.
    4. Click Save.
    5. Proceed to step 1 in the Configure a sender account section.

    For users who use SendGrid

    1. On the list of Integrations, click the SendGrid sender integration.
      Result: The form expands.
    2. From the Security level dropdown list, select one of the following options:
      • No security
      • SSL
      • TSL
    3. In the Port number field, enter the number of the port you will use. If you’re not sure which port you use, refer to the SendGrid documentation.
    4. In the API key field, enter the API key.
      To learn about creating an API key in SendGrid, click here.
    5. Proceed to step 1 in the Configure a sender account section.

Configure a sender account


A blank sender account form
A blank sender account form
  1. Go to Settings icon Settings > Email Accounts.
  2. Click Add account.
  3. In the Account name field, enter the name of the account (it will be visible only on the list of sending accounts).
  4. In the From (email) field, enter the email address from which emails are sent.
  5. In the From (name) field, enter the name of the sender that is displayed in the recipient’s inbox.
  6. In the Reply to (email) field, enter the email address to which responses to newsletters will be delivered.
  7. In the Reply to (display name) field, enter the name of the sender of email address to which responses are delivered.
  8. Optionally, in the Resignation link field, enter the resignation link. If you enter a URL here, a visit to this website by a customer results in changing the status of email marketing agreement to opt-out.
    Important: This field is optional. While creating email templates, you will be required to add a resignation link.
  9. In the Mail provider section, select one of the three options:
    • To use the default Synerise email provider, select Send using Synerise mail provider.
    • To use your own SMTP server (including Email Labs sub-account), select Send using your own SMTP server.
      • From the Choose your SMTP server dropdown, select the SMTP server.
    • To use ExpertSender as a email provider, select Send using the ExpertSender server.
  10. Confirm the settings by clicking Save.
    Result: A confirmation email is sent to the email address in the From(email) field.

Confirm the sender account


Go to your inbox and click the link in the confirmation email.
Result: The account is confirmed and can send messages. On the list of accounts, its status changes from Awaiting confirmation to Confirmed.

Track hardbounces and softbounces


You can receive information about the bounces in the form of events. Based on these events, you can prepare statistics or exclude the email addresses from which you received a bounce message by defining conditions in a segmentation.

Example segmentation that excludes email addresses with all kind of bounces
Example segmentation that excludes email addresses with all kind of bounces

The list of events:

Event name Description
newsletter.hardbounce The event is generated when the email is not delivered because an email address is invalid or the recipient blocked receiving emails.
newsletter.softbounce The event is generated when the email is not delivered due to an overloaded inbox, server error, or email size.
newsletter.spambounce The event is generated when the recipient’s email server recognized the message as potential spam. The email is rejected and not saved, even in the spam folder.
newsletter.dropped The event is generated when the email is not delivered due to putting the email address from which the email is sent on the black list.

To receive these events, you must perform the actions described below:

For users who use Synerise SMTP

If you use Synerise SMTP, you don’t have to do anything.

For users who use Emaillabs SMTP

Settings at Emaillabs' panel
Settings at Emaillabs' panel
  1. Go to the Emaillabs panel.
  2. Go to Event API settings
  3. Configure the form as presented in the screen above.
    1. Status set to on.
    2. Protocol set to https.
    3. Set Application URL: https://{SYNERISE_API_BASE_PATH}/webhook-handler/emaillabs
    4. webhook_basicAuth set to off.
    5. webhook_perSmtp set to off.
  4. Contact Synerise support and provide the following information:
    • API Key
    • Secret key
    • The name of the Emaillabs panel
  5. After the configuration, perform the test in the Emaillabs panel. If the configuration is correct, the test returns the success message.

For users who use SendGrid

After performing the procedure below, Synerise will receive events included in the table below, except newsletter.softbounce.

  1. In your SendGrid account, perform the Enable the Signed Event Webhook procedure.
  2. Provide the key to the Synerise support.
  3. In your SendGrid account, proceed to Settings > Mail Settings > Event webhook.
  4. In the HTTP POST URL field, enter https://{SYNERISE_API_BASE_PATH}/webhook-handler/sendgrid. Depending on the cloud where your workspace is hosted, replace {SYNERISE_API_BASE_PATH} with:
    • https://api.synerise.com for Microsoft Azure
    • https://api.geb.synerise.com for Google Cloud Platform
  5. Select Event notifications.
  6. Select dropped, bounced, and spam reports. These are the only possible options.
  7. Save the settings.

Only for users who use other providers

Check in the provider’s documentation, as the procedure and credentials required may differ for each provider.

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker