Issues with Custom SMTP Sever

[HugoWiff]

Custom SMTP Server with Google Workspace stopped working for us about a week ago, I have double checked that the credentials are correct but I am receiving the error message '5.7.8 Username and Password not accepted. Learn more at 5.7.8 https://support.google.com/mail/?p=BadCredentials s18-20020a17090330d200b001bdeb6bdfbasm19876387plc.241 - gsmtp'

screenshot is attached with the settings configured (password was only deleted for screenshot)

 

[Alejandro_3CX]

Hi @HugoWiff I’m afraid that you need to change the email password to a stronger one (alphanumeric). Also make sure that the account is allowed for third-party applications to use it.

However, why not using the 3CX SMTP? It works out of the box

 

[Lee Cramman]

However, why not using the 3CX SMTP? It works out of the box

Sorry, not my thread but there are lots of reasons... But mainly blacklisting. Be that the over-eager blacklisting / lack of retries by 3CX SMTP or possible grey / blacklisting by the customer's corporate mail server (which may be outsourced and difficult to whitelist addresses). If you can't directly control either the blacklisting or whitelisting process then it's difficult to guarantee voicemail over email will be delivered reliably.

An SMTP account on whatever corporate system is in use neatly side steps blacklisting issues (as it will automatically be trusted by the mail server) and helps with information governance compliance (as mail does not pass through unknown servers).

For example in my org, any email communication that contains confidential patient information is supposed to only pass through our corporate servers. So if a voicemail has patient information in it, it shouldn't go via 3cx SMTP.