While developing an application that is accepting POSTs from Mailgun, I often develop a backlog of messages that have failed and that Mailgun continues to re-post. Would be nice to be able to filter in the logs and have an option to delete accepted messages that are "in queue."3 votes
Currently its pretty hard to add an additional ip to an existing pool that sends couple of millions emails per month, because the new ip will be 'cold' and considered spam. To avoid this it would be great if we could specify the load of every ip in the pool in percent. So adding a new ip but giving it only 3-5% of the traffic would reduce the risk and allow the ip to warm slowly.3 votes
Under Reporting Section, we have filters based upon domain and Tagging . Please provide the same filters options on Logs Section to provide better filtered out results.
Currently we have to type manually in Search bar of Logs section.2 votes
You should log config changes. This will allow problems to be tracked back to the source quicker and aid in fault diagnosis. E.g. we had a problem on 12/01/2017 what config changes did we make? Log what changed from what, to what, log who changed it and when.2 votes
Our e-mail addresses for Web site forms from time to time automatically get added to the Suppression list without knowledge, so therefore we stop receiving Web site form e-mails due to this. It would be good to have a way in the control panel to set our e-mail addresses to never be added on the blacklist for Suppression to fix this issue.2 votes
In SMTP you can set envelope recipients that are not listed in the To: header fields (think BCCs here).
We have a need for this to send unique emails to individuals, while having the To: header in their email client appear as if it was to a group that this user is a part of.
Currently, this is not possible via the Mailgun API, but only via SMTP. Since Mailgun recommends using the API, I would love to see this feature included so we can make the leap over to the API instead of using SMTP for these particular emails.3 votes
Currently there is no convenient way to get a list for each of your domains what sending IP address(es) are assigned to them, the only way is using the website drill down into each individual domain's details.
Exposing the IP Address(es) of each domain in the /domains API endpoint seems like a good solution.
Additionally being able in the website to enter a sending IP address on the domains listing page and it would show all the domains with that sending IP address assigned.5 votes
Handling inbound emails via Routes on Mailgun and forwarding them to another mailbox has the undesired effect of modifying third-party messages.
This has serious consequences:
* It breaks DKIM signature from third-party
* It tracks messages that are Inbound and tracking is in general undesired
Please at least make it configurable to disable Tracking on per-Route basis when it's enabled on the Domain.
Disable Tracking for domain and enable it explicitly per-message via API/SMTP header.2 votes
Incoming mail(verified by support) has a bug that when email is sent from an entity like email@example.com and is signed by att.com, and we receive it at firstname.lastname@example.org, when the route gets applied, it also incorrectly swaps out the att.com with mydomain.com security key invalidating the email security. Gmail then throws this email in the spam folder.
outbound email works fine since it comes with a FROM address of mydomain.com and so when mailgun swaps in a signedby, it is 100% correct since it is the MX record for mydomain.com and the security is all setup.2 votes
Looking at campaign reports for link performance there are URLs that appear as unique when it would be more helpful if they were grouped as a single URL for reporting purposes.
It would be nice to have some sort of grouping, filtering, searching or pattern matching system so that the following URLs would be counted as the same:
...and these too:2 votes
Most of my emails are sent to users in Sweden. The geographic coverage is not very useful for me since it only shows statistics for countries.
I would like to see more details here. I would like to see an estimated city for the recipients. I know the data will not be 100% accurate but it is way better than nothing.2 votes
From the Logs, be able to have MailGun reprocess an existing message through a configured route. This would help debug messages that are posted to routes on incoming mail.2 votes
It would be really helpful if there were a way to specify webhooks at the message level as well as the domain level. (Perhaps the message-level webhook, if present, would override the domain-level webhook.)
I send some emails from one server, and some emails from another. It would be really nice to be able to have the postbacks go to the right place. I can emulate the functionality by querying Mailgun about each message at intervals, but that's awfully inelegant.2 votes
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
Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.5 votes
I'd like some basic footer information included on every email that gets sent to a mailing list. Eg something like:
Thanks for using somethingsomething, visit us here <link>
Or call us anytime on <number>
It would be great to just use the current Templating functionality to attach a Footer Template.1 vote
- Don't see your idea?