A fix was released to address case sensitivity in the Email Messages API.
The API now treats GET addresses/[email protected]/messages
the same as GET addresses/[email protected]/messages
.
A fix was released to address case sensitivity in the Email Messages API.
The API now treats GET addresses/[email protected]/messages
the same as GET addresses/[email protected]/messages
.
Our team will be performing database maintenance on Saturday May 22nd, 2021 from 14:00 – 16:00 UTC. During this period, API, email, and website services may be unavailable, intermittent, or slow to respond.
Updates during and on completion of the maintenance will be provided in this blog post.
UPDATE
All maintenance has been completed and the team is standing by monitoring performance. No further impact is expected.
My garden has been planted and the days are getting warmer. Next task, cleaning up. Mailsac won’t help you organize you garage or avoid the accumulation of clutter. But it can help you get rid of old emails.
The Delete All Messages in a Domain Endpoint released on March 23, 2021 can help you keep your private domain storage under the storage limit. It’s useful for deleting all messages before running integration tests.
This post will detail the different methods of bulk message deletion.
All messages in a custom domain can irrevocably be deleted.
From the Dashboard select Custom Domains → Select Domain to Mange → Advanced tab → Irreversibly Delete Email
The REST API has a commensurate endpoint for deleting all messages in a domain. It can be invoked by calling an HTTP POST https://mailsac.com/api/domains/{domain}/delete-all-domain-mail
, where {domain}
is the custom domain.
All messages in a Private Inbox can be deleted from the website or the REST API. Both methods will not delete starred messages.
From the From the Dashboard select Manage Email Addresses → Select Email Address → Purge Inbox
Messages in a Private Inbox can be deleted using the endpoint for deleting messages in a private inbox. The endpoint can be used with the HTTP DELETE
method on https://mailsac.com/api/addresses/{email}/messages
where {email}
is the private email address.
Individual messages can be deleted from both private and non-private inboxes.
From the From the Dashboard enter an inbox in the inbox viewer form and select Check The Mail!. From the Inbox, Click the message → Select Delete → Permanently Delete
Individual messages can be deleted using the delete message REST API. The endpoint can be called using an HTTP DELETE
with the URL https://mailsac.com/api/addresses/{email}/messages/{messageId}
. The {email}
parameter is the email address and the {messageId}
is identifier for the message to be deleted. The messageId
can be found by using the list messages in an inbox REST API endpoint.
At 7:40PM US West Coast Pacific time, we started a large planned database migration. Infrequent downtime is expected.
The Recent Activity Log now includes detailed sender and delivery information for outbound email. This empowers customers to diagnose sending issues.
The screenshot below shows a successful email delivery sent from [email protected]
to [email protected]
. The email message id, number of delivery attempts, rejection status, and time stamps are included in the logs
The screenshot below shows a failed email delivery from [email protected]
. 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.
Mailsac API Documentation has been converted over to use OpenAPI.
The new format gives developers and quality assurance testers code samples for common programming languages (curl, Node, Python, PHP, Go, etc).
The API can be explored without writing any code using the Swagger UI Explorer. All that is needed to get started is a free Mailsac API Key (requires sign up).
In the Swagger UI Explorer, choose the Authorize button and enter your Mailsac API Key
Use the “Try it out” button to interact with any of the REST API endpoints. A curl example, request URL, response body, and headers are provided.
All of our plans now included additional features. These features will help quality assurance teams and individual developers test sending and receiving of email, and easily share non-production email accounts.
To see a complete listing of feature visit see our pricing page.
We are in the process of rolling out these features to our existing customers. Please contact [email protected] if you need access to the features ahead of our scheduled roll out.
Old Plan | New Plan Feature / Limit |
N/A | Email Capture |
N/A | Webhook Forwarding (requires private inbox) |
N/A | WebSocket Forwarding (requires private inbox) |
N/A | Purge Inbox (requires private inbox) |
N/A | Slack Webhooks (requires private inbox) |
N/A | Community Support |
Old Plan | New Plan Feature / Limit |
10 Private Addresses | 50 Private Addresses |
0 Outgoing Messages | 500 Outgoing Messages (non-recurring) |
N/A | Email Capture |
N/A | Message Logs (15 minutes) |
N/A | Delete all messages by domain |
Old Plan | New Plan Feature / Limit |
50 Private Addresses | 250 Private Addresses |
0 Outgoing Messages | 2,500 Outgoing Messages (non-recurring) |
N/A | Website Login using API Key (2 users) |
N/A | Message Logs (1 month) |
The SMTP header endpoint provides quality assurance testers with the option to view an email message’s SMTP headers in parsed formats that easily integrate with automated testing frameworks.
Developers and QAs are often asked to validate contents of emails. This can include from address, links, and subject. For many organizations this can be a manual process of checking the email and validating if the test criteria has been met.
Mailsac’s new message header endpoint provides SMTP headers in 3 formats:
1. JSON object format, grouped by lowercased header key. This format is easily consumed by industry standard tools such as Selenium.
{
"received": [
"from 107.174.234.77 by frontend1-172-31-29-224 via 172.31.42.57 with HTTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon Dec 24 2018 15:29:06 GMT+0000 (Coordinated Universal Time)",
"from 107.174.234.77 by smtp-in2-172-31-42-57 via 172.31.23.10 (proxy) with SMTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon, 24 Dec 2018 15:29:06 UTC",
],
"from": [
"[email protected]"
],
"to": [
"[email protected]"
],
"subject": [
"invitation to collaborate"
],
"date": [
"Mon, 24 Dec 2018 15:29:06 +0000"
]
}
2. Ordered JSON array format. This formats pre-parses the headers, but maintains the original order, while still handling duplicate headers such as Received
.
?format=ordered-jso
n
[
{
"name": "received",
"value": "from 107.174.234.77 by frontend1-172-31-29-224 via 172.31.42.57 with HTTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon Dec 24 2018 15:29:06 GMT+0000 (Coordinated Universal Time)"
},
{
"name": "received",
"value": "from 107.174.234.77 by smtp-in2-172-31-42-57 via 172.31.23.10 (proxy) with SMTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon, 24 Dec 2018 15:29:06 UTC"
},
...
{
"name": "to",
"value": "[email protected]"
},
]
3. Plaintext original format. This format is useful when you are interested in parsing or inspecting the email headers yourself, and do not wish to download the entire message.
?format=plain
Received: from 107.174.234.77 by frontend1-172-31-29-224 via 172.31.42.57 with HTTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon Dec 24 2018 15:29:06 GMT+0000 (Coordinated Universal Time)
Received: from 107.174.234.77 by smtp-in2-172-31-42-57 via 172.31.23.10 (proxy) with SMTP id 8m7iqeiZKJ3MzwTwUQlU for <[email protected]>; Mon, 24 Dec 2018 15:29:06 UTC
...
To: [email protected]
“We are currently using the REST API headers endpoint in support between our own microservices. Our POP3 server fetches headers of message to implement the POP3 TOP command.” — Michael Mayer, Partner Forking Software LLC
The message header endpoint /api/messages/:messageId/headers
is available on all Mailsac plans (including our free tier). See our API Specification for more information.
This code example could can be modified to view the headers for the first email message on an inbox [email protected]
. Make sure to insert your API Key and change the email address to an email address you which is public or reserved by your account.
const superagent = require('superagent') // npm install superagent
const mailsac_api_key = 'YOUR_API_KEY_HERE' // change this!
superagent
.get('https://mailsac.com/api/addresses/[email protected]/messages')
.set('Mailsac-Key', mailsac_api_key)
.then((messages) => {
const messageId = messages.body[0]._id
superagent
.get('https://mailsac.com/api/addresses/[email protected]/messages/' + messageId + '/headers')
.set('Mailsac-Key', mailsac_api_key)
.then((response) => {
console.log(response.body)
})
})
.catch(err => console.error(err))
/**
{
received: [
'from [ by fireroof via ::1 with HTTP id bo4xdVji_oqEixBO0gGLbvIoe for <[email protected]>; Wed, 28 Oct 2020 23:05:29 GMT',
'from [ fireroof with SMTP id bo4xdVji_oqEixBO0gGLbvIoe for <[email protected]>; Wed, 28 Oct 2020 16:05:29 PDT'
],
'x-mailsac-inbound-version': [ '' ],
date: [ 'Wed, 28 Oct 2020 16:05:29 -0700' ],
to: [ '[email protected]' ],
from: [ '[email protected]' ],
subject: [ 'test Wed, 28 Oct 2020 16:05:29 -0700' ],
'message-id': [ '<20201028160528.2893005@fireroof>' ],
'x-mailer': [ 'swaks v20190914.0 jetmore.org/john/code/swaks/' ]
}
**/
Update: April 2021 – Multi-User login is now called “Sub-Accounts”
Named API Keys can now be used as website authentication.
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
Getting started is as easy as provisioning a new set of API credentials and enabling the website login on the API Key. This can be done the the Dashboard and selecting API Credentials & Users
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 [email protected] to get early access to this feature on you Business or Enterprise Plan.
With email capture, Quality Assurance teams testing email delivery can easily see the exact emails customers will receive.
The new Email Capture Service is an SMTP server that accepts all mail regardless of the To
and From
address. It is similar to Mailsac’s existing disposable mail, with some key differences. The capture service acts like a fake outbound relay, rather than a fake inbound relay.
Messages sent via capture.mailsac.com are available for viewing from the Mailsac Website or REST API. This allows Quality Assurance teams to validate that the message was sent and the contents of the message.
Web applications frequently send transactional emails to users. During development and User Acceptance Testing, sending email is disabled in the application – so emails are not accidentally sent to customers or fake test addresses. Sending lots of bounces from a development application is a great way to get your domain blacklisted, greylisted, or onto a spam list.
Web applications can be configured to use the Email Capture Service as their SMTP server. Emails sent by the application can then be viewed by developers and testers.
Customers have been sending test emails to hosted custom domains at Mailsac for years. The email capture services simplifies the process of sending emails to Mailsac by allowing developers to relay through Mailsac without any additional email infrastructure.
Michael Mayer – LLC Member at Forking Software LLC.
Most customers can get started sending through the Email Capture service instantly.
Wherever you input SMTP credentials in your application, change to the following:
5587
Any email sent to the capture server will be available at the TO address in Mailsac’s UI or API.
* a private address or custom domain address may be used if your email library does not support a separate FROM address for the username.