Differences

This shows you the differences between two versions of the page.

--- internet:mail:zimbra:zimbra_troubleshoot [2015/12/08 08:58]
127.0.0.1 external edit
+++ internet:mail:zimbra:zimbra_troubleshoot [2021/02/01 11:23] (current)
gcooper
@@ Line 1: / Line 1: @@
 ====== Zimbra Troubleshooting Tips ======
-Reboot the damn server:
+See also **[[https://www.sonoracomm.com/wiki/doku.php?do=search&id=zimbra|Other Zimbra pages in this wiki]]**
+===== Check Status and Reboot =====
 <file>
@@ Line 15: / Line 17: @@
 <note tip>Be patient. Zimbra takes a long time to start up and even longer for the status in the Admin Console to correctly reflect the current status.</note>
-<note tip>Probably the easiest way to avoid installation problems is to not mess with the firewall or change the SSH port before getting Zimbra tested and working.</note>
+===== Permissions =====
+Repair any potential permissions problems with files under ''/opt/zimbra'':
+<file>
+su - zimbra
+zmcontrol stop
+logout
+/opt/zimbra/libexec/zmfixperms --verbose --extended
+su - zimbra
+zmcontrol start
+</file>
+===== Message Tracking =====
+https://wiki.zimbra.com/wiki/Postfix-Queue-ID-vs.-message-id-MTA
+When a message enters the Postfix system [incoming or outgoing] it is immediately assigned a queue ID.
+Postfix/ZCS will most likely have a message leave the Postfix queue for other processing: amavis, filters, etc.  This will cause the message to get a new queue ID(s).  This can also happen if you were to requeue your messages by doing something like: ''postsuper -r''.  **You will need to note the message-id and ALL queue ID's to get the complete picture of what was happening for a particular email.**
+Find the ''Message ID'' in the message headers, then use it to find the associated ''Queue ID''s:
+<file>
+egrep "1544469627.145884.1473273227065.JavaMail.zimbra@mydomain.com" /var/log/zimbra.log
+</file>
+Then:
+<file>
+egrep "1544469627.145884.1473273227065.JavaMail.zimbra@mydomain.com|225D286F6F|3C18086F7A|B590286F6F" /var/log/zimbra.log
+</file>
 ===== DoSFilter =====
+**HowTo**: https://www.missioncriticalemail.com/2018/10/19/using-zimbras-dosfilter-and-failed-login-lockout-policy-together/
 http://wiki.zextras.com/wiki/ZeXtras_Suite_and_the_Zimbra_DoSFilter
@@ Line 34: / Line 69: @@
 su - zimbra
 zmprov gcf zimbraHttpThrottleSafeIPs
-zmprov gcf zimbraHttpDosFilterMaxRequestsPerSec
+zmprov gcf zimbraHttpDosFilterMaxRequestsPerSec  # Default 30
-zmprov gcf zimbraHttpDosFilterDelayMillis
+zmprov gcf zimbraHttpDosFilterDelayMillis        # Default -1
 </file>
@@ Line 43: / Line 78: @@
 <file>
-zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.0.65
+zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.2.0/24
 zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.0.66
@@ Line 120: / Line 155: @@
 ===== Server Status =====
+**Monitoring**: https://hazaq.me/zimbra/2018/02/02/Zimbra-Server-Status.html
 Check ''/var/log/zimbra.log'' and ''/var/log/zimbra-stats.log'':
@@ Line 153: / Line 190: @@
 ===== Mail Delivered to MTA But Not to Mailbox =====
+<file>
+tail -30 /opt/zimbra/log/mailbox.log
+</file>
 If your Zimbra server only has a private IP address and is behind a NAT firewall, you may see errors in ''/var/log/maillog'' or ''/var/log.zimbra.log'' like:
@@ Line 197: / Line 238: @@
 zmprov md <domain.tld> zimbraDomainDefaultCOSId <your-zimbraId>
 </file>
+===== Mail System Is Down =====
+Sometimes, the Postfix MTA may not start properly.
+Try deleting the ''.pid'' file and restarting Postfix:
+<file>
+cd /opt/zimbra/data/postfix/spool/pid/
+service zimbra stop
+rm master.pid
+service zimbra start
+</file>
+:!: **Wait** until Zimbra shuts down completely.  Then wait again for it to start up.
+The process ID file will be recreated when the MTA starts:
+<file>
+ll master.pid
+</file>

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools