I remotely accessed the client's system and it appears that the issue has been resolved by utilizing the classic version of Outlook rather than the new Outlook.