geosharp

Hey there, I assume most folks are aware of this now, but in case not - ESS have got a patch out now for this - the KB mentioned by ajp233 has a link to download the installer or it should eventually turn up in SOLUS. Not on our SOLUS yet but I installed it manually and BACS remittances are working again. Cheers :-)

Aha, good to know that - i'd always wondered if the local council SIMS teams did any patch testing, good to know they do. Presumably ours is as well and it'll show up eventually. Cheers :-)

Hey, Short while ago I had a reply from our councils finance helpdesk forwarded to me: "I’ve just received an update from ESS about the case I raised re the BACS e-mailremittance problem. It looks as though there has been a patch released on SOLUS for you to download. We are pleased to advise that FMS Autumn 2022Workstation Patch 1 is being made available on SOLUS to resolve the issuesbeing experienced when sending email using Microsoft365 (Office365). This is being released now and should be available onSOLUS by the end of 07/12/2022. Please run a 'Check for Updates' to pull thisdown. Once installed to affected workstations this will allowthe sending of emails from within FMS without the errors previouslyexperienced. Could you ask your technician to try it when he gets the chance and let me know if itsolves the problem." Whilst it not shown up on our SOLUS yet, keep an eye out! Hopefully it does indeed fix it. Cheers :-)

Hey there, Yeah, ours still isn't playing ball. I've found out since that we pay for FMS support from the local council, i've been in touch with them and the lady I got freely admitted she wasn't technical enough to really be able to help but would get back to me, and to be fair she has. Important bit copied below: "I logged a call with ESS and they have got back to me today. They are aware of an issue with sending emails from FMS, where Office365 (Microsoft365) is the mailserver provider being used by the school to send emails. They believe this to be related to a change made by Microsoft, investigation is still ongoing. However, they have had a setting within O365 suggested as a possible fix for the email issue: In the properties for the mail box user can you please go to Mail > Manage email apps and check the option "Turn on use of legacy TLS clients" " I'd already tried what she suggested at the end earlier in week and it hadn't worked, but worth a pop, may work for you! :-)

Hey, I knew there was something i'd done Thursday that seemed to make it work - i'd ended up at the same article you linked, I recognised it when I opened it up. I've ran the diag again to check but it does seem i've re-enabled basic auth for POP3, i'm assuming that's what it uses. I'll try EWS as well and see if that does anything. Cheers :-)

Hey there, Apologies if this the wrong part of the forum for this, but as the problem seems to be Office 365 config I figured here. We've had email PO's and BACS remittances set up for a while in SIMS FMS and it's worked fine. However, it suddenly stopped working last Thursday, then very briefly worked Friday and now has stopped it seems entirely. I've been mucking around trying to get it working for most of yesterday but i'm stumped. We've got Google for Education so I bought a domain, verified it with google and created a google account there and that works, so it's not entirely an FMS thing. The settings i've got in FMS are: Mail Server smtp.office365.com Port: 587 Use STARTTLS Encryption: Yes Authentication Required: Yes Followed be an email and password that I know is correct as i've logged into it - i've also tried sending and receiving email on that account. The error i'm seeing from FMS is 'Failed to read beginning of SSL/TLS record. Client handshake failed. Failed to establish TLS connection.' Now, I remembered that office was depreciating TLS 1.0 & 1.1 so I hunted round on Microsoft's site and i've made sure SMTP AUTH is still on and legacy TLS and tried using the legacy SMTP address, as I strongly suspect that despite ESS suggesting otherwise FMS doesn't support TLS 1.2. Anyone any thoughts? Any help appreciated :-)