6 results found
There is a way to create multiple logins for the same Mailgun account but we can't reuse an existing account. The error message is:
Error: Unable to invite user. User already exists
We need a way to manage multiple accounts under the same email, not having this is a total nightmare :\ We have this in Stripe, Twilio, SendGrid, Mailchimp, etc ...
There is no way I will ask my clients to forward me the "passcode" everytime I need to login on my client's account.111 votes
I hear you on the frustrations here. Unfortunately just about everything account related is tied back to user who created the account and their email address, which is currently a unique mapping across Mailgun, so it’ll take a bit of work to allow this functionality.
Until we’re able get this implemented, the workaround I use is plus addressing. For example, firstname.lastname@example.org and email@example.com allows me to essentially create multiple accounts using the same email (activation and notification emails will be delivered to firstname.lastname@example.org). The majority of the major Mailbox Providers (Gmail and MSFT included) support this.
Allow customers to pay via alternative payment types other than credit card.96 votes
Add Idempotency-Key to request ala Stripe's API. https://stripe.com/docs/api?lang=curl#idempotent_requests34 votes
-Please support DMARC on mailgun, and make it easy to deploy.
- Generate useful TXT entries (just like you already do for SPF and DKIM)
- Handle the DMARC reports
- Present DMARC reports in your control panel after decoding the ZIPed XML files the providers send.
- Convert DMARC failures (and successes?) into web hooks, events and log entries.131 votes
Mailgun bounce processing works great when a single sender is sending email to a broad audience. It does not work well when there are many original senders each with their own list of contacts.
- Company with 10 to 1000 employees.
- Company switches from a traditional in-house mail solution to Mailgun for all outgoing email.
- John, a typical employee in the organization, sends email to a customer, but spells the address wrong.
Traditional in-house system behaviour:
- John would get a Non-Delivery Report letting him know of his mistake. John would fix his mistake, and re-send the…70 votes
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…33 votes
We are currently in concept for a alert and notification feature to allow end user to configure alerts based on any number of sending metrics (e.g. hard bounce rate), notification channel (e.g. email) and filter by (e.g. specific sending domain, recipient domain, etc.).
Additionally notification may cover usage monitoring (e.g. send me an alert when I have reached 90% of my sending limit for the month).
- Don't see your idea?