#Cant maximize screen zimbra desktop how to

TIP2: If an email is corrupted, it will probably show Unknown in the From field. That way you don't have to remember the emails. TIP1: Not to make a mistake, you can use a Snipping Tool, to make a screenshot of the emails you move. Then one by one, move the emails from the Inbox to the test folder to identify which one is the corrupted one. That means, the problem email is one of the fifteen. Repeat that until you are unable to login. After you can login (using Ajax), then move 15 emails from the test folder to the Inbox (you can move more emails if you like). Usually you don't need to move a lot of emails, because the issue have happened recently, which means the problematic email is somewhere in the last 1-2 days. If you are unable to login (using Ajax), then move 50 more emails. When that is done, logout and then login. Then go to the Inbox, and move from there 50 mails to the test folder. What you have to do is to first create a test folder.

When you login, you will be able to see all emails in the Inbox folder. Try to login with Ajax, you will get stuck, then click on the link to switch to the HTML version. Zmprob ma zimbraPrefMailInitialSearch in:inbox

#Cant maximize screen zimbra desktop how to

How to identify corrupted email in the Inbox.Ĭhange back the zimbraPrefMailInitialSearch attribute to its original value:.

If the folder is empty, the problem is most likely an email that contains invalid character/formatting. If you can login with Ajax, then when you check the Inbox folder, it will probably show empty, or an error will be produced when you click on the Inbox tab (check logs). Zmprob ma zimbraPrefMailInitialSearch in:sent That will change the default login folder from Inbox, to the Sent folder. The very first thing to do, even before you try to check the logs, is to change the zimbraPrefMailInitialSearch attribute for the problematic user to the sent folder. The below steps are to give you more ideas as to where to check. Sometimes, we may not see anything in the logs, and then we should relay on different troubleshooting. If there is nothing in the logs, you may consider enabling debug logging for the user, by following this wiki.

After checking these logs, you may have some idea as to what the problem might be and where to check. Then we can check the mysql_error.log, zmmailboxd.out,, nginx.log, myslow.log, audit.log, httpd_-xx-xx logs. The first place we would be looking is in mailbox.log. Run 'tail -f' for different logs, and reproduce the issue to collect clues as to what the problem might be. To troubleshoot this problem, we would first rely on log files from the /opt/zimbra/log directory. User enters his/hers login name and password, press the Sign In, but the login screen is stuck on loading. This article is a Work in Progress, and may be unfinished or missing sections.