when sending (smtp) & receiving (Receiving Route) via Mailgun, within the same domain, the smtp client's ip address is not included in the POST parameters.
It would be very helpful if we could captre that ip address1 vote
Currently, the stop() action merely stops all subsequent routes. The email that matches the conditions is still processed (and therefore charged). As such, a potential attacker (say a determined competitor) can inflict a huge bill on a mailgun domain by sending a large amount of emails to that domain.
My suggestion is to have an action that will ignore a sender / sending domain entirely and refuse to accept some emails with the action.6 votes
Cleaner pricing verbiage around Routes on the pricing page or FAQ.4 votes
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.20 votes
- Don't see your idea?