it should be easy to support "One-Click Actions" and "Go-to actions" and would be a really nice feature imo.

https://developers.google.com/gmail/markup/overview#gmail_actions

Please consider providing the timestamp, token and signature as http headers. Some frameworks such has JAX-RS provide the ability to validate an incoming request via interceptors. This is difficult to do with form data as it is processed later in the request.

Ideally this would be done similar to Twilio https://www.twilio.com/docs/security

Maybe an

X-Mailgun-Timestamp
X-Mailgun-Token
X-Mailgun-Signature

Based on this we could verify the request before actually decoding the form data.

Most Serial to Ethernet server devices use a POST method similar to the following:

Serial.println ("POST: http://domain.com HTTP/1.0");
Serial.println ("Host: domainhost");
Serial.println(Content-Length: xx");
Serial.println("");
Serial.println(Content);

I have used this method to post data to data logging web sites and would like to use the same method for emailing. Thanks.

Some gateways can track when a customer deletes an email. This is an important indication of the recipient's attitude towards the email received, especially for marketing emails, but also for other types.

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.

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 Jamin

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 :)

https://github.com/mailgun/talon/pull/23

Especially:
- mailing list recipients
- logs

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.

This would be a useful safety feature in the event that something goes wrong in user code that is pushing messages thru mailgun.

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?

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.

Add some options to segment list sending, or create temporary lists based on number of list members.

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.

Add "block" as a third option in spam_action with the Domains API.

Add the ability to track email sends (hourly) in the dashboard so they can be compared directly against opens. This would greatly improve the ability to assess best send times that garner the highest open/click rates for recipients by drilling down into open rate by the hour the email was sent.

my idea is the you shoukd add a support for Disabling /Enabling link tracking by adding a parameter infront fo the link.
the reason is thet somtimes like in "Please Remove Me..." the email address in the links is differenf for eache mail and therefor this is a uniq link. this info is not very useful when tracking a campagin.

Would be great to define the outbound IP address (of those in my pool), for which emails will deliver, upon submitting to the API.

Show the date an email address has been added to a mailing list.