Help shape the future of Mailtrap! What's your idea for making it better for everyone?
Share your feature requests!
Preview text should not be followed by the email body
This is honestly extremely frustrating. When I define a custom preview text for an email, Mailtrap still lets email clients append the beginning of the email body right after it. The result looks messy and completely defeats the purpose of having a dedicated preview text. Brevo already handles this properly by automatically preventing the email body from appearing after the preview text. Mailtrap should do the same: when a preview text is defined, automatically add the necessary hidden padding so that only the preview text is displayed in the inbox preview. This should be handled by Mailtrap, not something users have to manually hack into every email template.
Show Category Timeline by Hourly
Currently, under "Email API/SMTP" → "Stats" → "Email Categories" → "Timeline", the data is displayed in a daily (date-based) format. Is it possible to add an hourly view as well, so that the statistics can be displayed on an hourly basis? Why is this feature needed? To monitor email sending frequency at a more granular level. The current daily timeline only shows aggregated totals per day, which makes it hard to see how volume is distributed within a day. An hourly view would let us track sending patterns and spot spikes as they happen. How do you intend to use it? We'd use it to monitor hourly sending frequency against our hourly limit, identify unusual bursts or peak-sending periods during the day, and better understand our sending behavior over time.
Simple Mobile View (remove sidebar)
We use Mailtrap to do software demos with an iPhone resolution sized browser window. This used to work great, however, you recently introduced a persistent left side navigation bar that we can’t collapse entirely. Please collapse this menu to hamburger menu when using mobile phone size browser resolution, or let us simply turn it off
Integration tests should not reuse event_id across types
All of the sample payloads use the same event IDs, so you can’t test different types if your service is aware of duplicate event IDs. It’d be nice if they were randomized when you switched tabs altogether so you can also test multiple events of each type.
WordPress RSS post
In Brevo, I can ask the service to automatically generate a newsletter from the last WordPress post(s). It is a kind of automation that creates a message using a given template that has support for getting the RSS fields, subject, date, excerpt, etc,... I have been using this in Brevo for a decade, and in Mailchimp as well. Every week, I get my newsletter sent with my blog's latest updates. That could maybe also used for other kind of RSS files as well.
More flexibility in Email transmission
Allow to start and stop email transmission through the dashboard
Templates sorting and ordering
Allow manual reordering and sorting options in the templates dashboard.
Templates: MJML support
Designing responsive emails is harder without MJML tooling. Add MJML support in the template editor and API (compile to HTML).
Detect 🤖 bot opens/clicks
Security scanners and bots inflate open/click metrics. Detect likely bot activity and label it, so it can be excluded from engagement metrics. Provide that info in webhooks payload.
Unsubscribe Groups (category‑based opt‑out)
Let subscribers choose what types of emails they receive instead of unsubscribing completely. Create custom preference centers with multiple subscription categories. Reduce total unsubscribes while respecting user preferences and maintaining compliance.
Suppressions: blocklist by recipient domain
Blocking addresses one by one is inefficient at domain scale. Allow domain‑level suppression (*example.com) in addition to per‑address blocks (user1@example.com, user2@example.com).
Templates: versioning and history
Template edits are risky without history and rollback. Introduce versioning with diff/restore and version labels.
Change NDR for a client email address
Bounce notifications (NDRs) are sent to Mailtrap Return path. Let users configure the sender/return‑path for NDR/system emails or forward them to a designated address.
Billing: annual plans for Email API/SMTP
Self‑serve annual billing isn’t available for Email API/SMTP. Add yearly plans with clear overage handling.