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.
Send via capture.mailsac.com instead
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:
- Server Name: capture.mailsac.com
- Port:
5587 - Use Secure Connection: Yes (TLS)
- User Authentication – Username: Mailsac account username *
- User Authentication – Password: any Mailsac API Key for the account
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.