HEY..... partial success
I've reverted my mail settings from SMTP to the board's native php. Now these were what i was using anyway until a few days ago and they weren't sending activation emails. So, on the advice of my host helpdesk i changed to smtp using their own (new) mail provider, Soverin, and this didn't work either - i think this was (and still is) issues with the settings they have suggested including the SPF entries.
So i've recently updated from 3.3.2 to 3.3.14 and changed my php version to 8.1, the highest my host supports. Still no luck..... then i changed back to native php mail settings. I also deleted the file io_lock.lock from the Store directory on the advice of warmweer (see thread).
Result: I've now sent out test registrations from four different email addresses, and they've all received an activation email.

I've got to say at this juncture that i'm not sure whether that was due to reverting to the native php or deleting that io_lock.lock file.
BUT..... one problem: all four activation emails ended up in the respective SPAM folders. Is this a common problem with the Board php? I've used the mail testing app suggested by thecoalman above and got a 10/10 store, but it did note that the reverse DNS does not match with the sending domain. Now i'm guessing that this is because i have created a redirect so that mails being sent from my board using the mail addresses native to my host are then redirected to my Outlook email addresses so that i get to read all my mail without having to keep logging in to my host. Has anybody got any observations as to whether this is likely to be the cause of the mails ending up in the Spam folders? I'm still going to pursue getting the SPF entries sorted to give me the option of using the host's email provider via SMTP - especially if this reduces the likelihood of activation mails being flagged as Spam. I'll test and compare if i can get those SPF settings sorted with my host's helpdesk.
Anyway, things are decidedly moving in the right direction and as a bonus the problems finally prompted me to update the Board.
