Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I removed some code pertaining to catching errors with PHPMailer objects.
Motivation and Context
Since PHPMailer objects can throw phpmailer exceptions, some error handling code is not needed because it is redundant. Since we catch all exceptions using a generic exception, getMessage() and ErrorInfo will provide the same message, but from different sources. Another reason to delete ErrorInfo is because if the error occurs in the initMailWrapper, a mail object will not exist, and therefore ErrorInfo will be useless. getMessage() would still be able to provide us with the same error response ErrorInfo would normally provide us, so ErrorInfo is not needed.
Tests performed
I (purposely) caused a mail-related error with only getMessage printing the error, and then with only ErrorInfo printing the error, and the messages were the same.
Types of changes
Checklist: