Difference between revisions of "Mgolfieri- Admin notification emails"

Line 10: Line 10:
  zmlocalconfig -e smtp_destination=admin@domain.com
  zmlocalconfig -e smtp_destination=admin@domain.com
Also zimbraSmtpHostname is a critical one here. It might be set at the global config, domain or server level though, please check them all:
zmprov gcf zimbraSmtpHostname
zmprov gd ''domain.com'' zimbraSmtpHostname
zmprov gs ''ZimbraNodeFQDNhostname'' zimbraSmtpHostname
it should match your MTA node FQDN as you find it listed via "zmprov gas" (it might be currently set to ''localhost''). To change it:
zmprov mcf zimbraSmtpHostname ''MTA_FQDN'' # if set at the globalconfig level
zmprov md ''domain.com'' zimbraSmtpHostname ''MTA_FQDN''
zmprov ms ''ZimbraNodeFQDNhostname'' zimbraSmtpHostname ''MTA_FQDN'' # if set at the server level
For the AV notifications, check:
For the AV notifications, check:

Revision as of 13:51, 22 June 2012

Admin email notifications are mostly hot-changeable, they don't need any restart since they are handled by cronjobs on most cases, and settings are sourced at every run. For example:

1) For any general SMTP-related notification, check:

zmlocalconfig smtp_destination

and if wrong, please change it via:

zmlocalconfig -e smtp_destination=admin@domain.com

For the AV notifications, check:

zmlocalconfig av_notify_user

and if wrong, please change it via:

zmlocalconfig -e av_notify_user=admin@domain.com

2) Regarding backup reports, check:

zimbra@zcs7-ga:~$ zmprov gacf zimbraBackupReportEmailRecipients
zimbraBackupReportEmailRecipients: admin@domain.com
zimbra@zcs7-ga:~$ zmprov gs `zmhostname` zimbraBackupReportEmailRecipients
# name zcs7-ga.cork.zimbralab.com
zimbraBackupReportEmailRecipients: admin@domain.com

In case they are misconfigured, you can change by first issuing:

zmprov mcf zimbraBackupReportEmailRecipients admin@domain.com

Since server settings override global ones, check on every store node:

$ zmprov gs `zmhostname` zimbraBackupReportEmailRecipients

If the above will still report a wrong value, then:

$ zmprov ms `zmhostname` zimbraBackupReportEmailRecipients admin@domain.com

Note that the value is multi-valued:

<attr id="459" name="zimbraBackupReportEmailRecipients" type="string" cardinality="multi" optionalIn="globalConfig,server" flags="serverInherited">
  <desc>Backup report email recipients</desc>

So if you want to add other email addresses, after setting the main one as per the instructions above, please do (note the plus sign, it's very important not to leave it out!):

$ zmprov mcf +zimbraBackupReportEmailRecipients another-admin@domain.com

and if you need this to be done on this server only instead of changing it globally:

$ zmprov ms `zmhostname` +zimbraBackupReportEmailRecipients another-admin@domain.com

Likewise, to remove an email address:

$ zmprov ms `zmhostname` -zimbraBackupReportEmailRecipients another-admin@domain.com

3) Check that the cronjobs are set, and at what time they trigger. Usually the following are the default settings:

zimbra@zcs7-ga:~$ crontab -l |grep report
0 1 * * 6 /opt/zimbra/bin/zmbackup -f -a  all --mail-report    
0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i  --mail-report 
0 0 * * * /opt/zimbra/bin/zmbackup -del 1m --mail-report
0 23 * * 7 /opt/zimbra/libexec/zmdbintegrityreport -m
# Daily reports
30 23 * * * /opt/zimbra/libexec/zmdailyreport -m

According to the above times set, you can then check /var/log/zimbra.log accordingly to see if you find any error. You should see entries around this following line for example, coming from the server itself:

Nov 27 23:30:40 zcs7-ga postfix/qmgr[16654]: BF2B020832: from=<zimbra@zcs7-ga.cork.zimbralab.com>, size=4138, nrcpt=1 (queue active)
Nov 27 23:30:44 zcs7-ga postfix/lmtp[24064]: 8D50320834: to=<admin@zcs7.cork.zimbralab.com>, relay=zcs7-ga.cork.zimbralab.com[]:7025, delay=0.18, delays=0.02/0.02/0.01/0.13, dsn=2.1.5, status=sent (250 2.1.5 Delivery OK)

4) If you get the emails, but you don't get a proper body content for some reason, manually triggering the commands you see in the crontab without the -m/--mail-report option will produce the same email content on the standard output, this might be useful for troubleshooting:


As you can see, running the other commands seen in the crontab will trigger bigger operations (full/incremental backups, deletion, etc..) so pay extra attention to them should you need to run them for troubleshooting.

Jump to: navigation, search