It seems that it is Microsoft is deliberately causing the 'bouncing' of a percentage of emails if using Microsoft Outlook under SMTP - all other email clients are currently unaffected. It is a security restriction that they have created to get Windows TLS email security pushed to a later version (TLS 1.2). Note that it ONLY affects the use of SMTP button and not the Outlook one.

"Exchange Online will begin rejecting a small (unspecified) percentage of attempts to make SMTP connections using TLS 1.0 or 1.1 and issue this error message -

421 4.7.66 TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2. Visit https://aka.ms/smtp_auth_tls

This is a temporary error and clients can retry the connection. Exchange Online will block only a small percentage of connections it?s likely that the next attempt to connect will succeed. However, that small percentage of declined connections will increase over time to gradually make it more painful for clients using the older protocols to connect to Exchange Online. As Exchange Online declines more connections, clients will experience delays in transmitting email. In some cases, depending on the client?s error handling, email might not get through until someone updates the client to handle frequent retries (or upgrade the client to TLS 1.2."

The source code of the sent emails from Loadmaster indicate that they have ALL been sent under TLS 1.2

Until this annoying situation is resolved we suggest using ?relaying? to get around the issue.

We opened up a Google gmail account then linked our email address to it. We then used the gmail SMTP server settings instead of Outlook and not a single email ?bounced?.

Other relaying systems should work as well, such as smtp2go.

See our PDF on how to use gmail in Downloads on our web site - Outlook_SMTP_TLS_1_2.pdf

Norman
 

We have started getting these.

It's BT. Text to speech convertor. Someone sends a text to your phone and this converts it to speech.

It can be a real nuisance and it can be spoofed. Call 0800-5875252 to stop it.

Norman
 

You get this message when performing apt-get update

1. Look in /etc/resolv.conf using nano

Add nameserver 1.1.1.1 to the bottom of the list

2. Look in /etc/apt/sources.list

Alter mirrordirector.raspbian.org to legacy.raspbian.org

Norman
 

I found a lot of instructions on the internet about how to do this but many were incomplete or were simply just wrong.

The only way I got it to work was to add these lines to config.txt on the existing SD Card :-

program_usb_boot_mode=1
program_usb_boot_timeout=1

Then reboot. This tells the Pi to check for other boot devices.

Once done, in terminal type vcgencmd otp_dump | grep 17:

The output should say 17:3020000a where the 3 indicates that USB boot is enabled.

Now plug the SSD into a computer and using the Raspberry Pi Imager create a new image on it.

Plug the SSD in and remove the SD card. Reboot. It should now work.

I tried to use the SD card copier to copy the SD card image onto the SSD and it didn't work. I kept getting 'Kernel panic-not syncing: VFS: unable to mount root fs on unknown-block(179,2)'

Apparently if you have a Pi 3 (not the B) then you need to format a SD card and just put the file bootcode.bin onto it (available from Pi site). Then put this card in the SD card slot. This tells the Pi to boot from the SSD.

Norman
 

If you have a new Chromebook and want to use Linux then you may have an issue. I had problems on my Asus C423 and had to research the issue as they didn't have an answer as to why it wouldn't load.

Found this on - https://www.androidpolice.com/2021/07/08/you-might-not-want-to-update-your-chromebook-to-the-latest-chrome-os-release-just-yet/

Google has pulled the latest version of Chrome OS 91. Reports have been emerging that some Chromebook owners are experiencing significant performance regressions on Chrome OS version 91.0.4472.147, the latest stable release. However, in the process of pausing the update on devices, Google has introduced another problem ? you can no longer install Linux on what has now become the latest release again, version 91.0.4472.114.

After pulling the problematic update to version 91.0.4472.147, Google is now pointing to v91.0.4472.114 as the most recent stable release. However, it looks like the Linux installer app hasn't received the memo regarding the pulled update yet. As reported by Chrome Unboxed, the Linux installer checks if you're running the latest version of the OS before it runs, and it looks like Google's servers still claim that version x.114 isn't the latest anymore, prompting users to update their Chromebooks. Since version x.147 is no longer available, that's not possible ? x.114 is simply the latest release now. Hence, you can't install Linux on the current release of Chrome OS 91 right now.

I had to tell Asus about this as they clearly didn't know.

UPDATE - THIS HAS NOW BEEN FIXED

Norman
 

Next meeting 7pm Wednesday 21st July, 2021 at the Lincoln Bowl, Washingborough Road, Lincoln LN4 1EF.

Norman
 

If you are doing a large global pricing update and your data is on a network then there is a quicker way of doing it.

Make a note of where your data is currently located. This appears at the top of the main screen.

Create three new directories on your local drive C: and call then MyOldBackup, MyNewBackup and MyData.

Ensure TPN Invoicing is not being updated and don't allow any changes while you carry out this procedure.

Go into Utilities and Backup. Backup your system to C:\MyOldBackup

Once done go into Utilities and Datapath. Alter the data directory to C:\MyData

Now go into Utilities and Restore Data.

Locate the file called BACKUP.ZIP in C:\MyOldBackup and restore this. You are now working with your existing data but on the local C: drive.

Perform your pricing changes.

When done go into Utilities and Backup. Backup the data to C:\MyNewBackup

Now go into Utilities and Datapath. Alter this back to your original network location.

Go into Utilities and Restore. Pick the file BACKUP.ZIP from C:\MyNewBackup and let it restore.

Your amended data is now on the network drive. You have a copy of the original data in C:\MyOldData

Updating on a local drive can be much faster than the network.

Norman
 

Apple do not allow all older models to be updated to the latest version despite the fact that they are powerful enough.

If you get this then search for PATCHED SUR on the internet. This allows a different method of updating. My 2013 Macbook Pro has updated to Big Sur with this quite happily.

It gets round the software restrictions.

Norman