Results 1 to 4 of 4

Thread: Soap fault

  1. #1
    Join Date
    Feb 2007
    Location
    Massachusetts
    Posts
    136
    Rep Power
    8

    Default Soap fault

    ZCO 4.5.9
    ZCS 4.5.9

    This is intermittant, but I have a user complaining of the fallowing:

    > From: System Administrator
    > Sent: Tuesday, November 27, 2007 8:49 AM
    > Subject: $ReallyLongSubjectLine
    >
    > Error: This message could not be sent.
    >
    > Subject: $ReallyLongSubjectLine
    >
    >
    > To: distlist@domain, confroom@domain
    >
    >
    > Note: Soap Fault. Please recreate and resend the message. Details below:
    >
    > Error Code: service.FAILURE
    > Error Text: system failure: MessagingException
    Last edited by Nutz; 11-27-2007 at 06:35 AM. Reason: clarity

  2. #2
    Join Date
    May 2007
    Location
    Selangor, Malaysia
    Posts
    16
    Rep Power
    8

    Default

    hi Nutz,

    before I upgraded to ZCS 5.0.2 I have only received 1 complaints as such... but just recently I have had 2 complaints regarding a similar SOAP ERROR as follows:-->

    My user, when replying a message, she clicks on the "To:" button to access the GAL and selects and email from the GAL to fill in the CC fields.

    From: System Administrator
    Sent: Monday, March 24, 2008 4:18 PM
    Cc: ‘myuser@mydomain.com’; ‘anotheruser@mydomain.com’
    Subject: Undeliverable: RE: Pricing Schedule.xls


    Error: This message could not be sent.

    Subject: RE: Pricing Schedule.xls

    To: someonelese@anotherdomain.com

    CC: ‘myuser@mydomain.com’, anotheruser@mydomain.com


    Note: Soap Fault. Please recreate and resend the message. Details below:

    Error Code: mail.SEND_ABORTED_ADDRESS_FAILURE

    Error Text: Invalid address: ‘myuser@mydomain.com’


    <soap:Envelope xmlns:soap=”http://www.w3.org/2003/05/soap-envelope”><soap:Header><context xmlns=”urn:zimbra”><change token=”60447”/></context></soap:Header><soap:Body><soap:Fault><soap:Code><soa p:Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>Invalid address: ‘myuser@mydomain.com’</soap:Text></soap:Reason><soapetail><Error xmlns=”urn:zimbra”><Code>mail.SEND_ABORTED_ADDRESS _FAILURE</Code><Trace>com.zimbra.cs.mailbox.MailServiceExcep tion: Invalid address: ‘myuser@mydomain.com’
    Code:mail.SEND_ABORTED_ADDRESS_FAILURE Arginvalid, STR, “’myuser@mydomain.com’”) Argunsent, STR, “someonelese@anotherdomain.com”) Argunsent, STR, “anotheruser@mydomain.com”)
    Last edited by prox; 03-24-2008 at 01:59 AM.

  3. #3
    Join Date
    May 2007
    Location
    Selangor, Malaysia
    Posts
    16
    Rep Power
    8

    Default

    CONTINUATION...

    at com.zimbra.cs.mailbox.MailServiceException.interna l_SEND_FAILURE(MailServiceException.java:422) at com.zimbra.cs.mailbox.MailServiceException.SEND_AB ORTED_ADDRESS_FAILURE(MailServiceException.java:42 6) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:306) at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:181) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:150) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272) at javax.servlet.http.HttpServlet.service(HttpServlet .java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174) at javax.servlet.http.HttpServlet.service(HttpServlet .java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093) at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:148) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139) at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:313) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)

    Caused by: com.zimbra.cs.mailbox.MailSender$SafeSendFailedExc eption: 501 5.1.3 Bad recipient address syntax ; chained exception is:

    com.sun.mail.smtp.SMTPAddressFailedException: 501 5.1.3 Bad recipient address syntax

    at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTranspo rt.java:1281) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTr ansport.java:622) at javax.mail.Transport.send0(Transport.java:169) at javax.mail.Transport.send(Transport.java:98) at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:428) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:248)

    ... 32 more

    </Trace><a t=”STR” n=”invalid”>’myuser@mydomain.com’</a><a t=”STR” n=”unsent”>someonelese@anotherdomain.com</a><a t=”STR” n=”unsent”>anotheruser@mydomain.com</a></Error></soapetail></soap:Fault></soap:Body></soap:Envelope>

  4. #4
    Join Date
    May 2007
    Location
    Selangor, Malaysia
    Posts
    16
    Rep Power
    8

    Default

    Nutz,

    I solved this before by disabling HTTP (port 80) and HTTPS (port 443) A/V scanning on the firewall at the client's side (firewall in front of the soap error user's gateway) for policies relating to the Mail Server's IP.

    I can't confirm if this can solve the issue now because I will only have access to my client's firewall tomorrow morning, but it did solve my issue in the past when we encountered the soap error and my client has confirmed he changed something on his firewall side prior to today so I will only know by tomorrow.

    Let me know how it goes for you. Cheers.
    Last edited by prox; 03-24-2008 at 02:23 AM.

Similar Threads

  1. XSD/WSDL Files for the SOAP Server?
    By photoadrian in forum Developers
    Replies: 5
    Last Post: 12-23-2012, 01:32 AM
  2. Jar For Soap Client
    By wcameron in forum Developers
    Replies: 19
    Last Post: 06-03-2009, 02:04 PM
  3. Zimbra SOAP Question
    By jonnybravo in forum Developers
    Replies: 8
    Last Post: 07-26-2007, 04:09 PM
  4. Bug with preauth mechanism and SOAP headers?
    By Coilcore in forum Developers
    Replies: 3
    Last Post: 07-20-2006, 10:41 AM
  5. Soap Requests ...
    By ubumail in forum Developers
    Replies: 2
    Last Post: 04-26-2006, 06:39 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
  •