To help manage volume, I'd like to be able to set a rule (per inbox) that automatically delete email n days after receipt.

For instance, during development, all email sent from the dev's box goes to one inbox, and can expire within a day. For some QA teams, that range might be 60 days.

Generate a .muttrc file from the "Integrations" menu.

Compliance and Data Protection

I need to check case when email ( recipient ) does not exist.
I know you don't check if email address exists in real world, but you could allow to set one or some email address(es) in configuration
and send 'recipient not exist' response with appropriate status code when client/user sends email to that address(es)

A while ago you removed [MAILTRAP FORWARD] from the subject and added a customer email header (x-mailtrap-forwarding) instead. This is causing problems for our Gmail users which had a custom filter for all emails from mailtrap.

While most of the standalone email clients allows to filter on the
new email header (x-mailtrap-forwarding), gmail doesn't allow this.

We would really appreciate the possibility to toggle the [MAILTRAP FORWARD] in the subject or maybe even better; allow users to add their custom prefix to the subject.

Change the mailtrap mascot to a toasted cheese sandwich

improving search the emails? Starts with is not really good...

The person who starts the account and handles the billing isn't always the one that wants to manage all the users as employees come and go. You need to allow multiple owners (incase owner A get hit by a truck) or at least another layer of security so someone else can manage users on the companies account.

Web Notifications.
So that when you receive a new mail, you get a nice popup :)

It would be great if there was a way to look up messages using the message_id header via both the API and the web interface.

That way it would be easy to programatically verify that a give message was delivered using the API

There doesn't seem to be an obvious way to create a bunch of users for an entire company group - this would make inbox addministration muc easier

Keyboard shortcuts

Allow users to sign up and access a shared inbox in one step.

Right now, users have to sign up, and then the inbox owner has to share the inbox with them in a separate step.

offer clients for different programming languages. my preference nodejs

Our use case is simple: we want to forward specific types of emails (our example: password reset). We can always classify them based on the subject line, but not on the email address nor the domain. This feature request is to add automatic forwarding based on subject.

We use a bulk email delivery company as our email campaign gateway (Socketlabs).
I am looking for something that will automate the responses to campaigns - ie. enable some to return
Bounced
Failed
Complaints
Opens
Clicks
The response could be set by mailbox - and perhaps the facility to spread the timing of opens and clicks.

Some hosts, such as GoDaddy, block all SMTP ports, or don't allow using an SMTP server other than their own. A lot of mail services, such as Mandrill, Mailgun, Sparkpost, etc. provide both an SMTP server and a REST API for accepting email. Providing a REST API endpoint for accepting email would allow users on such restrictive hosts to be able to use mailtrap, even when they can't use the SMTP server.

It would be nice to have configuration example for Exim too (only Postfix example is available today).

It would be helpful to be able to alphabetically sort the list of inboxes.