38 results found

1. Add unsubscribe footers to emails sent via "everyone" / "members" mailing list

   Currently, if you set up a mailing list, add people to it and select the access level to "everyone" or "members" you have a good old fashioned email discussion list where people use their regular email clients to access (ie we are not talking about programmatic access here).

   But - even when you enable "unsubscribes" in the mailgun admin - unsubscribe links are NOT appended to each email received via the list.

   After a lengthy discussion with support they tell me this is as the system is designed and the footer only gets added if people send via Mailgun's SMTP.

   This seems odd to me - people using their own email clients won't usually use Mailgun's SMTP. So would it not make sense to append the unsubscribe link to all messages sent via an email list not least so someone can get themselves off the list if they want to?

   Currently, if you set up a mailing list, add people to it and select the access level to "everyone" or "members" you have a good old fashioned email discussion list where people use their regular email clients to access (ie we are not talking about programmatic access here).

   But - even when you enable "unsubscribes" in the mailgun admin - unsubscribe links are NOT appended to each email received via the list.

   After a lengthy discussion with support they tell me this is as the system is designed and the footer only gets added if people send via Mailgun's SMTP.

   … more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Mailing Lists  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. The final failed retry event for a no MX message should have permanent severity.

   When a message is sent to a domain without an MX record (498), mailgun attempts to send the message for up to 8 hours. Each attempt will be recorded as a failed event with severity = "temporary". The reason is set to "generic" for each attempt except the final attempt which is set to "old".

   This final attempt failure event should have severity = "permanent" so you can use the Permanent Failure webhook to observe this dropped message.

   Currently, you must also use the Temporary Failure webhook and inspect the reason property to see if the temporary failure is effectively a permanently dropped old message.

   When a message is sent to a domain without an MX record (498), mailgun attempts to send the message for up to 8 hours. Each attempt will be recorded as a failed event with severity = "temporary". The reason is set to "generic" for each attempt except the final attempt which is set to "old".

   This final attempt failure event should have severity = "permanent" so you can use the Permanent Failure webhook to observe this dropped message.

   Currently, you must also use the Temporary Failure webhook and inspect the reason property to see if the temporary failure is effectively… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Webhooks  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Give ability to create sandbox for EU region

   Otherwise, it's quite hard to test own integration with Mailgun API when you develop a solution for a big number of clients who are required to use EU region.

   14 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Domains  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Routes Pricing

   Cleaner pricing verbiage around Routes on the pricing page or FAQ.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Routes  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Revert recent change regarding 400 Bad Request on non-working email addresses

   Mailgun provides an excellent service. However, a recent change was made to the API: 400 Bad Request is returned if the address is not valid.

   The validation is a deep check that is not commonly performed (in my experience), including checking the domain for a MX record and effective TLD names (using https://publicsuffix.org/list/effective_tld_names.dat).

   The issue with this is

   1) There are no clear distinction between an invalid API request and invalid content. E.g. you get a 400 bad request if a required parameter is missing and if the email address is invalid

   • Currently the documentation states: "Bad Request - Often missing a required parameter" (https://documentation.mailgun.com/en/latest/api-intro.html#errors)

   2) The API message (HTTP body) contains no error codes. Which makes it less suitable for containing a vast amount of different poorly related errors

   3) Implementation making the request to the API gets mixed with implementation handling bounces and dropped messages

   • In my case, we have a stable implementation that uses the API. A bad request is not expected and a serious indication of a breaking change to the API, since the usage of the API is stable

   • Now we need to parse strings such as "'to' parameter is not a valid address. please check documentation" to detect problems with the content, even though we also have API hooks established

   • The lack of separation of issues is a problem

   The suggested solution

   a) Accept the message (200 OK from the API)

   • Keep the distinction clear: a bad request is only about the API (the abstract meta only) - never about content itself

   b) Drop the message immediately and invoke API hooks

   • Please note that this is not about "drop immediately or wait and retry"

   • The only difference is: how is a immediate drop communicated? It should be communicated via the established API hooks (single channel with single purpose) and not via API response codes "just because the API connection is still active"

   • Compare this to suppressions: whether an address is suppressed or not is something known when the API is called. But it's not communicated via a 400 Bad Request or a 418

   Finally, quoting RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.1)

   "The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)"

   Please keep the layers separated.

   Mailgun provides an excellent service. However, a recent change was made to the API: 400 Bad Request is returned if the address is not valid.

   The validation is a deep check that is not commonly performed (in my experience), including checking the domain for a MX record and effective TLD names (using https://publicsuffix.org/list/effective_tld_names.dat).

   The issue with this is

   1) There are no clear distinction between an invalid API request and invalid content. E.g. you get a 400 bad request if a required parameter is missing and if the email address is invalid

   • Currently the documentation states: "Bad Request -… more
   24 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Allow modifying the return-path of routed emails to allow better support of email auto responders.

   Right now if you receive an email that you are forwarding with a route to gmail, Mailgun sets the Return-Path header to a bounce email. This does not play nicely with vacation reponder systems (namely Gmail). Those systems respond to the Return-Path and the auto-response doesn't go to the intended recipient. I'd like the ability to override the modified Return-Path and set it to the from/reply-to email.

   21 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Routes  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. API Key Permissions/Restrictions to Reduce the Impact of a Leaked Key

   Security Feature:

   It should be possible to restrict the call types that your API key is able to make in order to reduce the impact of a leaked/breached key.

   For example, if my API key is accidentally exposed, an attacker could then go on to exfiltrate data from my account.

   If it were possible to lock down your API key so that it can only make certain call types, the impact of such a breach would be drastically reduced.

   For example, I could lock down my key so that it is only permitted to add/send emails to a particular mailing list. If the key were to be breached, the attacker would only have limited access, hopefully preventing a full-scale breach.

   Security Feature:

   It should be possible to restrict the call types that your API key is able to make in order to reduce the impact of a leaked/breached key.

   For example, if my API key is accidentally exposed, an attacker could then go on to exfiltrate data from my account.

   If it were possible to lock down your API key so that it can only make certain call types, the impact of such a breach would be drastically reduced.

   For example, I could lock down my key so that it is only permitted to add/send emails to a particular mailing… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Security  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Enable MailGun Api to send email with multiple BCC email addresses only.

   It's a common scenario when you want to send an email and have a list of recipients which for business purpose needs to be in BCC.

   Currently the error which comes from the MailGun Api is "'Bad Request - 'to' parameter is missing' error."

   Here are some StackOverflow threads about this
   * http://stackoverflow.com/questions/28503099/how-to-send-mail-only-to-bcc-with-mailgun-php-api
   * http://stackoverflow.com/questions/34400386/do-i-have-to-specify-a-to-recipient

   25 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  6 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Allow wildcard and full domain suppression

   Allow adding address such as the following to suppress lists so that known bad domains can be preemptively blocked.

   test*@baddomain.com
   *@extrabaddomain.com

   18 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Domains  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Get stats by SMTP credentials

    Hello,

    I think it would be interesting (from a stats perspective) if you can provide another API endpoint to get the current stats by domain and credentials.

    An example:

    Imagine the domain.com has 3 SMTP login:
    - postmaster@domain.com
    - newsletter@domain.com
    - autoresponse@domain.com

    Now we can get stats from domain.com (so we can get the domain has sent 300 messages), but we don't know if we have sent these messages using the autoresponse@domain.com account or using newsletter@domain.com or any other account that we can create.

    If you can consider this new feature I think will be nice from a Stats and Marketing perspective, to know how the company is in touch with the registered users.

    Thanks for your time.

    Cheers,

    Hello,

    I think it would be interesting (from a stats perspective) if you can provide another API endpoint to get the current stats by domain and credentials.

    An example:

    Imagine the domain.com has 3 SMTP login:
    - postmaster@domain.com
    - newsletter@domain.com
    - autoresponse@domain.com

    Now we can get stats from domain.com (so we can get the domain has sent 300 messages), but we don't know if we have sent these messages using the autoresponse@domain.com account or using newsletter@domain.com or any other account that we can create.

    If you can consider this new feature I think will be nice from a Stats and… more

    26 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SMTP  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Accept attachments encoded as Base64 strings in the "/messages" API endpoint

    It might be helpful for some users if the "/messages" API endpoint would accept attachments as Base64-encoded strings, with a name and content-type described somehow.

    16 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. API : Add an API method to download attachment for inbound emails.

    Right now mailgun SDK provides no method to download attachment given we have the URL. Only method is to download the attachment via language specific libraries like open-uri for ruby and we have to pass parameters for authorization. It would be great if there is a pre-built method to download attachments easily

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. implement a test api key

    In Mailgun you should be able to use a test api key to experiment with Mailgun's API. No mail should be sent, but webhooks should trigger normally and you should be able to generate synthetic bounces and complaints without impacting your reputation.

    This also lets the developer to setup a development environment that is similar to the production environment without the risk of sending any mails by misstake.

    54 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Prevent duplicate emails to same recipient

    We had a bug on our end that sent the same message to the same recipient thousands of times—resulting in thousands of spam reports while we were oblivious until months later.

    While there are things we could do on our end to improve quality control and ops, etc., it would be amazing if Mailgun could provide a duplicate detection feature. I'm imagining saving a hash of content for sent messages, and catching any time we repeat the content to any recipient. A repeat could be prevent, or an alert sent, or both.

    29 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Let me pay extra to get > 30 days log retention

    We would like to pay you guys real money to have the option to extend our log retention...there have been many cases where we need more than 30 days, and we dont want to setup webhook or anything external...your UI is perfectly good!

    ...you like money right

    28 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Logs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Bulk delete mailing list members via API

    Currently the API allows POSTing a CSV list of users to be added to a mailing list.

    I would like to POST a list of users in CSV who should be deleted from a mailing list

    17 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Mailing Lists  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Unsubscribe page for users (Mailing Lists)

    Make a template editing unsubscribe page (use this template in the mailing lists). Suggest using the editing unsubscribe page for use in various languages ​​(e.g. Russian, French, German, etc.), similar to the design of the main site, and more.

    24 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    8 comments  ·  Mailing Lists  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Add an md5 hash to the attachment object in the API

    I would like to save myself from having download an attachment if I already have a matching file stored locally.

    Our organisation sends out alot of product brochure that are mostly all identical.

    Rather than download this attachment in our application, I would use the copy I have on hand. Saving alot of bandwidth/server load

    29 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close