SMTP passwords can be set per private address. This allows you to keep your API key separate from your SMTP passwords. This password can be set by selecting “Manage Email Addresses” in the Dashboard and selecting POP/SMTP next to the email address you want to define a SMTP password for.
Email can be forwarded using websockets, webhooks, slack, and catchall. The way email is forwarded has been changed for consistency. Reserved addresses, which are part of a catchall domain, will now be the inbox email is saved to. Catchall forwarding will still take place on websockets, webhooks, and slack webhooks.
Examples:
The Unified Inbox provides a way to see all of your private addresses at once. We added several enhancements to make the Unified Inbox the place you to manage all your Mailsac addresses.
The required TXT and MX records for setting up a BYODomain (Bring Your Own) are now compatible with most GUI DNS editors.
The current origin is referred by “example.com.”, which is RFC 1035 compliant. Notes on the page have been made showing that some GUI editors (such as Namecheap) require the use of a “@” in place of the current origin.
Outbound mail (out.mailsac.com, port 587) now supports the following auth methods in a wider variety of scenarios:
– AUTH LOGIN
– AUTH PLAIN
Until the latest release, in some instances the AUTH LOGIN command was not completing the authentication process.
The robustness of our SMTP server has been improved by providing better response codes.
Incoming SMTP connections will be queued based on system load. The connection will stay open while waiting for system resources. If the SMTP connection cannot be completed in a reasonable period of time the server will issue a response code of 421. This situation may be encountered while sending a large amount of email from a specific server or to Mailsac hosted email address.
We offer custom domains to get around throttling, in all but the heaviest DDOS scenarios. Also, Enterprise customers can visit mailsac.com/enterprise to view higher performance or dedicated deployments.
An updated was released which allows Mailsac to receive messages lacking a TO field, as long as there is a CC or BCC.
The status code for reserving an address on the API was returning a 302 in some situations, while the documentation said it was a 200. This has been resolved. This endpoint for reserving an address will also return the address object.
When deleting a private address, the API used to return { "ok": true } with a 200 status code. Now the API will return a 200 a copy of the address object which was deleted.
Mailsac has added a new spamminess indicator in the API.
New messages will have a spam property that’s a score between 0.0 and 1.0. 1.0 indicates a high likelihood of spam. The system will get smarter over time.
The main component of spam detection is a time tested approach called Naive Bayes Classifier. The core of the code is open source at github.com/mailsac/spam-classifier, though a little special sauce is applied, too. This classifier library is ready to use and includes a simple API server and a terminal training tool.
In the works are additional spam classification projects using three different deep learning techniques: random forest, a long short term neural network, and a combination recurrent network + liquid state machine with spike dependent plasticity. The goal is to open source the useful pieces of the coming spam classifiers.