russjones

6 ms·

1. 31.▲
   by russjones 13y ago

   Check out the /parse endpoint for our API, it does exactly what you want: https://api.mailgun.net/v2/address
2. 32.▲
   by russjones 13y ago

   Hi Zikes, that's actually a bug, thanks for finding it. I'll fix it, and yes, that will soon be marked as valid.
3. 33.▲
   by russjones 13y ago

   Hi airnomad, I'm the developer of the validation service here at Mailgun. I can confirm that we do not store email addresses. The parser runs completely in memory and no address is persisted after the request is complete.
4. 34.▲
   by russjones 13y ago

   Hi fsckin, example@example.com fails because while we do fallback to A records, no mail exchanger responds to us, so no one can actually receive mail at that inbox which is why we mark it as invalid.
5. 35.▲
   by russjones 13y ago

   Hi cleverjake, I'm the developer of this service at Mailgun. You can't actually register "email with spaces"@gmail.com or "very.unusual.@.unusual.com"@mail.yahoo.com with Google or Yahoo. Both addresses pass pu
6. 36.▲
   by russjones 13y ago

   I only have performance numbers for the parser right now, and on average it takes about 0.07 milliseconds to parse and validate an address. That's the pure RFC syntax part. The longest part of validation service is DNS checks, but once
7. 37.▲
   by russjones 13y ago

   Hi Zikes, I'm the developer of this service at Mailgun. Nice to meet you. We've been using this service at Mailgun during testing and we've reduced bounce rates by 5%. That might not seem like a signficant number, and it may