

The way the error is worded would make one believe it is a problem with that user's mailbox size but clearly that is not the issue. I deleted theseīut it had no effect on the frequency of the error message appearing. Move user's mail to a PST file and deleting the account, deleting the OST and re-creating the accountĪfaik the user does not send large amounts of bulk messages but does sent out sales-related e-mails that have brochures attached, I noticed about 4 of these that were stuck in the Outgoing folder. Increasing the default mailbox size in Exchange from 2 GB to 100 GB Other things I've tried that have not solved the problem: When the user logs in with OWA there are no Most of the other users that have mailboxes on the Exchange server are using Outlook from Office 2013 to connect and I'm starting to wonder if this issue is due to this user being on Office 2016 version. I know that the OST file is well under any limits as I've checked both the actual file size on the computer and the size reported by Exchange Management Shell. Deleting messages and emptyingĭeleted Items as the error suggests had no effect. However, the error keeps coming up with annoying frequency when the user has Outlook open. The user can actually send and receive just fine as I've had them send several test messages which were successfully sent and received.

Empty your deleted items folder from Outlook or delete messages from your mailbox to create more space.įile: \outlook\pstprx\storeas\utils\airsyncstatuscodes.h

Your mailbox has reached its maximum size limit at which you cannot send or receive any more content. The computer getting the error is not joined to our domain as they are an off-site user. When connecting to our Exchange Server 2013 Standard Version 15.0 (Build 847.32) - this is the on-premises version NOT online. I have one user only out of 25 total getting this error in Outlook (Home & Business 2016 installation) I have been researching this error for several days now and I see that it comes up a lot with users but my scenario is different.
