Verifications
What do you think of our Email Validation API? Leave some constructive feedback here along with a brief description of your company’s use case for context purposes.
Please be courteous of others and upvote if you believe strongly enough in an idea!
4 results found
-
Validation Statistics
Currently there are zero stats for validations. My company was using this for all user input to validate the email addresses, after a few months we wanted to see how many users were not able to complete our forms based on this. But there are zero ways to accomplish this short of storing every call and response to the validation system on my end.
1 voteI’m happy to inform that you may see validation statistics on the validations usage page in the control panel (https://app.mailgun.com/app/email_validations/usage).
-
Fix the did_you_mean on email validations
The didyoumean described in your API for email validations never works, not even with the example "john@yhoo.com" displayed in your link https://www.mailgun.com/managed-validation/
1 vote -
Add an API entry point to check if an email belongs to a well-known temporary/disposable email provider
Add an API entry point to check if an email belongs to a well-known temporary/disposable email provider.
Currently, if we want to filter out disposable email address we have to monitor corresponding domain manually based on our rejection logs.
Given its position, Mailgun has probably better ways to identify disposable email address domains -- either through manual monitoring of the disposable mail offering or by cross-compiling the rejection logs of its customers.
2 votesOur responses now include a ’ is_disposable_address’ field to indicate temporary/disposable addresses.
-
Add an API for validating email addressess
Add an API call for validating email addresses (i.e. checking whether the domain is valid, the username exists, the mailbox is not full, etc..) similar to kickbox.io and make it affordable/free to use :)
3 votes
- Don't see your idea?