4 ms·

Well.... thanks for ruining my weekend... Gonna be fun on Monday looking into this, talking with leads, and looking for Mailgun alternates.

• kxrm 5y ago
  If you pay for a static IP and tighten up your SPF records to just that IP rather than using Mailgun's include, you should be fine. It's bad that their service allows this at all, but it isn't the end of the world for all of their customers.
  • tehbeard 5y ago
    What trust do I have that a static IP would fix this? If the bug is before any routing to which server to send from takes place... then it'll just end going out on the static IP all the same..
    • kxrm 5y ago
      I was on the free tier so I don't know for sure, but I believe the whole point of the dedicated IP offering is you are the only customer who can use it. So long as your SPF records reflect just that IP SPF will remain in force if someone tries sending through one of the shared IPs as you. But if moving isn't a huge deal, there are plenty of recommendations in these comments of alternatives.
• welder 5y ago
  The Mailgun support also says DMARC records prevent this, when the reject policy is set to deny.