Results 1 to 3 of 3

Thread: [SOLVED] MTA is running, but not working?

  1. #1
    gabe is offline Junior Member
    Join Date
    Nov 2010
    Posts
    5
    Rep Power
    4

    Default [SOLVED] MTA is running, but not working?

    We've been using Zimbra without issue for 1.5 months on:

    Zimbra/OS Version:
    Release 6.0.10_GA_2692.RHEL5_64_20101215170845 CentOS5_64 FOSS edition.

    Yesterday the server was rebooted for the first time since install. It should be noted that in that time both Zimbra & the OS were updated. We are now unable to send or receive mail. When trying to send we receive the following (domain name changed for privacy):

    Code:
    An unknown error (mail.TRY_AGAIN) has occurred.
    method:	SendMsgRequest
    msg:	try again: Unable to connect to the MTA
    code:	mail.TRY_AGAIN
    detail:	soap:Receiver
    trace:	com.zimbra.cs.mailbox.MailServiceException: try again: Unable to connect to the MTA ExceptionId:btpool0-17://mail.mydomain.com:60081/service/soap/SendMsgRequest:1294672657050:c75b57290c9a1a17 Code:mail.TRY_AGAIN at com.zimbra.cs.mailbox.MailServiceException.TRY_AGAIN(MailServiceException.java:475) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:475) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:309) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:266) at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:189) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:150) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:413) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:265) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:227) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1511) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:453) at javax.mail.Service.connect(Service.java:291) at javax.mail.Service.connect(Service.java:172) at javax.mail.Service.connect(Service.java:121) at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:781) at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:702) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:412) ... 39 more
    request
    The server reports that the MTA is running:
    Code:
    [zimbra@mail log]$ zmcontrol status
    Host mail.mydomain.com
            antispam                Running
            antivirus               Running
            ldap                    Running
            logger                  Running
            mailbox                 Running
            mta                     Running
            snmp                    Running
            spell                   Running
            stats                   Running
    zimbra.log says:
    Code:
    [zimbra@mail log]$ tail zimbra.log
    Jan 10 15:31:30 ns2 postfix/postqueue[3287]: fatal: Queue report unavailable - mail system is down
    Jan 10 15:32:00 ns2 postfix/postqueue[3306]: fatal: Queue report unavailable - mail system is down
    Jan 10 10:32:06 ns2 zmmailboxdmgr[3716]: status requested
    Jan 10 10:32:06 ns2 zmmailboxdmgr[3716]: status OK
    Jan 10 15:32:30 ns2 postfix/postqueue[4605]: fatal: Queue report unavailable - mail system is down
    Jan 10 10:32:39 ns2 zmmailboxdmgr[5095]: status requested
    Jan 10 10:32:39 ns2 zmmailboxdmgr[5095]: status OK
    Jan 10 10:32:39 ns2 zmmailboxdmgr[5178]: status requested
    Jan 10 10:32:39 ns2 zmmailboxdmgr[5178]: status OK
    Jan 10 15:33:00 ns2 postfix/postqueue[5238]: fatal: Queue report unavailable - mail system is down
    postfix check gives this:
    Code:
    [zimbra@mail log]$ postfix check
    postfix/postfix-script: warning: not owned by root: /opt/zimbra/data/postfix/spool
    postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.6.7.2z/conf/main.cf
    postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.6.7.2z/conf/master.cf
    postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.6.7.2z/conf/master.cf.in
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/347301D8002D
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/2C6DC1570070
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/156231570079
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/5DA1A157007C
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/0E82F1570071
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/0C77E157007A
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/32D141570078
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/DFC7A1570074
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/0422F1570072
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/88CCF1570073
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/5A9FA1D8002C
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/E52251570076
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/B3F871570077
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/A1CF11570075
    postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/51BEB157007B
    I've tried stopping ZCS, running the following:
    Code:
    /opt/zimbra/libexec/zmfixperms
    /opt/zimbra/libexec/zmfixperms --extended
    And starting again, but the problem persists.

    Any ideas?
    Last edited by gabe; 01-10-2011 at 11:57 AM. Reason: [SOLVED]

  2. #2
    gabe is offline Junior Member
    Join Date
    Nov 2010
    Posts
    5
    Rep Power
    4

    Default

    I THINK this was caused by an improperly configured /etc/hosts

    After simplifying to assure compliance with the documentation, things seem to be working.

  3. #3
    davidkillingsworth is offline Loyal Member
    Join Date
    Feb 2012
    Location
    Hong Kong
    Posts
    77
    Rep Power
    3

    Default

    Quote Originally Posted by gabe View Post
    I THINK this was caused by an improperly configured /etc/hosts
    I had the same issue on one of my servers. The host name was zimbra.<countrycode>.mydomain.com. I had set the MTA in both Global settings and Server to use zimbra.mydomain.com.

    I was getting the "try again: Unable to connect to the MTA" error, but I did not see any errors in my zimbra.log and all zimbra services were running.

    I did not yet have the external DNS entry created yet, so the server itself could not resolve zimbra.mydomain.com.

    I added a local hosts entry in /etc/hosts for 127.0.0.1 zimbra.mydomain.com and all started working after that.

    Ideally, you would have a public DNS entry for your zimbra.mydomain.com, but I was in testing mode.
    Release 7.2.4_GA_2900.UBUNTU10_64 UBUNTU10_64 FOSS edition.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Daily mail report always reports "No messages found"
    By McPringle in forum Installation
    Replies: 42
    Last Post: 06-13-2011, 08:57 AM
  2. zmmailboxdctl is stopped frequently..
    By tamilnandhu in forum Installation
    Replies: 13
    Last Post: 04-12-2008, 08:59 AM
  3. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM
  4. Trouble sending mail from Outlook
    By czaveri in forum Users
    Replies: 15
    Last Post: 07-24-2006, 11:01 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •