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!
30 results found
-
Have the ability to turn off SMTP sending for the domain if only API is being used.
If we are not utilizing SMTP but only API we want the ability to turn off SMTP so that the server settings can't be used.
3 votes -
Comments to SMTP credentials
It would be nice that we could add some comments to accounts at SMTP credentials. Now we have a list of accounts that was created years ago and I'm not sure where they are used. In this case if there are would any comment section I could enter that this account is used in CRM and this in website as example.
3 votes -
Sort order SMTP login
Hello,
It would be great if SMTP Credentials could be sorted on Login (ascending or descending).
Best regards,
Simon1 vote -
Delayed email route
Forward routes to email are executed immediately. It would be nice if a delay could be configured, so that an email isn't immediately forwarded on receipt. In our case we want to do some backend processing (via HTTPS route) before the email route forwards the email to our user.
1 vote -
Allow setting the open, click, and unsubscribe settings when creating a domain
Currently when creating a new domain via the API, we have to set the open, click, and unsubscribe tracking settings via individual PUTs. Instead, we should be able to create and configure a domain in a single call - that way we don't have to worry about a domain being partially setup.
1 vote -
Allow specifying the DKIM selector during domain creation via the API.
Currently when creating a new domain via your API, you have to post a second request to set the DKIM selector. I think it would make more sense to allow us to specify the DKIM selector (along with anything else) in a single request - that way we don't have to worry about the possibility of a domain being partially setup (e.g. the create domain being successful but setting the DKIM name as unsuccessful).
1 vote -
Provide receiving API keys specific to domains
This would enable finer grained control for development teams that have multiple environments or applications using the same account.
For example, credentials to receive from development / receiving domains would be different than the ones needed to receive from the production domain.
1 vote -
Remove RequestedAuthnContext Parameter from SAML Response
In the MG SAML requests a parameter called RequestedAuthnContext is included. Some customers wish to remove this parameter, however doing so has the potential to lead to unwanted/unexpected behavior in Mailgun's systems.
2 votes -
Request for method to programatically pull security event logs
Requesting to have an api endpoint or programmatic way of pulling security event logs (e.g. a org user logs in, if there was a failed login, activity of users etc) so they can be ported over into a SIEM.
2 votes -
Sending DNS record instructions via email with one click.
I should be able to send someone the DNS records via email so they can connec it to their hosting.
1 vote -
Option to Retrieve / Export Account Users
Currently it is only possible to view the users on an account within our control panel. Having a way to retrieve and/or export this information via API would be helpful for customers who do not wish to use our control panel
1 vote -
MJML sending via API
In addition to the "text" and "html" parameters of the "messages" API endpoint, add another "mjml" parameter. Mailgun should automatically generate the HTML from the MJML and send the email.
Currently, an intermediary trip to the MJML API (https://mjml.io/api) is required (which is still in beta, so that it might be unsuitable for use in production) in conjunction with the Mailgun API or a custom Node.js service for parsing the MJML before sending it to Mailgun has to be set up.
Seeing as Mailgun and Mailjet/MJML are owned by the same entity, it would be good if this…
1 vote -
API access audit logs
API Access Audit Logs
Please provide audit logging for any and all API calls. Results should include
- Date/time
- Source IP
- API called
- Account used
- Query header
- Authentication Success/Failure1 vote -
Delivery Queue and Average Delivery Time Analytics
Please create a Ops dashboard where i can see
What is the current length of the delivery queue (how many messages has been accepted but is still waiting for delivery)and a graph of the delivery time -> the average time a message is taking moving from accepted to delivered
1 vote -
MAKE A MOBILE-FRIENDLY WEBSITE
For crying out loud, MAKE A MOBILE-FRIENDLY WEBSITE.
2 votes -
PTR record Setup
It would be nice if the DIP process would be more streamlined and the setup of the PTR record be initiated upon assignment to avoid any mailing complications with ESPs like Microsoft.
1 vote -
Add unique opens and unique clicks in stats api
Hi there, working with the stats api at the moment and realized that for "opened" and "clicked" event types only totals are provided (https://documentation.mailgun.com/en/latest/api-stats.html#event-types)
It would be great if you could add unique opens and unique clicks as well to that api.
Thanks in advance.
Daniel2 votes -
Account Audit Logs
Audit logs that cover user events. Events could include:
login
logout
API key rotation
template change/edit
mailing list change/edit
manual suppressions list add/delete/change
webhooks add/delete/change
sender key creation/rotation
domain add/delete
domain settings (TLS, message retention, tracking settings, etc.)
user role add/delete/change
validations job
IP/IP Pools changes
authentication changes (SAML, Google Auth, etc)
account settings changes (billing details, timeout, downgrade/cancellation)7 votes -
Email notification for reply to ticket
When a reply is made to a ticket please inform us by email.
2 votes -
Retry when the DNS server is not responding
It's more a bug than a feature, but you CS referred me to here.
I ran into a problem when Mailgun doesn't route emails to my end, since "the DNS server didn't respond at that time"I really tried to understand why you just don't send the request again and try to reach the server after a few minutes?
The DNS server should always be available, so it just makes sense to send the request again and try to route the email.2 votes
- Don't see your idea?