> "I do understand that there are issues with trying to deliver obviously invalid emails and I don't really mind that the request returns a 400 error."
I agree that 400 Bad Request can be the response of an email address that is *obviously* invalid. E.g. "@" would be obviously invalid.
The problem here is the depth of the check that Mailgun performs. E.g. checking the DNS record of the domain to verify that it is associated with an email server. In my opinion that is extreme. It is also a check that isn't deterministic, i.e. it suddenly matters *when* you validated the address.
Doing such checks before actually sending is fine, of course.
Anonymous
In reply to Stenmark below
> "I do understand that there are issues with trying to deliver obviously invalid emails and I don't really mind that the request returns a 400 error."
I agree that 400 Bad Request can be the response of an email address that is *obviously* invalid. E.g. "@" would be obviously invalid.
The problem here is the depth of the check that Mailgun performs. E.g. checking the DNS record of the domain to verify that it is associated with an email server. In my opinion that is extreme. It is also a check that isn't deterministic, i.e. it suddenly matters *when* you validated the address.
Doing such checks before actually sending is fine, of course.