New Email Infrastructure
Lately, email deliverability has become one of the biggest pains in Invoicebus, so we had to change the way we handle emails.
It’s one thing to send email but another thing to actually deliver email. Given the fact that more than 90% of all daily emails are spam, Email Service Providers are constantly changing their policies. A small deviation from the ESP rules can easily throw completely legitimate email into the spam folder.
As the email is core functionality in Invoicebus, we have to be on top of the game to ensure your emails always land in the right inbox.
In the past few years, many popular ESPs like Yahoo, Hotmail, and others, have imposed extra restrictions to lower the spam they get. New types of email authentication and verification like DMARC policies were set in place. These rules started to cause email deliverability issues in Invoicebus.
Few years ago, Invoicebus was sending emails on behalf of our customers by specifying their original email address in the “From” field. This was working well until many ESPs decided to adopt the DMARC policy. Simply put, DMARC policy doesn’t permit the address in the “From” field to be on a different domain than the sending server domain:
To solve this, we implemented a small hack – instead of putting the customer’s original email address into the “From” field we specified a permanent email address registered under our domain (firstname.lastname@example.org). As the customer’s original email address was specified into the “Reply-To” field, all email replies would go to the right inbox without a problem.
This was working quite well until we started receiving complaints from customers that some of their emails are mistakenly marked as spam.
The problem became even more serious when a few customers reported that their emails are not delivered at all. We weren’t sure what’s happening because Invoicebus was receiving delivery confirmations from the remote servers, yet the emails were somehow dropped by their internal mechanisms. After an exhaustive investigation, we found out that this was caused by a new spam rule introduced by the popular spam software SpamAssasin. The rule requires the addresses specified into the “From” and “Reply-To” field to be on the same domain as the sending server domain. Who would have thought? Just solved one problem another one appears.
There was no quick solution nor any possible workarounds to this. We had to completely migrate our email infrastructure and the way Invoicebus handles emails. This resulted in developing two new features for handling emails:
- dedicated Invoicebus mailbox for each customer (for example email@example.com)
- optional setting that allows specifying custom SMTP server
1. Dedicated Invoicebus mailbox (default option)
Note: All customers will receive a dedicated Invoicebus mailbox automatically.
Invoicebus will generate a unique email address from your original address and set it as a default “from/reply-to” address for all outgoing emails you send. For example, if your login email is firstname.lastname@example.org your Invoicebus email will be email@example.com. The username before the @mail.invoicebus.com part is required, and you can change it to whatever you like (if available).
This ensures any messages sent via Invoicebus to pass even the most restrictive spam filters.
Your clients can also directly reply to any email you send. Invoicebus catches the replies and automatically forward them to your original email address. If the conversation relates to a document, the entire message thread will be saved under the document’s activity history as an incoming email (depends on the plan). This way you can keep all your important conversations in one central place (see image below).
2. Custom SMTP email server
Specifying a custom SMTP (depends on your plan) gives you the flexibility to send emails via your own email server/mailbox. This way your clients will get emails from your original email address (or address on your domain), rather than the one assigned by Invoicebus.
Please note that if you specify custom SMTP server, Invoicebus won’t be able to track any email events such as delivered, bounced and opened (“opened” is a new event that shows when an email is opened by the client. This is different from “document opened”, which fires only when an online document is opened).
Last but not least is the customization of your Display (From) Name, where you can specify the name your client sees when they get an email from you (see image below). If you leave this empty it will default to the last saved company name.
The new infrastructure should significantly improve the email deliverability. It should also give you a better insight of what’s going on with your emails almost in real-time. The easiest way to keep track of your emails is to take a look at the dashboard and see the status of each email, reminder, and thank-you note. Here’s a quick reference: