No UI message for failure of mail delivery if SMTP config is incorrect

[SanjaySiddarth]

Describe the bug
When the SMTP configuration is incorrect or the configured SMTP server is unreachable, SplitPro does not send a mail, but also does not show any error message in the UI. The only indication of the problem is an error written to the container logs.

To Reproduce

• Configure SplitPro with an invalid or unreachable SMTP server (e.g. incorrect host or port).
• Invite a user to a group
• no error message is displayed in the UI.

The logs:

splitpro  | Error sending email Error: connect ECONNREFUSED 172.28.0.3:1025
splitpro  |     at <unknown> (Error: connect ECONNREFUSED 172.28.0.3:1025) {
splitpro  |   errno: -111,
splitpro  |   code: 'ESOCKET',
splitpro  |   syscall: 'connect',
splitpro  |   address: '172.28.0.3',
splitpro  |   port: 1025,
splitpro  |   command: 'CONN'
splitpro  | }
splitpro  | Discord webhook URL is not defined in the environment variables. So printing the message to the console.
splitpro  | Message:  Error sending email: error.message: connect ECONNREFUSED 172.28.0.3:1025
splitpro  | error.stack: Error: connect ECONNREFUSED 172.28.0.3:1025
splitpro  |     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)

Expected behavior
If an email cannot be sent due to an SMTP connection or configuration error, the UI should display an error mentioning the email delivery failure.
Ideally, SMTP configs could be checked at startup

Screenshots
NA

App version
v2.1.5

Desktop (please complete the following information):

• OS: Ubuntu server

Additional context

The error is being handled internally, but the failure is not propagated back to the frontend. Displaying an error would make SMTP configuration problems much easier to figure out