General
-
Symfony 4 .env configuration
Symfony 4 configuration example would also be nice.
.env example:
###> symfony/swiftmailer-bundle ###
# For Gmail as a transport, use: "gmail://username:password@localhost"
# For a generic SMTP server, use: "smtp://localhost:25?encryption=&auth_mode="
# Delivery is disabled by default via "null://localhost"
MAILER_URL=smtp://81d3957be84923:9e35845b8b3b2f@smtp.mailtrap.io:2525?encryption=tls&auth_mode=login
###< symfony/swiftmailer-bundle ###1 voteHi, thanks for your request! We’ll add this example.
-
Auto Forward SMTP log view
View forwarded smtp logs
1 voteThank you for the request! Currently, we won’t be implementing such functionality. This can become something we’ll look into in future, depending on the community demand.
-
Support port 587 as well
Some software doesn't let you specify port...
3 votesHi!
Thank you for the request. We’re planning to implement the support for port 587 with future Mailtrap version. Stay tuned! -
Add laravel .env file boilerplate instead of config array as integration
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=null18 votesHi,
Thank you for your request, makes perfect sense! This feature request is already in our to-do list and will be implemented any time soon. Please, stay tuned! -
roles
Why aren't different roles defined in your solutions. Currently I see owner and user.
What about administrators etc..3 votesHi!
Thanks for your input.
We agree that expanding Mailtrap’s administration roles and permissions is important to our users, and currently, it is one of the priority tasks on our to-do list. We’ll be releasing this functionality with a new version.
Stay tuned! :) -
Readd the ability to remove email messages using POP3 protocol
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.
6 votesThanks for posting this request! We consider re-adding this option in future for your convenience. Meanwhile, you can make use of our API for removing messages .
-
Allow invitation by email address
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.
6 votesHi,
Great request, thank you! We’ll add this option in the upcoming update. -
Allow single sign on via WS-Federation / SAML / OpenID Connect / JWT or similar
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.
20 votesHi,
Your request makes great sense, thank you!
Currently, we are focused on feature requests with top priority, anyway, we will make sure to investigate possible ways to get single organisation’s sign on implemented for Mailtrap in future. -
Allow "Forward as attachment" to prevent spoofing
The problem with forwarding an email from a mailtrap domain is that the original "From" address remains intact, creating a situation where it appears the forwarded email appears like the sender (mailtrap) is spoofing the original domain.
For instance, a test forwarded email, note the content:
Received: from mailtrap.io (ec2-52-55-102-193.compute-1.amazonaws.com [52.55.102.193])
by ismtpd0024p1iad2.sendgrid.net (SG) with ESMTP id OlrG4Ki2RRyRjj3CpUmVYg
for <myname@mycompany.com>; Wed, 25 Apr 2018 17:35:19.161 +0000 (UTC)
Clearly should be rejected for safety.Our company's rules tag this as a spoofing email, which of course confuses our testers.
Gmail blocks these so they never get to the inbox.
…
7 votesHi,
Thank you so much for your suggestion!
We’ll consider implementing it once we go through our to-do’s with bigger priority in our backlog and if we see that this request has high demand. -
Mutt configuration
Generate a .muttrc file from the "Integrations" menu.
3 votesHi!
Thanks for your request.
May we ask you to provide an example of configuration that will be applicable to your use case? We will add your request to our backlog once we have these specifics. -
Simulate 'Failed' response
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)13 votesHi,
Interesting idea! We will consider working on this feature once the request is in high demand. Thanks for the input! -
Allow custom prefix like [MAILTRAP FORWARD] in subject
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.
5 votes -
Search any text in the email/subject
improving search the emails? Starts with is not really good...
6 votes -
Allow multiple Owners or another layer of security to manage Company Users
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.
13 votes -
Web Notifications
Web Notifications.
So that when you receive a new mail, you get a nice popup :)4 votes -
Add Company Users for all Inboxes in Company
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
12 votes -
Add Keyboard shortcuts
Keyboard shortcuts
4 votes -
Create an invite feature for shared inboxes
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.
16 votes -
Add the ability to forward email based on subject
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.
3 votes -
4 votes
- Don't see your idea?