questionFAQs

This page covers frequently asked questions about Email Sandbox. For technical issues and error troubleshooting, see the Troubleshooting section.

Integration & setup

chevron-rightHow do I integrate Email Sandbox with my application?hashtag

The integration is very simple and you can complete it in just a couple of minutes using SMTP credentials or code samples for over 20 frameworks.

See our step-by-step guide: How to integrate Email Sandbox with your application.

chevron-rightDo you need to view Sandbox emails only through its interface?hashtag

No, you don't have to stick to Email Sandbox web interface. You can forward every single email to your or a teammate's mailbox.

You can even enable automatic forwarding, and Email Sandbox will act as a proxy between your application and your email client. In this case, you won't miss important messages from the QA environment, such as exception notifications.

Learn more:

Technical specifications

chevron-rightHow does Email Sandbox render emails?hashtag

Sandbox renders emails in the same way browsers do, which means no additional stylesheet or CSS presets are applied by default.

chevron-rightCan Email Sandbox show what emails look like in various email clients?hashtag

Email Sandbox is compatible with web email clients and renders HTML as-is, without external CSS styles.

Sandbox provides HTML checks and demonstrates potential errors that different email clients may experience when rendering an HTML email. You can also get a preview of test emails for different devices (e.g., mobile, tablet, desktop).

You can also forward emails to Outlook, Thunderbird, etc., and use these desktop clients to view them.

chevron-rightWhat does Sandbox do with the <style> tag?hashtag

Sandbox doesn't remove the <style> tag from email templates.

chevron-rightWhat does Sandbox do with the <script> tag?hashtag

For enhanced security, Sandbox removes all <script> tags from HTML.

chevron-rightCan I use Email Sandbox as a /dev/null SMTP server?hashtag

The main goal of Sandbox is to help you test emails, and /dev/null is not a part of it.

Should you need a /dev/null SMTP server, please use the following built-in Python SMTP server:

chevron-rightWhat is the email size limit for Sandbox?hashtag

The maximum size of an email including attachments ranges from 5 MB to 25 MB, depending on your subscription plan.

If your message exceeds this limit, you will get the following error: 552 5.3.4 Error: message too big.

For complete details, see Features and Limits.

chevron-rightWhat is the testing rate limit for the sandbox?hashtag

It's the number of emails you can send to each of your sandboxes every 10 seconds. The rate limit depends on the subscription plan.

For more details, check out the Features and Limits article and our pricing pagearrow-up-right.

chevron-rightWhat is the monthly messages limit for Email Sandbox?hashtag

It's the maximum number of emails you can test and get in all your sandboxes per month. The total emails per month limit depends on the subscription plan.

If you reach your monthly limit, you'll receive the SMTP protocol error: 535 5.7.0 Monthly messages limit reached. We also send out notifications for having used 80%, 90%, and 100% of the monthly limit.

To continue testing when you're over the limit, please upgrade your subscription plan. Alternatively, you can wait until the next billing period starts, when the limit is reset.

For more details, check out the Features and Limits article or our pricing pagearrow-up-right.

Pricing

chevron-rightHow much does Email Sandbox cost?hashtag

Email Sandbox provides a free subscription plan for new users who want to evaluate it.

For larger teams, we offer sets of features within several paid subscription plans, starting from $17/month.

To choose one that best fits your needs, check our pricing plansarrow-up-right.

Last updated

Was this helpful?