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!
-
Detect for multiple emails sent to same person by subject line and time rather than message ID
Right now, Mailgun will send the exact same email to our customers if the message ID is different. Some of our customers have received more than 150 copies of the exact same email, each within seconds of the last, because the message ID# for each is different, even though the subject line and content of the email is identiical. There ought to be a way for Mailgun to notice when it is sending the same email to the same person over and over again.
2 votes -
provide the option to notify an email address when certain mailgun actions have occurred (bounces, suppressions etc)
Would be great if this could be simple but configurable - or if we could opt to have summary reports at the end of a day/week/month of bounces, suppressions etc. Thanks
3 votes -
Forward mail to mailgun server for receiving Emails (instead via MX record)
Hello mailgunners,
wouldn't it be a nice possibility to receive inbound Emails via forwarding? We mostly cannot point to mailgun mailserver via MX record. But we could configure the Email addresses in question to be forwarded to some-cryptic-mailbox-name-dedicated-to-our-domain@inbound-or-whatever.mailgun.org.
Greetings from Germany,
Tobias Jamin2 votes -
Disablement process needs to be improved
The account disable process as currently defined is somewhat user-hostile. There are a couple small items that would make the actual experience less disruptive and easier for everyone to resolve. First and foremost, disabling the logs page on the impacted domain seems to be counter productive. I was hoping to be able to investigate for malicious behavior via those logs. Disabling the page means that I had to waste the time of the support staff to help root cause the problem (thanks again Raquel!). Secondly, the quick-pass onboarding process doesn't call out that inbound messages can impact the operation of…
3 votes -
Expand the stripped-text feature to other languages, e.g. german
I'm happy to help and I'm glad you open sourced this library, but please let pull requests in and ship it to production :)
6 votes -
Add regex capabilities to search boxes in the website
Especially:
- mailing list recipients
- logs3 votes -
Notify account holder when reaching max routes limit
The maximum limit for routes is 5,000. Currently Mailgun does not notify you when you're close to the limit. This is especially risky if you create lots of routes programmatically via the Routes API.
4 votes -
The failed reason value passed to webhook and classfied in Mailgun event log are different
I find the failed reason value passed to webhook and classfied in Mailgun event log are different.
e.g. we just can get the reason value like "hardfail" or "old" from webhook, but we use Event api can get "bounce", "suppress-bounce", "old", "suppress-Complaint", .... these many reasons. so we want Mailgun can make the reason values are consistent in both ends.2 votes -
Add the ability to set a daily or hourly cap on outgoing messages
This would be a useful safety feature in the event that something goes wrong in user code that is pushing messages thru mailgun.
4 votes -
Allow sending text/calendar as a multipart/alternative format so Outlook can accept my invites
We've been sending ics files as attachments, but the only way that Outlook will recognize them as calendar events is if you send it as a multipart/alternative. The Mailgun API only supports text or html, which means I have to build a MIME email to send it.
7 votes -
Provide an option to not re-sign emails when forwarding
Currently, Mailgun re-signs emails using DKIM and modifies mail headers when forwarding incoming mail. This causes Gmail, and possibly other spam filters, to give the email more trust than it should have. Could an option be provided to forward the existing envelope, without re-signing?
2 votes -
Add the event's timestamp in addition to the webhook timestamp
The time of the event is important to us and if the event time is only available from the Event API, then we will have to make additional calls to the Event API for EVERY single notification(delivered, failed, open, click etc), which may add significant load to our (and probably yours) server and network.
2 votes -
Add segmenting options to the list sending API to make it easier to send to a portion of the list
Add some options to segment list sending, or create temporary lists based on number of list members.
4 votes -
Add a throttling to allow for list sending to be sent over longer time period
When sending out to a large list, a user may sometimes wish to throttle the sends over a time period to avoid having too many responses or heavy web traffic all hitting at once.
4 votes -
Do not send duplicate email to same recipient in different list
Recipient in different list would receive only one copy of message, this is a basic ESP feature that everyone supports. But currently if a address is on more than one list than recipient will receive messages that are sent to each list, the only way to avoid this is to remove the email from other list.
Please add a workaround for this basic ESP feature.
5 votes -
HTML mailing list variables
Have the ability to put HTML into the mailing list template variables.
e.g.
{
html : "<strong>bold text</strong>"
}<html>
<body>
%recipient.html%
</body>
</html>Gets transformed into:
<html>
<body>
<strong>bold text</strong>
</body>
</html>2 votes -
Add "block" as a third option in spam_action with the Domains API.
Add "block" as a third option in spam_action with the Domains API.
3 votes -
Implement email notifications about selected issues
There are some delivery issues which usually warrant manual inspection and care by the administrative users. I feel that continuing to send emails to addresses that have ended up in the Bounces list would at least be one of them.
It would be convenient if the user could select certain common delivery issues like this and get a notification about them emailed to a specified email address. This email address could then be a mailing list for administrative personel who could look in to the error and see it they should act upon it.
It is possible to implement this…
8 votes -
Messages can be scheduled for a maximum of 7 days in the future.
Messages can be scheduled for a maximum of 7 days in the future instead of 3.
If it's due to spam perhaps you can get people to verify their bank account etc.
The reason why this would be good is because i plan my release of products every weekend. The items will be released daily and so can my email be sent daily automatically. Well i mean it's easier for me.
Thanks :)
7 votes -
Send logs into aggregators like Papertrail
I would love the ability to hook up my Mailgun account to a service like Papertrail (https://papertrailapp.com) so I can get access to emails more than 30 days old. We've had half a dozen cases in the last few weeks where we've needed to see if a receipt email was received, but since it was more than 30 days ago, we're out of luck.
10 votes
- Don't see your idea?