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!
-
billing &databoard
I think the databoard &billing has error , we didn't send so much emails every day from 20th Apr. but your data-board show we sent 4-5K each day. actually we only send 1.5-2K each day!
1 vote -
Sign api key
When rotating API keys, always use the key the client used to authenticate to Mailgun in signing webhooks. The issue is that when a new key gets generated usually we cannot update it everywhere immediately so we use the old key for a period of time, but Mailgun starts signing webhook calls immediately with the new API key resulting in invalid signatures and loss of data on our side.
1 vote -
Analytics problem
Hi,
I have a question when using 'Analytics' tab.
I sent a lot of mails in 4/26. In Analytics tab I selected date '4/26', but the result said 'No tags were found with the filters you've selected.'
How could I solve this problem?Thank you.
1 vote -
Search All Log by email address
I would like to be able to search for an email address that might exist in any domain we have, not just the one selected in the dropdown. Some kind of search all option.
1 vote -
Sending
Cannot send anymore after 100 messages sent
2 votes -
SMTP
can you give me access to send it again?
SMTP username and password to send.
I accidentally deleted it in the code.2 votes -
Add AAAA record
Would it be possible to add an AAAA record for smtp.mailgun.org, so that those of us who use postfix can just leave the inet_protocols = all, which is the default setting? I've had this happen multiple times to multiple customers, because they upgraded their postfix package, and it reset the main.cf file. If you aren't paying attention, a lot emails will get stuck because of this.
2 votes -
IP is blocked on 4 diffirent places
HI there on my newsletter pre-check I get this for the Mailgun server IP:
Your IP 143.55.232.11 is blocked on 4 lists:
s5h.net: See http://s5h.net/rbl
dnsbl-1.uceprotect.net: IP 143.55.232.11 is UCEPROTECT-Level 1 listed. See http://www.uceprotect.net/rblcheck.php?ipr=143.55.232.11
dnsbl-2.uceprotect.net: Net 143.55.232.0/24 is UCEPROTECT-Level2 listed because 33 impacts are seen from MAILGUN-, US/AS396479 there. See: http://www.uceprotect.net/rblcheck.php?ipr=143.55.232.11
Sorbs.net: Spam Received See: http://www.sorbs.net/lookup.shtml?143.55.232.111 vote -
Incorrect date shown on Logs page on hover
On the Logs page, all date-times are shown in PST8PDT as indicated, but on hover-over, a date is shown in UTC.
1 vote -
Allow other per-domain API calls for domain sending keys
Allow other domain-based operations such as retrieving events for domain sending keys. It's nice to be able to have sandboxed API keys per domain for sending but it would be more powerful if it also allowed doing things like querying events for that domain, that way you could have one account with development/QA/production domains each with their own keys restricted to those domains.
1 vote -
Add tracking protocol as a parameter to PHP Mailgun API
Currently you can update the tracking protocol (http/https) via the Mailgun dashboard, and via the Maligun API. There is however, no support in the PHP SDK (https://github.com/mailgun/mailgun-php) as far as I am aware.
Is there any reason this can't be included?
1 vote -
When attempting to create a domain in via API, the error responses are not as verbose as in the client portal. there should be parity here.
Attempting to create an already existing domain via API does not return verbose error responses:
{
"message": "Domain not found"
}Creating an already existing domain via the client portal returns an error message that is a lot more informative:
Failed to create domain. Domain already exists in registry. Domain Name: domain.tld.
Parity between the two would be good.
1 vote -
Sending too fast?
I upgraded my account to foundation, why do I keep getting "you're sending to fast" emails???
1 vote -
Help
Im being billed but not yet using? Theres no answers on the Q&A and it's not letting me start a ticket
1 vote -
Unclear & DANGEROUS configuration instructions
😡 "Thanks" for the unclear message about MX configuration! It messed up my email setup so I've lost 2 days of emails!!!
OK, it says "if you've MX records for @example.com"… but I don't have that kind of records because it's on a managed server that probably do that in the background.
From a UX point of view, don't put first in bold "recommended for all domains, even if you are only sending messages" then discretely after "don't do it if it can mess up your emails"… that should be displayed in BOLD RED!!! Attract the attention of the user…
1 vote -
Increase limit of 1000 recipients per API call
Increase the number of recipients allowed in a single API or SMTP request.
Currently we have to manage our own throttling of email recipients to cope with sending limit of 1000 recipients per API or SMTP request. Will be good if Mailgun can handle the throttling on their backend and adjust the sending limitations.
1 vote -
There was an error loading your data
There was an error loading data.
1 vote -
always problem
Its always a problem with this page. just loading and loading. ALWAYS
1 vote -
I have successfully paid but my account is still locked
I have successfully paid but my account is still locked
1 vote -
RESTORE the old Resend functionality of auto-populating the address
When I click the cog to RESEND a bounced email, it USED TO fill in the bounced email address so that I could just click OK or make a quick edit to it, but now it comes up EMPTY so I have to retype the address from scratch. Can you please restore the previous functionality?
1 vote
- Don't see your idea?