The Craving Mind

  A full backup for a single account stops with the following exception: 2016-05-11 13:58:25,603 WARN [FullBackupThread] [name=admin@example.com;mid=2;] backup - Error occurred during full backup for account admin@example.com; aborted backup and deleting /backup/tmp/full-20160511.115806.637/accounts/991/e7e/991e7e61-8ec0-4216-ac39-13407491ac83 com.zimbra.common.service.ServiceException: system failure: backing up table: mboxgroup2.mail_item ExceptionId:BackupSetWorkerThread-DB:1462967905595:a573750a2018f5f0 Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:260) at com.zimbra.cs.db.DbBackup.saveTable(DbBackup.java:128) at com.zimbra.cs.backup.BackupAccountSession.storeTablesToLocalFile(BackupAccountSession.java:317) at com.zimbra.cs.backup.FileBackupTarget$BackupAcctSession.storeTablesStage(FileBackupTarget.java:1639) at com.zimbra.cs.backup.FileBackupTarget$BackupSetWorkerThread.run(FileBackupTarget.java:2993) Caused by: com...

 After a restore from a backup, an e-mail is stuck in the Inbox as unread.  When trying to mark it as read, the following exception is produced: 2014-05-12 09:43:50,630 INFO  [qtp58648533-5694:https://169.254.254.2:7443/service/soap/MsgActionRequest]   [name=malte.stretz@example.com;mid=1;ip=169.254.0.102;oip=131.169.214.202;ua=ZimbraWebClient - FF29 (Linux)/8.0.7_GA_6021;] SoapEngine - handler exception com.zimbra.common.service.ServiceException: system failure: inconsistent state: unread < 0 for item 2 ExceptionId:qtp58648533-5694:https://169.254.254.2:7443/service/soap/MsgActionRequest:1399887830630:614f5e33fd12e368 Code:service.FAILURE        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:258)        at com.zimbra.cs.mailbox.MailItem.updateUnread(MailItem.java:2361)        at com.zimbra.cs.mailbox.Folder.updateUnread(Folder.java:610)        at com....

Steps: 1) Specify the account for which the restriction is applied. echo "test@example.com restrict_sender" > /opt/zimbra/postfix/conf/restrict_senders  Note: If you would like to restrict all users of a domain, enter the domainname instead of email ids. For example: echo "yourdomain.com restrict_sender" > /opt/zimbra/postfix/conf/restrict_senders   2) postmap /opt/zimbra/postfix/conf/restrict_senders 3)  Create a blank file in which no domain name is specified. touch /opt/zimbra/postfix/conf/restrict_recipients  4) postmap /opt/zimbra/postfix/conf/restrict_recipients  5)  In the file /opt/zimbra/conf/zmconfigd.cf, find the "SECTION mta DEPENDS amavis", and enter the following before the "RESTART mta" line: vi /opt/zimbra/conf/zmconfigd.cf Enter the lines POSTCONF smtpd_restriction_classes restrict_sender  POSTCONF restrict_sender FILE postfix_restrict_sender.cf  6)  Enter the line below at the top of the /opt/zimbra/conf/zmconfigd...

  Understanding DMARC record DMARC, (Domain-based   Message Authentication Reporting, & Conformance) an open source standard, uses a concept called alignment to tie the result of two other open source standards, SPF (a published list of servers that are authorized to send email on behalf of a domain) and DKIM (a tamper-evident domain seal associated with a piece of email), to the content of an email. DMARC alignment By themselves, SPF and DKIM can associate a piece of email with a domain. DMARC attempts to tie the results of SPF and DKIM to the content of email, specifically to the domain found in the From: header of an email. The domain found in the From: header of a piece of email is the entity that ties together all DMARC processing. Because anyone can buy a domain and put SPF and DKIM into place (including criminals), the results of processing SPF and DKIM have to be related to the domain found in the From: header to be relevant to DMAR...