-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing IsValid email validation causes issues after upgrading from 4.12 to 4.20 #385
Comments
Hey. What endpoint are you calling? |
This result is from the maligun website: Mailgun -> Validate -> Single Validation . The tool there calls: https://api.mailgun.net/v4/address/validate?address=xyz%40gmail.com. The Golang client seems to call the same endpoint. |
I see. I added engagement data and deprecated the v3 validation in v4.14.0 and v4.15.0. I'll contact the backend team and ask if they could add |
Caused by #218 |
Fixed in https://github.com/mailgun/mailgun-go/releases/tag/v4.22.1, but you should consider switching to |
Dear mailgun-go contributors,
We recently upgraded mailgun-go from v4.12 to v4.20. With this change the IsValid parameter seems not to be filled at all anymore and leads our code to reject any new registration. Upon investigation and as stated in the issue #265 this might be caused due to inconsistencies between the api response and what mailgun-go expects to read. This seems to still be an active issue in newer versions.
Here is the actual api response:
Is the IsValid parameter deprecated? Or can this issue be fixed by Mailgun?
Greetings,
Jacob
The text was updated successfully, but these errors were encountered: