Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: [SOLVED] Question about configuration

  1. #1
    mityollom is offline Junior Member
    Join Date
    Jun 2009
    Posts
    7
    Rep Power
    6

    Default [SOLVED] Question about configuration

    I have a question regarding setup of a ZCS 5.0 environment. I have 2 MTA servers and 1 LDAP/MailStore server.

    I got the servers all setup without much of a hitch, however, I am not able to send mail using the LDAP/MailStore server (i.e through web client, or with the Desktop client configured with a 'Zimbra' account type). I am assuming this is due to the fact I did not install zimbra-mta on the LDAP/MailStore server; i.e no SMTP running, no sending mail. I did this as per the instructions in the Installation guide.

    My question is, should I just install the zimbra-mta on the LDAP/MailStore server to allow this functionality, or is there some other alternative method of doing this?

    Thanks!

  2. #2
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    Zimbra MTA component is used to send and recieve mail. Since you have zimbra MTA installed as seperate component why not use them for sending? Tere is no need to install mta on LDAP/Mailstore. If you are using outlook then better use mta server as smtp server and if webmail then mail should go. what error you are getting in /opt/zimbra/zimbra.log while sending mail ?

  3. #3
    mityollom is offline Junior Member
    Join Date
    Jun 2009
    Posts
    7
    Rep Power
    6

    Default

    Quote Originally Posted by veronica View Post
    Zimbra MTA component is used to send and recieve mail.
    This I understand

    Quote Originally Posted by veronica View Post
    Since you have zimbra MTA installed as seperate component why not use them for sending?
    The issue comes down to user experience and client configuration. If I configure the ZImbra Desktop app with a 'Zimbra' account, there is no place I can see to set an outgoing mail server, as it tries to use the MailStore/LDAP server. If I configure the account as an IMAP account, I can set the outgoing server as one of the MTAs, and it works fine. The same issue arises with the Web Client; I cannot send mail through the web client. Here is the message I get:

    Code:
    method:	SendMsgRequest
    msg:	system failure: MessagingException
    code:	service.FAILURE
    detail:	soap:Receiver
    trace:	btpool0-0:1244484217245:f2bed5455876bbe8
    request:	
    
    Body: {
      SendMsgRequest: {
        _jsns: "urn:zimbraMail",
        m: {
          e: [
            0: {
              a: "traim@yahoo.ca",
              add: 1,
              t: "t"
             },
            1: {
              a: "tim@rbase.ca",
              p: "Tim Molloy",
              t: "f"
             },
            2: {
              a: "tim@rbase.ca",
              p: "Tim Molloy",
              t: "r"
             }
           ],
          idnt: "12c08b65-69f2-436c-a760-dd9a993f40ad",
          mp: [
            0: {
              content: {
                _content: "test
    
    -- 
    Tim Molloy
    Proprieter, rBase Communications
    tim@rbase.ca
    "
               },
              ct: "text/plain"
             }
           ],
          su: {
            _content: "test"
           }
         },
        suid: 1244484248075
       }
     },
    Header: {
      context: {
        _jsns: "urn:zimbra",
        account: {
          _content: "tim@rbase.ca",
          by: "name"
         },
        authToken: "(removed)",
        format: {
          type: "js"
         },
        sessionId: {
          _content: 1156,
          id: 1156
         },
        userAgent: {
          name: "ZimbraWebClient - FF3.0 (Win)",
          version: "5.0.16_GA_2921.RHEL5"
         }
       }
     }
    Another issue I can think of that might come up is if the MTA configured in the client fails, then they will lose the ability to send email without either changing their MTA to the secondary manually or waiting until the primary MTA is back online.

  4. #4
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    > If I configure the ZImbra Desktop app with a 'Zimbra' account, there is no place I can see to set an outgoing mail server, as it tries to use the MailStore/LDAP server

    For ZDesktop you dont need to set smtp server as every user profile has setting for zimbraSmtpHostname which is used for sending mail. If you cannot send mail using webclient also then it seems this variable is not set properly.

    zmprov gs `zmhostname ` | grep -i smtp
    zimbraSmtpHostname: smtpserver

  5. #5
    mityollom is offline Junior Member
    Join Date
    Jun 2009
    Posts
    7
    Rep Power
    6

    Default

    Thanks for the info. I figured out how to set this value. Is it possible to put 2 servers in that list for redundancy purposes?

    regards,

    tim
    Last edited by mityollom; 06-10-2009 at 05:53 PM.

  6. #6
    mityollom is offline Junior Member
    Join Date
    Jun 2009
    Posts
    7
    Rep Power
    6

    Default

    I set this value, but I am still getting the same error when I try sending a message via webmail client. The value is now set from localhost to the hostname of the Primary MTA server.

    What are my other options?

  7. #7
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    What does mailbox.log say ? Does mail actually go to MTA and gets rejected or webmail only don't send it ? Please paste zimbra.log also

  8. #8
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    zimbra.log on MTA
    mailbox.log on mailstore

  9. #9
    mityollom is offline Junior Member
    Join Date
    Jun 2009
    Posts
    7
    Rep Power
    6

    Default

    Thanks for your help on this. Here's the mailbox.log from the MailStore server:

    2009-06-12 10:44:23,199 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] soap - SendMsgRequest
    2009-06-12 10:44:23,200 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] SendMsg - LC(mbox=12c08b65-69f2-436c-a760-dd9a993f40ad, sessions=1125)
    2009-06-12 10:44:23,200 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] smtp - Sending message to MTA at localhost, port 25: Message-ID=<10679349.181244825063200.JavaMail.root@hiclx07.hos tedincanada.com>, replyType=r
    2009-06-12 10:44:23,202 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] mailop - Adding Message: id=394, Message-ID=<10679349.181244825063200.JavaMail.root@hiclx07.hos tedincanada.com>, parentId=-1, folderId=5, folderName=Sent.
    2009-06-12 10:44:23,214 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] mailop - Deleting Message (id=394).
    2009-06-12 10:44:23,218 WARN [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] smtp - exception occurred during SendMsg
    com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: Connection refused; chained exception is:
    java.net.ConnectException: Connection refused
    at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTra nsport.java:1378)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SM TPTransport.java:399)
    at javax.mail.Service.connect(Service.java:275)
    at javax.mail.Service.connect(Service.java:156)
    at javax.mail.Service.connect(Service.java:105)
    at javax.mail.Transport.send0(Transport.java:168)
    at javax.mail.Transport.send(Transport.java:98)
    at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:558)
    at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:255)
    at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:120)
    at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:196)
    at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:156)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:275)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:190)
    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:132)
    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.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
    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:211)
    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)
    2009-06-12 10:44:23,218 INFO [btpool0-0] [name=tim@rbase.ca;mid=5;ip=75.157.80.84;ua=ZimbraW ebClient - FF3.0 (Win)/5.0.16_GA_2921.RHEL5;] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: system failure: MessagingException
    ExceptionId:btpool0-0:1244825063218:dbb1e61e86569c0f
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
    at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:332)
    at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:120)
    at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:196)
    at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:156)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:275)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:190)
    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:132)
    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.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
    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:211)
    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$SafeMessagingExce ption: Connection refused; chained exception is:
    java.net.ConnectException: Connection refused
    at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTra nsport.java:1378)
    at com.sun.mail.smtp.SMTPTransport.protocolConnect(SM TPTransport.java:399)
    at javax.mail.Service.connect(Service.java:275)
    at javax.mail.Service.connect(Service.java:156)
    at javax.mail.Service.connect(Service.java:105)
    at javax.mail.Transport.send0(Transport.java:168)
    at javax.mail.Transport.send(Transport.java:98)
    at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:558)
    at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:255)
    ... 33 more
    2009-06-12 10:44:45,309 INFO [IndexWritersSweeperThread] [] index - open index writers sweep: before=1, closed=0, after=1 (0ms)

    The zimbra.log file on the MTA does not show anything when I try sending mail from the web client; I'm assuming this means the outbound message is not even being forwarded to the MTA.


    cheers,

    tim
    Last edited by mityollom; 06-12-2009 at 06:37 PM.

  10. #10
    veronica is offline Outstanding Member
    Join Date
    Jun 2008
    Posts
    594
    Rep Power
    8

    Default

    > The zimbra.log file on the MTA does not show anything when I try sending mail from the web client; I'm assuming this means the outbound message is not even being forwarded to the MTA.

    Seems MTA is not being used for sending mails. Can you let me know what is the value of zimbrSmtpServerHostname set on mailboxserver ?

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Default domain configuration question
    By liuk in forum Administrators
    Replies: 3
    Last Post: 05-12-2009, 05:50 AM
  2. Ubuntu 8.04 Lts Zimbra 5.0.14 Ldap Problem
    By rkrojero in forum Installation
    Replies: 10
    Last Post: 04-20-2009, 11:58 PM
  3. Transport configuration question
    By jroberts235 in forum Administrators
    Replies: 0
    Last Post: 05-21-2008, 02:29 PM
  4. server configuration question
    By burnmage in forum Installation
    Replies: 0
    Last Post: 11-08-2007, 04: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
  •