Hello, when using the Laravel Framework, the integration you provided overrides the default configuration values which resolves .env file. That is why, we end up entering this information manually.

Instead, can you please provide the .env file values as well/instead of the config file?

Like:

MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME={mail_username}
MAIL_PASSWORD={mail_password}
MAIL_ENCRYPTION=null

Why aren't different roles defined in your solutions. Currently I see owner and user.
What about administrators etc..

According to https://twitter.com/Mailtrap/status/1034816874188554240 you removed the ability to remove email messages using POP3 protocol.

We rely on this function since we don't only use mailtrap to send emails but also to read emails and test our POP3 client.

At the moment, it seems like you can only invite company users by the share link. When inviting a team of folks, this means I have to send the link to them all, then check back that they've accepted it before changing that share link to prevent further sign-ups if it's accidentally shared later.

It would be good if you could invite specific email addresses only, rather than anyone who has access to a global share link.

It would be great if team members within a paid team could sign in using our organisation's existing single sign on infrastructure.

This would mean when folks leave the organisation, they'd automatically lose access to Mailtrap. Better yet, if we could configure Mailtrap to allow anyone with a specific role access as a team member, this would greatly simplify our ability to manage team members.

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

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.