All is running, but cannot send email

[bvillers]

All services show running.

I can login to admin console.

There is no email activity showing.

Cannot send emails.

Our email system is unavailable and people are cranky....

Below are Mailbox.log ERROR entries (selected from larger text):

ERROR [ImapSSLServer-1] [ip=97.195;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

2018-03-19 09:59:13,799 ERROR [ImapSSLServer-2] [ip=1071;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:882)

2018-03-19 09:59:54,463 ERROR [ImapSSLServer-4] [ip=172.250;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:882)


2018-03-19 10:00:36,602 INFO [btpool0-14://emailServer.name.com/service/soap/SendMsgRequest] [name=jhughes@emailServer.name.com;mid=660;ip=10.217.0.67;ua=ZimbraWebClient - FF3.0 (Win)/7.2.7_GA_2942;] SoapEngine - handler exception com.zimbra.common.service.ServiceException: system failure: Unable to send message ExceptionId:btpool0-14://emailServer.name.com/service/soap/SendMsgRequest:1521468036601:e7a96b02ed0680a2
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)

2018-03-19 10:17:32,606 INFO [btpool0-39://servername.com/service/soap/SendMsgRequest] [name=fmunro@emailServer.name.com;mid=352;ip=10 24;ua=ZimbraWebClient - FF3.0 (Win)/7.2.7_GA_2942;] SoapEngine - handler exception

ExceptionId:btpool0-39://emailServer.name.com/service/soap/SendMsgRequest:1521469052606:e7a96b02ed0680a2 Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)

ERROR [ImapSSLServer-2] [ip=10.;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

[L. Mark Stone]

All services show running.

I can login to admin console.

There is no email activity showing.

Cannot send emails.

Our email system is unavailable and people are cranky....

Below are Mailbox.log ERROR entries (selected from larger text):

ERROR [ImapSSLServer-1] [ip=97.195;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

2018-03-19 09:59:13,799 ERROR [ImapSSLServer-2] [ip=1071;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:882)

2018-03-19 09:59:54,463 ERROR [ImapSSLServer-4] [ip=172.250;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:882)


2018-03-19 10:00:36,602 INFO [btpool0-14://emailServer.name.com/service/soap/SendMsgRequest] [name=jhughes@emailServer.name.com;mid=660;ip=10.217.0.67;ua=ZimbraWebClient - FF3.0 (Win)/7.2.7_GA_2942;] SoapEngine - handler exception com.zimbra.common.service.ServiceException: system failure: Unable to send message ExceptionId:btpool0-14://emailServer.name.com/service/soap/SendMsgRequest:1521468036601:e7a96b02ed0680a2
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)

2018-03-19 10:17:32,606 INFO [btpool0-39://servername.com/service/soap/SendMsgRequest] [name=fmunro@emailServer.name.com;mid=352;ip=10 24;ua=ZimbraWebClient - FF3.0 (Win)/7.2.7_GA_2942;] SoapEngine - handler exception

ExceptionId:btpool0-39://emailServer.name.com/service/soap/SendMsgRequest:1521469052606:e7a96b02ed0680a2 Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)

ERROR [ImapSSLServer-2] [ip=10.;] ProtocolHandler - Exception occurred while handling connection javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

Bill,

Feel free to call me if you need help with this...

All the best,
Mark

[bvillers]

This blog is related to my issue:
https://guypaddock.livejournal.com/52605.html
Nearly to a tee, it describes my situation.

Mar 19 15:47:29 mailhost4 postfix/smtpd[31738]: fatal: open database /etc/aliases.db: No such file or directory
Mar 19 15:47:30 mailhost4 postfix/master[14940]: warning: process /opt/zimbra/postfix/libexec/smtpd pid 31738 exit status 1
Mar 19 15:47:30 mailhost4 postfix/master[14940]: warning: /opt/zimbra/postfix/libexec/smtpd: bad command startup -- throttling
Mar 19 15:48:07 mailhost4 zmmailboxdmgr[32072]: status requested
Mar 19 15:48:07 mailhost4 zmmailboxdmgr[32072]: status OK


My entries in the /opt/zimbra/conf/postfix_recipient_restrictions.cf file were as follows:
reject_unknown_recipient_domain
reject_unverified_recipient
I added these lines just after the first line, which should be reject_non_fqdn_recipient (https://wiki.zimbra.com/wiki/Improving_Anti-spam_system)

Somehow, it caused, I believe, the /etc/aliases.db file to be deleted. /var/log/zimbra.log for this time period is corrupted, therefore, unavailable.

========== text of web page ===========

Here at RedBottle, we recently started using Zimbra, a most awesome e-mail system. As part of the set-up, we needed to lockdown a feel of our internal mailing lists to prevent outside spammers from sending messages to them. I followed the tutorial on how to restrict Postfix recipients, and learned in the process how to seriously break the ability to send e-mails.

Long story short: don't use comments in the /opt/zimbra/conf/postfix_recipient_restrictions.cf file. Zimbra includes that file inside the value of the smtpd_recipient_restrictions variable of /opt/zimbra/postfix/conf/main.cf. So... if you put comments in the file, those comments become part of the configuration value.

So, for example, my /opt/zimbra/conf/postfix_recipient_restrictions.cf file was like this:

# GAP on 2011-11-16: Adding restriction to outside e-mail for internal RBD distribution lists
check_recipient_access hash:/opt/zimbra/postfix/conf/rbd_protected_recipients

%%contains VAR:zimbraServiceEnabled cbpolicyd, check_policy_service inet:127.0.0.1:10031%%
..remaining file omitted..

Resulting in Zimbra adding the following directive in /opt/zimbra/postfix/conf/main.cf:
smtpd_recipient_restrictions = # GAP on 2011-11-16: Adding restriction to outside e-mail for internal RBD distribution lists, check_recipient_access hash:/opt/zimbra/postfix/conf/rbd_protected_recipients

That, in turn, leads to an error like the following, inside /var/log/zimbra.log:

Nov 17 22:55:45 zimbra-server postfix/smtpd[21240]: fatal: open dictionary: expecting "type:name" form instead of "2011-11-16:"
Nov 17 22:55:46 zimbra-server postfix/master[17417]: warning: process /opt/zimbra/postfix/libexec/smtpd pid 21240 exit status 1
Nov 17 22:55:46 zimbra-server postfix/master[17417]: warning: /opt/zimbra/postfix/libexec/smtpd: bad command startup -- throttling

So... one tiny comment leads to a broken Postfix, which leads to a broken Zimbra because it can't send or receive e-mails (though you can read what you already have in your inbox).

=======================================

[bvillers]

Disk full appears to have caused the /etc/aliases.db file to be renamed/corrupted _db.aliases.db.

Ran newaliases and the file was re-created.

New errors in /var/log/zimbra.log

[bvillers]

New errors in /var/log/zimbra.log

postfix/smtpd[6824]: fatal: need service transport:endpoint instead of "permit"
postfix/master[5317]: warning: process /opt/zimbra/postfix/libexec/smtpd pid 6824 exit status 1
postfix/master[5317]: warning: /opt/zimbra/postfix/libexec/smtpd: bad command startup -- throttling

checking smtpd, main.cf & master.cf for configuration

[bvillers]

"postfix check" identifies
master.cf and main.cf
are not owned by ROOT

When I chown the files and restart postfix, they revert to being owned by zimbra.

[phoenix]

"postfix check" identifies
master.cf and main.cf
are not owned by ROOT

When I chown the files and restart postfix, they revert to being owned by zimbra.

Shutdown Zimbra and run zmfixperms with the extended option then restart Zimbra. Do not post duplicate messages in these forums and do not add them to threads that are several years old, stick to the one thread otherwise it gets confusing for people trying to answer your questions. I've removed your duplicate post.

[L. Mark Stone]

"postfix check" identifies
master.cf and main.cf
are not owned by ROOT

When I chown the files and restart postfix, they revert to being owned by zimbra.

Bill,

That log entry is normal; it's not your issue. As we discussed by phone yesterday, some change, combination of changes, or ripple effect from a chang(es) is likely borking your Postfix/Amavis portion of Zimbra, and that's why Zimbra appears to be running OK, but is not transporting any email.

I would also caution that if you do indeed have a compromised mailbox, thousands of bad emails will slow legitimate email delivery and _may_ make it seem like Postfix/Amavis is borked.

If you start posting log files, we should be in a better position to help here!

All the best,
Mark

[bvillers]

Thanks for the heads up. I will post as prescribed.

After running zmfixperms -extended, there was no change.

Still getting the postfix/smtpd fatal warning regarding need service transport:endpoint instead of "permit"

Do you have any suggestions to get our email moving? Do you need logs/files/etc?

Let me know at earliest convenience.

[bvillers]

Sorry Mark, I didn't see your update as my screen was not refreshed for some time.

Let me know which log(s) would be helpful and I'll upload them immediately.