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!
102 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 -
Suspend/unsuspend SMTP Creds
I would love to see the ability to suspend/unsuspend SMTP Credentials.
Occasionally customers don't pay and I'd like to suspend their creds...but my only option at the moment is to delete their creds or reset their password. Both of those options require us to spend time settings things back up in various different systems.
1 vote -
We have many versions of one template and the most recent versions are at the last page. It'll be nice to have the most recent versions on t
We have many versions of one template and the most recent versions are at the last page. It'll be nice to have the most recent versions on the first page
1 vote -
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 -
Set "too old" expiry period on send
Our customers often send alerts that are very timely in nature, so if they aren't sent in some period of time they don't want them sent at all. Often that period of time is much shorter than the current default 8 hours.
It would be helpful for us to be able to set the send window for an email in the send api to prevent overly stale sends from going out.
1 vote -
webauthn/yubikey support
Please consider adding support for webauthn/yubikey as a 2FA method for admin accounts. It's superior to TOTP, since it's phishing resistant & hardware tokens cannot be stolen without physical access. Also, it is more convenient to use. (When implementing this please be sure to allow users to enroll multiple security keys when enabling webauthn 2FA)
1 vote -
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 -
Cloudflare DNS Auto-Connect
I would like to request a feature that allows seamless integration between Mailgun and Cloudflare for DNS configuration. Similar to how Google Workspace provides a one-click setup process for adding necessary DNS records via Cloudflare, this feature would streamline the onboarding process and enhance the user experience.
Currently, setting up Mailgun requires manually adding DNS records (MX, SPF, DKIM, etc.) to the domain's DNS provider, which can be time-consuming and error-prone, especially for users less familiar with DNS management. A seamless integration with Cloudflare, leveraging Cloudflare's API, would enable automatic configuration of all required DNS records with a single click…
1 vote -
domain dropdown field
Extend the site of the domain dropdown so you can see more characters. Longer domains cant easily be located by their extension since its cut off.
1 vote -
Template Editor access at lower-level role than Developer
We have numerous users who design email templates. We need to give them access to the DnD template editor and the HTML template editor. Currently the only way to do this is to assign them to the developer (or admin) role. The developer/admin roles contain way too much privilege for these users.
I would like the Support role to have access to create/modify templates, or for a new role like "Designer" to be implemented. Then I could grant users access to create and modify templates without giving them unnecessary and risky privileges.
1 vote -
IP address
On the new "Sinch Login" dashboard there is an "Activity" tab which makes it clear what access has happened recently. It'd be good to add a column for IP address to this table.
1 vote -
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 -
Make tracking domains reachable via IPv6
Currently tracking domains are only reachable via IPv4 addresses
1 vote -
Provide a catch all emails like mailhog to test
Could we have a catch all emails like the tool mailhog does. It's very complicated to test and not practical at the moment
1 vote -
Apply date formatting to Metrics screen
I have set my preferences to display ISO date/times. In the Metrics screen I only see AM/PM times. And the dates are also formatted in some backwards format.
1 vote -
Search Option for SMTP Login Names
I don't see an option in the "SMTP Credentials" interface in the "Domain Settings" page under "Send" that allows a search for login names. This would be nice to have when trying to find a login, and it would make an otherwise nice website and interface even better.
1 vote -
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 -
Log who creates an API key, make part of the key model, and show in the UI with the key ID to allow for security auditing and spot checks
This missing is a bit of a security risk as if a user creates an API key we cannot audit it and understand who performed the action within our organization. Talking to support they could not tell us which user created an API key.
A user created an API key and then we could not tell who had performed the action though it was someone who we would have allowed to do it. Were we able to tell it was them, we'd not have needed to contact support. We had to reach out to all our users and figure this…
1 vote -
greenhouse gas emissions on invoices
Transmit the greenhouse gas emissions associated with the service you are invoicing us for, on your invoices
1 vote
- Don't see your idea?