You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally, there should be a way for the email backend to gracefully ignore invalid email addresses rather than having this result in a hard error.
Alternatively, at the very least the email backend should catch responses resulting from illegal email addresses and return them as an exception that can be caught. Right now illegal email addresses raise the boto.exception.BotoServerError request, which means that any code sending out emails would have to be tightly coupled to the backend.
My recommendation would be a global setting, by default true, which ignores these errors and instead outputs a warning message (ideally specifying the illegal email in question).
I'm happy to code this myself but wanted to run it by the developers prior to writing the code.
The text was updated successfully, but these errors were encountered:
Hi Jordan, thanks for your insightful note here. If this approach is not too tightly coupled with the internals of AWS (and thus likely to break easily within <1yr), then I say go for it. Basically, I would think it's worth the effort if the solution is relatively robust since Boto/AWS evolve over time as well.
And thanks also for offering to code this up! I'm willing to do a review, and please include tests.
Ideally, there should be a way for the email backend to gracefully ignore invalid email addresses rather than having this result in a hard error.
Alternatively, at the very least the email backend should catch responses resulting from illegal email addresses and return them as an exception that can be caught. Right now illegal email addresses raise the
boto.exception.BotoServerError
request, which means that any code sending out emails would have to be tightly coupled to the backend.My recommendation would be a global setting, by default true, which ignores these errors and instead outputs a warning message (ideally specifying the illegal email in question).
I'm happy to code this myself but wanted to run it by the developers prior to writing the code.
The text was updated successfully, but these errors were encountered: