Good day MoHeyns,

Thank you for your support post.

That’s a good question, but I think this discussion is starting to get beyond the scope of the Sage City forums. There are many factors that could play a role in this scenario and while other Sage City members may still offer input, I would like to invite you to work with our Sage Support Team per the hyperlink below or consider getting in touch with your local Business Partner for personalized assistance and troubleshooting of your exact scenario. 

Web Form People 300 Payroll/HR Support

Sage support has now on 2 occasions failed to come to a resolution.

The working theory is be cause sage 300 people uses TLS1.0 to send mails so i have installed .net 4.7 and edited the registry to use TLS1.2 and no im getting 2 things.

1. The error is now : The client and server cannot communicate, because they do not possess a common algorithm

2. The local method of sending mail is not working. If i change the mail server to local then it still uses the scheduler to send mail.

TLS1.0 has been depreciated for how long but sage still uses that to send mail. Sage support (PAID support) has no answers and in the mean time the company of 400+ employees aren't getting ANY sage notification emails.

So where am i supposed to go next?

Good day MoHeyns,

Thank you for your further feedback.

Kindly provide me the HD reference number for the case you logged as requested above, on which you were not provided a working solution, so that we may escalate this further to our Technical Operations Department for a foolproof resolution to your query,

Thank you 

Hi Jamie 

We have found the issue. After having multiple sessions with sage consultants we managed to get some answeres from a sage 300 developer. 

On the server is the sage and then as part of that there is a plugin or module called send or mailsomething. This is baked into the sage software from a code perspective. 

This part is where is the issue is, this send module is incompatible with TLS 1.2. 

Basically the sage 300 applicaiton cant use TLS1.2 which is absolutely shocking since the depreciation of TLS1.0 and 1.1 has been a long time coming and now that its affecting people now only have we logged a call with sage for this to be fixed.

Then the workarround or fix - no help from sage was received on this.
Install the SMTP relay service on any server and set it up with the details for MS exchange online.enable TLS and port 587 

Then change your sage settings to send to the relay server IP on port 25 with no user name and password and no TLS or SSL enabled. 

Current Work Around that I have on this is to have a scheduled script in SQL to run every 15 mins to change error status to new on emails, this then retry to send the email and eventually everything goes through.

Hello Diebaas01,

Please can you help me with the script.

Hi, here's the script

Update Notification.Mail
set Status = 'N'
where Status = 'E'

always make sure you have backups and that you are working in the correct Database before running any script

Hello DieBaas01 

Thanks for joining the community and offering your assistance to fellow members.

Tolulope , have you had a chance to review the script? If the answer proved helpful, please let me and the rest of the community know by clicking on "Verify answer."