Configuring email transfer settings
page last edited on 26 March 2018
Email transfer configuration is the most important part of the notifications maintenance as whether your emails will be delivered and read by the end users (your customers) will completely depend on it.
First of all you’ll need to set the default FROM email address for your store. To set it go to the E-Mail transfer settings tab of the Store setup -> Email notifications page.
Use the ‘Which email to use for the FROM field’ drop-down to choose the email. Your options are as follows:
| Email from the Contact information section |If you choose this option the default FROM email(s) for your store will be the one(s) that are specified for Contacts| | Sender email as identified by the server |If you choose this option the default FROM email will be the one defined by your mail server| | Email address specified below | If you shoose this option you can define any FROM email address you like better | Submit the changes after the email is set.
Once a FROM email is defined you need to test it using the ‘Test email configuration’ section in the bottom on the page.
To learn how to test your email transfer settings please refer to the article - Testing your email transfer settings with mail-tester.com.
If you want to send email notifications via an email server, different from the one your store is installed at, enable the ‘Use SMTP server’ option. Once enabled you’ll see the fields that you can fill in to configure the option.
You’ll need to specify the SMTP server that should be used for the email notificatons. If necessary configure the background job processing on your server to send emails asynchronously, that will improve the website performance. Then define your username and password for the SMTP server and set the ‘Use authentication’ and ‘Secure connection’ options. When everything is done, submit the changes.
Besides SMTP you can use Mandrill as a default mailer for all the transactional emails.
Help make this document better
This guide, as well as the rest of our docs, are open-source and available on GitHub.