Email app load testing
Email app load testing is one of the most popular cases of using Mailtrap's Enterprise plan. This plan allows you to send up to 150 emails every 10 seconds to as many as 300 inboxes.
Every Mailtrap inbox has a unique email address that can be customized (the "email per inbox" feature). It consists of two parts:
- A customizable alias, which you can edit manually. You can use any combination of numbers and Latin symbols. For example, your company name or the name of the current inbox with an identifying number. Mailtrap inboxes support dynamic aliased addresses. For example, firstname.lastname@example.org and email@example.com will both be accepted and delivered to the same inbox.
- Mailtrap’s technical hash, which cannot be changed. It consists of 6 symbols and acts as our internal inbox identifier. Using this feature, you can use an infinite number of address combinations, and can imitate sending emails to a large number of users (with unique email addresses). The inbox name changes are applied instantly, meaning that you don’t have to pause your email testing and wait until a new alias becomes valid.
Also, note that Mailtrap verifies inbox aliases so that if you try to send a message to a custom inbox address that doesn’t exist, you will get the "554 5.5.1 Error: no inbox for this email" message.
By default, the inbox email address is disabled for security reasons. To activate it, go to the Email Address tab and open the three dots menu next to the Copy button. Click Enable. In this menu, you will also find the Edit and Reset Address buttons.
Load testing use case
Large-scale systems employ numerous servers to distribute loading. Specifying a separate testing email address for each server allows you to follow and inspect failures or unexpected behavior. This way you can test and load all your resources at once and then filter the results accordingly.
Here is how it looks in practice:
- email server A sends messages to the firstname.lastname@example.org inbox
- email server B sends messages to the email@example.com inbox
- email server C sends messages to the firstname.lastname@example.org inbox
- email server L sends messages to the email@example.com inbox, etc.
Then enter a corresponding project in your Mailtrap account and see a list of these inboxes with the number of messages in each on one screen:
This way, you can check and compare your sending capabilities and instantly identify which of your servers is experiencing problems.
You can disable the email addresses any time you need it. We recommend disabling them as soon as you finish testing, for improved safety.