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!
33 results found
-
1 vote
-
Malware scan of Email attachments
I am writing to request the implementation of a malware scan for attachments in incoming emails. We regularly receive emails from users that may include attachments, it is imperative that we take proactive measures to mitigate the risk of malware infiltration. To achieve this, we kindly request the integration of a robust malware scanning system for email attachments.
The primary objective is to identify and eliminate any potential threats that may be concealed within attachments before they reach the intended recipients.1 vote -
Unique user-agent name for webhook requests
Ability to change the user-client name for webhook POSTs. For instance, "Mailgun Webhook API" or something similar.
1 vote -
API for returning user/admin info - Mailgun UI
Would love an API for returning information about the management users for the Mailgun account.
I'd like to be able to query to get a list of "what employees have mailgun accounts? what role (admin etc) they are assigned to? is 2FA is configured?"
Would like to have the capability to get those details programmatically from Mailgun on a recurring basis.
Having this via the API would be extremely beneficial.
1 vote -
Set a default DKIM selector for the account
Every sender domain you add currently gets a random DKIM selector such as email.dmarc, mta.dmarc or web._dmarc for example. However, it would be easier to have it so that you can set a default on account level for every new sender domain so it is always the same by default. Offcource you then can change it if needed.
1 vote -
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 -
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
- Don't see your idea?