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
After setting-up SES and smtp drivers with failover in that order, I have an issue where AWS throw an error but laravel does not failover to stmp (when I disable ses I can confirm that smtp work properly).
I understand how to fix the misconfiguration on AWS but would expect laravel to failover in that case.
The error is thrown by \Illuminate\Mail\Transport\SesTransport::doSend() and is a simple \Exception
As I understand it the failover works by catching any error here \Symfony\Component\Mailer\Transport\RoundRobinTransport::send(), but because the error thrown does not implement \Symfony\Component\Mailer\Exception\TransportExceptionInterface it is not catched.
I can make a pull request to change the error thrown by the SES driver to be catched but would like to make sure first that it's the correct way to correct that.
Steps To Reproduce
Setup laravel in failover with multiple drivers, SES first, with valid AWS credentials but a wrong configuration.
In my case I have an unvalidated domain, therefore SES refuse to send from a not verified email address.
The text was updated successfully, but these errors were encountered:
As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.
If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.
Laravel Version
10.19.0
PHP Version
8.2.6
Database Driver & Version
No response
Description
After setting-up SES and smtp drivers with failover in that order, I have an issue where AWS throw an error but laravel does not failover to stmp (when I disable ses I can confirm that smtp work properly).
I understand how to fix the misconfiguration on AWS but would expect laravel to failover in that case.
The error is thrown by
\Illuminate\Mail\Transport\SesTransport::doSend()
and is a simple\Exception
As I understand it the failover works by catching any error here
\Symfony\Component\Mailer\Transport\RoundRobinTransport::send()
, but because the error thrown does not implement\Symfony\Component\Mailer\Exception\TransportExceptionInterface
it is not catched.I can make a pull request to change the error thrown by the SES driver to be catched but would like to make sure first that it's the correct way to correct that.
Steps To Reproduce
Setup laravel in failover with multiple drivers, SES first, with valid AWS credentials but a wrong configuration.
In my case I have an unvalidated domain, therefore SES refuse to send from a not verified email address.
The text was updated successfully, but these errors were encountered: