I wasn't aware that this was something that changed, but I agree that it is unexpected.
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. However I would really appreciate a more machine-oriented reply in the API and documentation of which errors can occur. Now we have to string match for the correct errors and there are no way of knowing which errors can actually occur which is clunky and unreliable
I wasn't aware that this was something that changed, but I agree that it is unexpected.
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. However I would really appreciate a more machine-oriented reply in the API and documentation of which errors can occur. Now we have to string match for the correct errors and there are no way of knowing which errors can actually occur which is clunky and unreliable