Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Monterey Mail problems

I am running 12.6.2 macOS Monterey on a 2019 Mac Pro.


I began having problems some months ago with the content of the email not showing up, even after double clicking to open mail. Sometimes quitting mail, restarting, deleting accounts works, but the problems always recurs.


I've contacted Apple support, spoke to multiple senior advisors and screen sharing session, sent screen shots and files to Apple Engineering. Run in safe mode, created a test user, etc, taken every step the Apple techs asked, nothing has worked.


They told me there is a reported bug in Monterey Mail and the only fix is to upgrade to Ventura.


I am a Creative Cloud user, and Ventura is not even three months old, with many reported bugs and problems using Creative Cloud.


Any advice?



5 replies

Sorry you are experiencing this issue. Please consider the following. Ventura is working fine in most computers, including two of mine. Any new operating system will have some problems in some computers. Often, this is due to problems with other installed apps. Prior to release, all new operating systems are used and tested extensively by Apple test volunteers and problems are reported and resolved. You have a problem. I would do the upgrade to deal with it.


Have you worked with your email service provider to address their problem? I suggest doing so.

i would suggest to downgrade to macOS Monterey 12.6.1 , as that version has lesser bugs , atleast in network-office environment & in individual/professional run instance environment , from my/our side observations.


make sure you have TimeMachine software based full backup.


this earlier post shows how to download specific version , in command-line change the "10.15.7" , into "12.6.1". when the installer app download completes, then run the installer app.

if installer app does not want to install, then you may have to use boot-media or, downgrade to 12.6 , then upgrade to 12.6.1


Thanks for the reply.


I am not upgrading to Ventura because I use Creative Cloud, including InDesign, Dreamweaver, Photoshop, Lightroom, Illustrator, Acrobat, etc.


Creative Cloud has many issues with Ventura, which is less than 3 months old. Unless you are running Creative Cloud and using the same applications that I use, your experience with the new operating system really is not relevant. Other Adobe users have indicated problems. I use Connect Fonts to manage my fonts for InDesign.


I have more than one email service provider, they are not the problem. The email issue is the same with both providers, some emails do not render correctly in Mail.


The problem has always been Apple blames Adobe, and Adobe blames Apple. And it takes months before all the Adobe apps start working smoothly. This is an Apple bug, which they admitted to me.

Thank for the suggestion. I was not having the email problem in the earlier version (12.6.1) of Monterey.


However, when I tried to run it in Terminal:


$ softwareupdate --fetch-full-installer --full-installer-version 12.6.1


I got this message: -bash: $: command not found


It would be nice if Apple support could show me a method to install the previous version, but they want everyone upgrading to Ventura whether it makes for my business or not. I am nervous about downgrading to 12.6 then trying to upgrade to 12.6.1.


I guess I will just continue to use workarounds. But thanks for the help.

The "$" is not part of the shell-command , thats the prompt symbol in "Terminal" app (which is a shell-management app) , this symbol is used in guides / instructions / manuals etc , to indicate a user : run the command in a general shell.

Its similar to windows-command-line prompt, which has the ">" symbol as prompt indicator.

In unix/macOS/linux the "$" before a shell-command is indicating, you run the shell-command in a general shell/Terminal window initiated by your own user account , and if root access is needed temporarily, then use "sudo" in front of a specific command.

In unix/macOS/linux the "#" before a shell-command is indicating, you run the shell-command in a privileged shell/Terminal window initiated by privileged user "root" , so using "sudo" is not needed.


So do not use the 1st symbol "$" or "#" itself , when use/run a shell-command inside the Terminal app.



if a shell-command has the comment seciton after the shell-command in same line,

then dont use the # symbol in a shell-command, & remove the # symbol & remove all words after the hash symbol in that same line, before using the shell-command in Terminal app.

be-careful, sometime "#" symbol can be par of command, then keep it intact.



By the way , to setup configuration/settings related lines (also knows as config-command-line or config-command) in config/settings related ( *.cfg , *.ini etc ) files,

you will have to open the config file by using a text Editor software / tool , such as "nano", "vi", "gEdit", "TextMate", etc, and after copy-pasting config-lines, etc you will have to "Save" your new code/changes inside the text Editor software/tool, & then exit from editor.

When you copy config-commands displayed in a guide , & paste into the text editor,

you will/may see some config-command or some config-line has the "#" symbol as 1st symbol of a line,

then that symbol indicates, that specific line is a comment-line, & not a config-command line,

these lines explain whats doing what, etc.

In config line, the "#" symbol must be kept-intact if its the 1st symbol of a line, & some time the "#" will be used in end a config-command, to start a comment-section in same line, then the "#" symbol must remain where its used/placed.

Such comment/explanation line or comment/explanation section/portion at end of a config-command line , must start with the "#" symbol , inside a config file.

( there are other symbols for creating "comment" section/portion/line , but the # is just too popular & has become a convention for config files. )