In Erply, it is possible to send certain types of documents (receipts, invoices, purchase orders) to customers and suppliers by email.
When an email is sent from Erply, the “From” field in the message is set to an “erply.io” or “erplyinfo.com” address:
From: Company ABC <1234@us.erply.io>
Your actual email address appears in the "Reply-To" header:
Reply-To: Company ABC <alice@example.com>
Generally, this is not an issue. Recipients can still see your actual email address, and if they hit the "Reply" button, the response will arrive in your mailbox.
This might seem an unusual way to construct an email, but Erply is following global standards on email security and trustworthiness. In emails, "sender spoofing" is nowadays strongly discouraged. In a message, the “From:” address must match the actual sending server, and there is a standard called DKIM (DomainKeys-Identified Mail) to prove it with a digital signature. When receiving mail, servers increasingly check whether a message has this signature.
To set up DKIM, domain owners generate a public key-private key pair, publish the public key as a DNS record and configure the outgoing mail server to digitally sign each message with the private key. Receivers can verify the signature.
Messages not using these techniques might be penalized with a higher spam score.
EMS
EMS is Erply's email routing service. Emails sent by EMS have a sender address ending in erply.io.
Some accounts might still be using an older setup, where the emails have a sender address ending in erplyinfo.com.
Additionally, the use of EMS is indicated by account configuration parameter use_ems_service = 1.
Sender Address Customization
At this time, Erply does not offer any services for setting up DKIM signatures for other domains. Therefore, it is not possible to configure the domain of the sender address.
However, it is possible to customize the part of the address before the “@”. This does not change anything in how the emails are routed and received, but it might give an additional bit of reassurance to receivers that the email has indeed been sent by your company. Instead of:
12345@us.erply.iowe can change it to:
yourcompany@us.erply.ioPlease get in touch with customer support to configure it.
Sender Address Customization in the Past
In the older setup, it was possible to use a sender address with a custom domain name — provided that the domain owner disabled both DKIM and DMARC.
This feature is generally not available any more. It was not a good solution, because turning off DKIM affects all email sent from your domain, not only the receipts emailed by Erply. Messages sent from Outlook might have delivery problems as well, due to missing DKIM signatures.
These were the setup requirements for that feature:
- The "From:" address had to be one fixed email address, eg. "info@example.com".
- You had to be the owner of the domain: third-party email providers like @aol.com, @hotmail.com, @gmail.com were not supported.
- The following DNS SPF record was required:
"v=spf1 a:mx1-out.erplyinfo.com a:mx2-out.erplyinfo.com ~all" - DKIM and DMARC had to be disabled.
- The desired email address had to be defined as a configuration parameter:
from_email_address = info@example.com