Add failover transport to MailSetting
@mjauvin are people able to configure the transports through the backend as well as use the failover transport?
@mjauvin are people able to configure the transports through the backend as well as use the failover transport?
No, they would need to configure the other mailers in the config
As I wrote in discord:
<@164272636988227584> I'm thinking we should move away from the SettingsModel behavior for the MailSetting model and have an active record instead (for the default mailer). That would allow setting multiple records for the different transports to support the failover (and roundrobin in Laravel 11)
@mjauvin are people able to configure the transports through the backend as well as use the failover transport?
No, they would need to configure the other mailers in the config
All mailers can be configured through the backend as usual, and they are all saved together. Therefore, in theory, you should first configure the individual mailers, then select and configure the failover, and finally save everything in a single action.
From a user perspective, it would probably be more intuitive if the configurations of the selected failover mailers were visible, preventing them from being "hidden."