Hello everybody Just a quick notification for the benefit of anybody who may have tried to post to this group over the last few hours.
As a result of a particularly aggressive system update on the primary server machines here. Neither of them was allowing the Mail Service API to communicate with any other machines when the update was completed. Thus, outbound mail wasn’t possible, and inbound connections were being refused. I have worked hard for most of today trawling through numerous logs to find out where the blockage was. After a great deal of. Effort, much swearing and cursing, and an even bigger dollop of bad-mouthing certain software engineers, I am pleased to be able to report that, finally, my efforts paid off. The services are now all back up and running. Therefore, please accept my apologies for any inconvenience caused. I can assure you that my patience with automated update processes was wearing extremely thin by the time I came across the log entry which told me where the issue was hiding. I then had to log into the machines as “Root”, and initiate a couple of quite complex Terminal commands to overcome the new default settings which a certain software producer has decided are appropriate. Put simply, they are in the process of removing all of their open source components from the Server applications which they are rolling out for a not too distant update. Whilst that in itself does not worry me, as I don’t use their apps anyway, They decided to block some third-party apps from accessing the TCP/IP stack. Therefore, the service was not visible as far as the mail server we use was concerned. And this prevented it from communicating with the outside world, or even with the other machines on the local network. Anyway, I’m delighted to be able to report that this issue has been squashed. I have also submitted system reports to the software engineers because you can bet your life I won’t be the only one affected by this change. OK, by all means destroy your own server application. But really, there’s no need to make it impossible for other third-party developers to access the services. OK, rant over. We’re now up and running and I’m about to go and get my much-needed brunch/afternoon Tea. Seriously though, my sincere apologies for any inconvenience caused. This wasn’t in any way an error on my part, but at least we’re fixed now. Gordon ======================================== My compliments and kindest regards Gordon Smith: <gor...@mac-access.net> Accessibility & Information Technology Support Specialist.. This Message Was Created Using 100% Recycled Electrons. If you can avoid printing it, please do so. Think of the environment, save a tree! Contact: Twitter: @maciosaccess • UK Free Phone: 0800 8620538 • UK Geographic / Global: +44(0) 1642 688095 • UK Mobile/SMS: +44 (0) 7804 983849 • Vic. Australia: +61 38 82059300 • US/Canada: +1 646 9151493 ----------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
