The Recent Activity Log now includes detailed sender and delivery information for outbound email. This empowers customers to diagnose sending issues.
Successful Email Log Entry
The screenshot below shows a successful email delivery sent from email@example.com to firstname.lastname@example.org. The email message id, number of delivery attempts, rejection status, and time stamps are included in the logs
Failed Email Log Entry
The screenshot below shows a failed email delivery from email@example.com. The message id, number of attempts, timestamp, and error message are provided.
This error message indicates that the recipients domain no-where-no-where-no-where.info does not exist.
Custom domains and Private Addresses have been great for quality assurance teams to conduct end to end automated testing of email. But sometimes interacting with an REST API can be a lot of overhead for non-repeating tasks. API Credentials can now be used to login to the website.
All private addresses and custom domains associated with the primary account will be visible from the website for API users. The permissions for API users are the same as API keys.
Quality assurance teams often share credentials of test accounts for the web application they are testing. These test accounts might to be associated with an email provisioned by their IT department or the QA tester’s personal email. Mailsac private domains allow the test accounts to be created in an an environment all members of the QA team have access to.
This feature allows teams to work together in the Mailsac platform. There is no longer a need to for each person to have their own Mailsac account. A named API Key can be created for each person. That API key can be used to interact with the REST API and the website. As a result, password resets and transaction emails sent to a Mailsac private domain can be accessed by any member of the QA team.
“Internally we have used Mailsac for collaboration. Being able to share a private address or domain allows my team members to see exactly what I am seeing. This feature allows our customers to do the same with their own private domains and addresses” Michael Mayer – Member – Forking Software LLC
We will be rolling this feature out to our Business and Enterprise Plans in the next couple weeks. If you have an immediate need for this feature we can enable it on your account. Contact firstname.lastname@example.org to get early access to this feature on you Business or Enterprise Plan.
We’ve listened to your feedback. This week we released new functionality to delete all the messages in an inbox.
Purging an inbox can be accomplished in two ways:
programmatically, via the REST API DELETE /api/addresses/:email/messages route
by clicking the new “Purge Inbox” button
Here’s an example of clicking the Purge Inbox button, instantly recycling over 80 messages:
Why were all the messages not deleted?
Starred messages (savedBy in the REST API) will not be purged.
We recommend un-starring those messages first, then purging the inbox, if you want to completely clear the inbox. Or, use the existing single-message deletion feature will allow you to delete a starred message. There is a button for deleting messages on the inbox page. The REST API route to delete a single message is DELETE /api/addresses/:email/messages/:messageId.