LMTP is the local delivery to your local mailbox. This is not the log showing the mail coming into the system.

See this forum post. http://www.zimbra.com/forums/administrators/59592-ldap-database-went-97meg-86gig.html.

Zimbra 7.1.2 was sending non-delivery notifications to (faked)e-mail addresses when a virus or banned extension was found, ie. backscatter. It requires you to edit the amavisd.conf.in file to correct the final destination of the non-delivered message. There is a forum article about this with details...

There was a problem with 8.0.2 and IPv6. But according to the announcement forum 8.0.3 should have fixed IPv6 blocking delivery. This may be another issue.

Quick question Quanah. I've used cp to backup my server since ZCS5 and now with ZCS7. I shut the server down first then cp -rp the zimbra directory. I have restored successfully from these backups. Your statement that it remains unacceptable for ZCS7 and prior due to BDB has me confused. Since m...

Can you test it to see if you can hit it through the LAN IP on the computer. It does appear your firewall is off and you should be able to to hit the port if LDAP is bound to 127.0.0.1. Are you running IPv6?

Not sure how Network Edition backups work but you could always mount a drive and its partition to the directory where backups are going. If zimbra won't let you choose the directory. I have a hard drive mounted in /opt so my whole installation is on a separate drive.

Make sure port 465 is open. And the split DNS is configured correctly. Your internal and external DNS servers should be different. So forwarding port 53 appears like the outside world is resolving on your internal DNS. Internal should point to LAN ip's and external to WAN IP.

Is it possible you have an infected computer on your trusted network?

It appears that one of your e-mail clients is not set to authenticate and is on a different network than your mail server's trusted networks.