I used to have 6 IMAP accounts on it when I first installed it.
Then I saw the CPU problem and uninstalled the app. A few days later I downloaded it again and only added one IMAP account, but I still happens.
So I don't think that could be the problem either. 🙁
Except if the 1 account now is the same one causing the issue before, to know you would have to configure 1 of the other 5 accounts (perferab;y on a different provider, and unconfigure the account you have there now, allow the new account to sync and see if it uses lots of cpu then....
If you close Airmail (but not completely stop), the CPU is almost fine.
What do you mean here, if you hide Airmail but don't quite the CPU is ok? If so that indicates possible issues with displaying the App, not the underlying IMAP etc processes.
Yes, if I hide it (but not stop it) the CPU is ok. If I open it again (and do nothing), the CPU goes up and down...
What you said in the last paragraph is exactly what I thought. The thing about push notifications is that you don't need the app to be open in order to get a notification from it.
I just don't like apps running in the background with no reason. Seems odd that push notifications require to run in the background on the Mac while all smartphones implement the concept of push notifications perfectly.
the only problem I have with Mail is that I'd prefer to send pictures/attachments as an actual attachment rather than in-line and I can't find anywhere to change that behavior
defaults write com.apple.mail DisableInlineAttachmentViewing -bool yes
defaults write com.apple.mail DisableInlineAttachmentViewing -bool false
Yes, if I hide it (but not stop it) the CPU is ok. If I open it again (and do nothing), the CPU goes up and down...
Just came home, opened Mac and Airmail started using 95-125% cpu (hadn't noticed anything unusual during the day). I couldn't see anything obvious other than it was using 4GB of virtual memory.
I closed and restarted the app and back to usual <1% cpu and 150MB of memory - even with the startup-sync activity so this definitely points to the app getting stuck on something during normal operation from time-to-time, at that level it may be a big, sudden memory leak and the cpu could come from that 😱
See, they have some serious work to do on the app still... 🙂