Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » internet » mail » zimbra » zimbra_troubleshoot
Trace:
internet:mail:zimbra:zimbra_troubleshoot

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
internet:mail:zimbra:zimbra_troubleshoot [2016/10/13 11:04]
gcooper 		internet:mail:zimbra:zimbra_troubleshoot [2021/02/01 11:23] (current)
gcooper
Line 1: Line 1:
 ====== Zimbra Troubleshooting Tips ====== ====== Zimbra Troubleshooting Tips ======
 +
 +See also **[[https://www.sonoracomm.com/wiki/doku.php?do=search&id=zimbra|Other Zimbra pages in this wiki]]**
  
 ===== Check Status and Reboot ===== ===== Check Status and Reboot =====
Line 14: Line 16:
  
 <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>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 ===== ===== Permissions =====
Line 34: Line 34:
 https://wiki.zimbra.com/wiki/Postfix-Queue-ID-vs.-message-id-MTA 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.**+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: Find the ''Message ID'' in the message headers, then use it to find the associated ''Queue ID''s:
  
 <file> <file>
-egrep "1544469627.145884.1473273227065.JavaMail.zimbra@virtualarchitects.com" /var/log/zimbra.log+egrep "1544469627.145884.1473273227065.JavaMail.zimbra@mydomain.com" /var/log/zimbra.log 
 +</file>
  
-egrep "1544469627.145884.1473273227065.JavaMail.zimbra@virtualarchitects.com|225D286F6F|3C18086F7A|B590286F6F" /var/log/zimbra.log+Then: 
 + 
 +<file> 
 +egrep "1544469627.145884.1473273227065.JavaMail.zimbra@mydomain.com|225D286F6F|3C18086F7A|B590286F6F" /var/log/zimbra.log
 </file> </file>
  
 ===== DoSFilter ===== ===== 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 http://wiki.zextras.com/wiki/ZeXtras_Suite_and_the_Zimbra_DoSFilter
Line 61: Line 69:
 su - zimbra su - zimbra
 zmprov gcf zimbraHttpThrottleSafeIPs zmprov gcf zimbraHttpThrottleSafeIPs
-zmprov gcf zimbraHttpDosFilterMaxRequestsPerSec +zmprov gcf zimbraHttpDosFilterMaxRequestsPerSec  # Default 30 
-zmprov gcf zimbraHttpDosFilterDelayMillis+zmprov gcf zimbraHttpDosFilterDelayMillis        # Default -1
 </file> </file>
  
Line 70: Line 78:
  
 <file> <file>
-zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.0.65+zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.2.0/24
 zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.0.66 zmprov mcf +zimbraHttpThrottleSafeIPs 192.168.0.66
  
Line 147: Line 155:
  
 ===== Server Status ===== ===== 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'': Check ''/var/log/zimbra.log'' and ''/var/log/zimbra-stats.log'':
Line 180: Line 190:
  
 ===== Mail Delivered to MTA But Not to Mailbox ===== ===== 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: 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 224: Line 238:
 zmprov md <domain.tld> zimbraDomainDefaultCOSId <your-zimbraId> zmprov md <domain.tld> zimbraDomainDefaultCOSId <your-zimbraId>
 </file> </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>
 +
internet/mail/zimbra/zimbra_troubleshoot.1476378262.txt.gz · Last modified: 2016/10/13 11:04 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki