Results 1 to 6 of 6

Thread: system failure: Unable to send message

  1. #1
    Join Date
    Feb 2012
    Posts
    4
    Rep Power
    3

    Default system failure: Unable to send message

    I had several users complain today that when they try sending a message they are getting an error.

    method: [unknown]
    msg: system failure: Unable to send message
    code: service.FAILURE
    detail: soap:Receiver
    trace: com.zimbra.common.service.ServiceException: system failure: Unable to send message ExceptionId:btpool0-37://eposta.yyu.edu.tr/service/soap/SendMsgRequest:1329664997486:93cf1fb86decae3b Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:630) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:425) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:385) at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:193) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:154) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215) at javax.servlet.http.HttpServlet.service(HttpServlet .java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) 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(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:583) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:986) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:414) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:429) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451) Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: Read timed out; chained exception is: java.net.SocketTimeoutException: Read timed out at com.zimbra.cs.mailclient.smtp.SmtpTransport.protoc olConnect(SmtpTransport.java:183) 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:898) at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:831) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:565) ... 39 more
    request:

    Body: {
    SendMsgRequest: {
    _jsns: "urn:zimbraMail",
    m: {
    e: [
    0: {
    a: "ecelik@yyu.edu.tr",
    add: "0",
    t: "t"
    },
    1: {
    a: "ecelik@yyu.edu.tr",
    p: "H. Eray ÇELİK",
    t: "f"
    }
    ],
    idnt: "11bdcdab-276a-438f-8a19-9741e7dc01c0",
    mp: [
    0: {
    content: {
    _content: "

    --
    Yrd. Doç. Dr. H. Eray Çelik
    Yüzüncü Yıl Üniversitesi
    Fen Edebiyat Fakültesi
    İstatistik Bölümü
    Zeve Yerleşkesi 65080 / VAN
    -------------------------------
    Ass.Prof.Dr. H. Eray ÇELİK
    Yüzüncü Yıl University
    Faculty of Science
    Department of Statistics
    Zeve Campus 65080 Van-Turkey
    "
    },
    ct: "text/plain"
    }
    ],
    su: {
    _content: ""
    }
    },
    suid: 1329664937436
    }
    },
    Header: {
    context: {
    _jsns: "urn:zimbra",
    account: {
    _content: "ecelik@yyu.edu.tr",
    by: "name"
    },
    authToken: "(removed)",
    session: {
    _content: 182,
    id: 182
    },
    userAgent: {
    name: "ZimbraWebClient - FF3.0 (Win)",
    version: "7.1.3_GA_3346"
    }
    }
    }

  2. #2
    Join Date
    Feb 2012
    Posts
    4
    Rep Power
    3

    Default

    please help me.

  3. #3
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by ecelik View Post
    please help me.
    Five hours is rather a short time to wait before 'bumping' a thread (which isn't acceptable on forums) and you haven't even provided any detailed information about the problem: whether this is a new problem; how many people have this problem; whether this is a new install or an upgrade; the specification of your server; which version and release of zimbra; what errors you see in the log files; etc., etc., etc. While you've been waiting , did you try searching the forums for an answer?

    site:zimbra.com +"system failure: Unable to send message" - Yahoo! Search Results
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #4
    Join Date
    Feb 2012
    Posts
    4
    Rep Power
    3

    Default

    Ubuntu 10.04 LTS 64 bit
    zimbra version 7.1.3_GA_3346


    when I restart zimbra
    ->starting MTA .. done
    but when I was cehck zimbra status
    --> mta stoppeed
    --->postfix is not running

  5. #5
    Join Date
    Feb 2012
    Posts
    4
    Rep Power
    3

    Default

    The prosses MTA start and stop take long time about five min.

  6. #6
    Join Date
    May 2010
    Posts
    272
    Rep Power
    5

    Default

    look at the mailbox.log files - betwee start and stop there must be something

    maybe a scrambled message waiting for send or so

    The client error message doenst help here we really need the logfile specially between starting mailbox and "mailbox stopped"

Similar Threads

  1. Unable to send message: Did not receive greeting from server
    By guedressel in forum Administrators
    Replies: 7
    Last Post: 05-07-2012, 03:34 AM
  2. [SOLVED] SOAP command to send message from drafts ?
    By liverpoolfcfan in forum Developers
    Replies: 1
    Last Post: 06-14-2011, 03:36 AM
  3. need advice on configuring zimbra to work with fax server
    By pheonix1t in forum Administrators
    Replies: 0
    Last Post: 07-11-2007, 08:46 PM
  4. system failure: getDirectContext
    By avisser in forum Installation
    Replies: 3
    Last Post: 10-12-2005, 06:32 AM
  5. Insallation failed (Debian server)
    By popui007 in forum Installation
    Replies: 5
    Last Post: 09-29-2005, 03:27 PM

Posting Permissions

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