Feature Requests
If you’ve got a feature request, you’ve come to the right place! Please relay your request request here, along with any additional details you think might be helpful.
This is not the spot for feedback on current features, only new plausible ideas will be considered. Please be courteous of others and upvote if you believe strongly enough in an idea!
84 results found
-
Add support to automate creation of sending API Keys with Terraform
We would like to automate the creation of the API sending keys with terraform.
1 vote -
Scheduled Report Email To Have Report In Body Of Email
Customer would like to have the scheduled report email contain the actual report in the body of the message as opposed to having to download a file.
2 votes -
billing
Ability to access billing data via API to calculate costs per email or total costs directly from the data provided in the billing section of our Mailgun account. Specifically, we are looking for a way to retrieve this information programmatically to integrate it with our admin panel.
2 votes -
Add template name as a query parameter in the API.
Add template name as a query parameter for getting templates based on their name through the API.
2 votes -
Method and api-key-id flag in all the events
Pass the "method" and "api-key-id" variables in all the events for emails sending through SMTP credentials.
1 vote -
Cancel queued emails from a particular sender
Similar to the cancel emails for a domain but filtered on emails sent by a sender (From field in the message). for example this would allow cancelling emails from no-reply@company.com but not the ones sent by alerts@company.com
1 vote -
Support DNSSEC for mailgun.org
DNSSEC is supported for eu.mailgun.org but not for mailgun.org
3 votes -
3 votes
-
Change order of templates versions by date DESC
It'll be very handing to show recent template versions at the beginning, not at the end
1 vote -
Webhooks - Change user agent to something that identifies Mailgun
Change the user agent for webhooks from Go-http-client to something more specific.
Our system gets lots of requests from user agents identified as Go-http-client and we want to block them as the vast majority are from Bots5 votes -
Make tracking domains reachable via IPv6
Currently tracking domains are only reachable via IPv4 addresses
2 votes -
Domain Queue overview
At the moment, one can clear the domain queue. in doing so, it would be nice to see what is actually queued on the domain e.g. emails in the retry window, scheduled sends, etc. Right now it is a black box.
4 votes -
2 votes
-
Extend API to Allow Modifying Message on the Server without Downloading
It would be great if Mailgun API is extended to allow modifying the message on the server, before sending it out, without downloading.
Our use case is very simple. We want to update FROM, TO, CC, BCC for each received message and send it out. The current API allows this use case, but requires that each message is entirely downloaded by our services, including all possibly big attachments, and uploaded back to Mailgun after updating. This is a lot of wasted network bandwidth both ways and highly increases processing / delivery times of each message.
If Mailgun API is extended…
1 vote -
terraform
create/modify/delete Mailgun resources using terraform
There is a community driven provider for Mailgun but does not support all the API's
https://registry.terraform.io/providers/wgebis/mailgun/latest/docs/resources/domainwould be nice to have an official Mailgun provider
3 votes -
Use Recipient Variable without batch sending
Could Mailgun provide some option to explicitly disable Batch Sending, or not batch send if the only Recipient Variables being used are related to one-click unsubscribe headers?
7 votes -
Log Attachments and ReplyTo Header
It would be nice to download the Mail Attachments from the Logs. This is especially useful for Testing or Real-World Issue Tracking.
Also I'm missing the "reply-to" Header in the Logs. Is there a way to expose this?1 vote -
Allow for dynamic domain URLS when forwarding Email Routes
for receiving emails, I want to create a catchall route that can route to a specific client site based on email address, like so:
match_recipient("(?P<user>.?)@(?P<domain>.).mysite.com")
and then in "forward" put:
https://\g<domain>.mysite.net/api/emailrecieving
This would give us infinitely less routes to maintain.
3 votes -
Cancel shedule email
Currently we are stuck in situtation where we are scheduled the future email but we can not cancel the the scheduled email.
Ex: We have scheduled 5000 emails which are sent after 2 days. I want to cancel only 5 emails out of 5000 but this simple functionality does not exist by REST API.
Suppricing for any user that I can schedule the email but I can't cancel the specific scheduled email.
Can we have this functionality, please?
5 votesWe will be offering a public API to allow basic CRUD operations for scheduled sends.
-
Name, email and number to be added to CSV email validation file
The ability to upload not only the email but also the name so it makes it easy to manage CSV files and validated emails when adding them back into the crm system. At the moment, with just emails, it's a long process. Trying to update files with names on valid emails causes long issues; if we were able to just export validated names, emails, and numbers, then it'd be easy to move files between systems.
1 vote
- Don't see your idea?