Difference between revisions of "Zimbra mail queue management"
(Created page with "<yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb> =Zimbra mail queue management= Zimbra server mail queue might become big if there are too many emails...") |
m |
||
| Line 1: | Line 1: | ||
<yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb> | <yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb> | ||
=Zimbra mail queue management= | =Zimbra mail queue management= | ||
'''There is new article at [[CentOS 7.x Zimbra mail queue management]]''' | |||
Zimbra server mail queue might become big if there are too many emails being sent / received from server. This could just be a capacity issue or could also be an indicator of server being target/source of spam attack. Please refer to [[Prevent spam problem with Zimbra server]] to protect server from SPAM attack. If server was recently under attack or heavy use then mail queues might have too many queued emails. In such cases shift all mails from active and deferred queues to "Held" queue. In held queue release only the good emails and delete emails which are not genuine. After mails are held if you need to check the content of email then go to '/opt/zimbra/data/postfix/spool/hold' folder to look at email files. You can use 'grep "sender or receiver email" *' to get IDs of emails with particular sender and receiver. Then 'cat file' or preferably 'xxd file' command can be used to check contents of particular email. | Zimbra server mail queue might become big if there are too many emails being sent / received from server. This could just be a capacity issue or could also be an indicator of server being target/source of spam attack. Please refer to [[Prevent spam problem with Zimbra server]] to protect server from SPAM attack. If server was recently under attack or heavy use then mail queues might have too many queued emails. In such cases shift all mails from active and deferred queues to "Held" queue. In held queue release only the good emails and delete emails which are not genuine. After mails are held if you need to check the content of email then go to '/opt/zimbra/data/postfix/spool/hold' folder to look at email files. You can use 'grep "sender or receiver email" *' to get IDs of emails with particular sender and receiver. Then 'cat file' or preferably 'xxd file' command can be used to check contents of particular email. | ||
Revision as of 05:01, 15 March 2019
<yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb>
Zimbra mail queue management
There is new article at CentOS 7.x Zimbra mail queue management
Zimbra server mail queue might become big if there are too many emails being sent / received from server. This could just be a capacity issue or could also be an indicator of server being target/source of spam attack. Please refer to Prevent spam problem with Zimbra server to protect server from SPAM attack. If server was recently under attack or heavy use then mail queues might have too many queued emails. In such cases shift all mails from active and deferred queues to "Held" queue. In held queue release only the good emails and delete emails which are not genuine. After mails are held if you need to check the content of email then go to '/opt/zimbra/data/postfix/spool/hold' folder to look at email files. You can use 'grep "sender or receiver email" *' to get IDs of emails with particular sender and receiver. Then 'cat file' or preferably 'xxd file' command can be used to check contents of particular email.
Note that various postfix commands such as
postsuper -H ALL
even after specifying path as /opt/zimbra/postfix/sbin/postsuper do not work well with Zimbra Management Interface queue management. Hence always use Zimbra Administrative interface queue management and avoid postfix commands.
Zimbra postfix queue directories can be figured using steps from http://www.datanethosting.com/kb/zimbra/zimbra-postfix-queue-management-via-command-line
