SMTP servers forward mail on to BCC recipients while at the same time stripping that field. Because Mailtrap is serving as the SMTP server, it can record the original data in the BCC header.
The default Mailtrap view should continue to hide the BCC header to provide a Client-like view, but the BCC header should be made available in either the RAW view or another view "As Received".125 votes
It will be good to be able to receive bigger emails using mailtrap. Is it possible to increase message limit to, for example, 10MB for paid account?
Or as workaround - allow forwarding of that emails.19 votes
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?
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!
Add ability to migrate ownership to another user in company, for example by confirmation email.17 votes
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.17 votes
It would be helpful to be able to alphabetically sort the list of inboxes.13 votes
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 easier12 votes
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
Why aren't different roles defined in your solutions. Currently I see owner and user.
What about administrators etc..3 votes
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! :)
Symfony 4 configuration example would also be nice.
###> 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"
###< symfony/swiftmailer-bundle ###1 vote
Hi, thanks for your request! We’ll add this example.
- Don't see your idea?