-
Notifications
You must be signed in to change notification settings - Fork 16
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
"invalid addresses" exception too broad #160
Comments
That log looks like the debug log. What is the full Java stacktrace with exception names? |
It is not a debug log since a real exception during mail sending is thrown...
I know it is still the javax version of mail since we just recently upgraded to angus mail (but not productive yet) |
Ok that helps. The source of the behavior is in the SMTPSendFailedException API docs:
We just need to dig into the logic to see if it was incorrectly was added to invalid list instead of the unsent list. |
I recently got lots of error messages from jakarta/angus mail:
Invalid addresses
but on further inspection (most of) the addresses were correct and valid. I had to dig through a lot of exception causes until I got to the real issue(s). Those were for example:It seems that "invalid addresses" is some kind of default or fallback error message, which is however incorrect in certain (many?) cases.
Would it be possible to use a different error message like
Error sending mail
in case no clear or an unknown error code is used.Ideally (optionally) the cause from the server would be great:
The text was updated successfully, but these errors were encountered: