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

Thread: Unable to set up my email addresses

  1. #1
    raylynup is offline Starter Member
    Join Date
    Aug 2008
    Posts
    2
    Rep Power
    7

    Thumbs down Unable to set up my email addresses

    Having just loaded Zimbra, I tried to set up the various email addresses that I have & got the following message every time I tried.

    com.zimbra.cs.mailclient.CommandFailedException: LOGIN failed: LOGIN failure. Server Error-Please try again after some time. Error code 2

    I am running Windows XP Pro

  2. #2
    jjzhuang is offline Zimbra Employee
    Join Date
    Jan 2007
    Posts
    1,688
    Rep Power
    11

    Default

    which server is it?

  3. #3
    raylynup is offline Starter Member
    Join Date
    Aug 2008
    Posts
    2
    Rep Power
    7

    Default

    Have tried to set up password for Yahoo.com.au, bigpond.com. tpg.com.au all of which have my emails. I get the same error message every time

  4. #4
    jjzhuang is offline Zimbra Employee
    Join Date
    Jan 2007
    Posts
    1,688
    Rep Power
    11

    Default

    OK for yahoo.com.au I can understand. In build 1251 that's a known issue. Please try build 1278 which was just released today.

    For the other two services I'm not familiar with.

  5. #5
    sintesys is offline Starter Member
    Join Date
    Aug 2008
    Posts
    2
    Rep Power
    7

    Thumbs down Unable to configure extra accounts....

    I'm having the same issue when trying to configure extra email (pop) accounts; the application fails complaining about invalid user/password/server parameters.

    The extra pop accounts I'm trying to configure are currently working without issues with other email client so I'm pretty sure about the pop/smtp servers and passwords.

    Can anybody provide any ideas?

    By the way I'm using build 1278

    Martin

  6. #6
    jjzhuang is offline Zimbra Employee
    Join Date
    Jan 2007
    Posts
    1,688
    Rep Power
    11

    Default

    Please verify not only your POP settings but also SMTP. If SMTP settings are not correct it will fail to verify.

  7. #7
    sintesys is offline Starter Member
    Join Date
    Aug 2008
    Posts
    2
    Rep Power
    7

    Default

    All settings including SMTP have been verified and still receiving: "Service error. Please check your server settings; verify your email address, password or IMAP access (if required)."

    Martin

  8. #8
    jjzhuang is offline Zimbra Employee
    Join Date
    Jan 2007
    Posts
    1,688
    Rep Power
    11

    Default

    could you check mailbox.log under <install>/log to see if there are errors?

  9. #9
    jnsilver is offline Starter Member
    Join Date
    Aug 2008
    Location
    Germany
    Posts
    1
    Rep Power
    7

    Default Same error - excerpt from the log...

    Account settings are o.k and working in other mail clients...

    Here is the corresponding entry in the mailbox.log when i try to register my imap acoount (same with pop3).

    2008-08-23 18:28:19,921 INFO [btpool0-0] [name=zimbra;ip=127.0.0.1;] datasource - Error connecting to mail store:
    java.io.EOFException: SSL peer shut down incorrectly
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Unkn own Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(Unknown Source)
    at com.zimbra.cs.mailclient.MailConnection.startTls(M ailConnection.java:283)
    at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:90)
    at com.zimbra.cs.mailclient.imap.ImapConnection.conne ct(ImapConnection.java:82)
    at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:135)
    at com.zimbra.cs.datasource.ImapSync.test(ImapSync.ja va:104)
    at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:66)
    at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:515)
    at com.zimbra.cs.account.offline.OfflineProvisioning. createDataSourceAccount(OfflineProvisioning.java:5 67)
    at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:419)
    at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:58)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:411)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:268)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:188)
    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.handle(Se rvletHandler.java:362)
    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: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)
    2008-08-23 18:28:19,921 INFO [btpool0-0] [name=zimbra;ip=127.0.0.1;] datasource - Test failed: java.io.EOFException: SSL peer shut down incorrectly

  10. #10
    varghese2lijo is offline Junior Member
    Join Date
    Feb 2009
    Posts
    5
    Rep Power
    6

    Default login error

    from dec 23 i am not able to download yahoo mail. i cant login from zimbra. its shows error. but i can login from a web browser . zimbra sync with gmail and other yahoo mail account its serious bug..




    2009-02-27 12:43:18,726 DEBUG [btpool0-8] [ds=yahoo;] datasource - Generating new yauth token for user 'xxxxxxxxx'
    2009-02-27 12:43:19,396 DEBUG [btpool0-8] [ds=yahoo;] datasource - Saving 1 yauth token(s) for user 'xxxxxxxx@yahoo.com'
    2009-02-27 12:43:22,204 DEBUG [btpool0-8] [ds=yahoo;] imap - S: * OK IMAP4rev1 server ready (3.5.39)
    2009-02-27 12:43:22,204 DEBUG [btpool0-8] [ds=yahoo;] imap - C: C01 CAPABILITY
    2009-02-27 12:43:22,610 DEBUG [btpool0-8] [ds=yahoo;] imap - S: * CAPABILITY IMAP4rev1 LOGIN-REFERRALS AUTH=XYMCOOKIE AUTH=XYMCOOKIEB64 AUTH=XYMPKI AUTH=XYMECOOKIE ID
    2009-02-27 12:43:22,610 DEBUG [btpool0-8] [ds=yahoo;] imap - S: C01 OK CAPABILITY completed
    2009-02-27 12:43:22,610 DEBUG [btpool0-8] [ds=yahoo;] imap - C: C02 AUTHENTICATE XYMECOOKIE
    2009-02-27 12:43:23,031 DEBUG [btpool0-8] [ds=yahoo;] imap - S: +
    2009-02-27 12:43:23,031 DEBUG [btpool0-8] [ds=yahoo;] imap - C: <authentication data>
    2009-02-27 12:43:23,312 DEBUG [btpool0-8] [ds=yahoo;] imap - S: C02 NO AUTHENTICATE failure. Invalid auth-token. Error code 2
    2009-02-27 12:43:23,312 DEBUG [btpool0-8] [ds=yahoo;] datasource - Invalidating possibly expired cookie and retrying auth
    2009-02-27 12:43:25,090 DEBUG [btpool0-8] [ds=yahoo;] imap - S: * OK IMAP4rev1 server ready (3.5.39)
    2009-02-27 12:43:25,090 DEBUG [btpool0-8] [ds=yahoo;] imap - C: C03 CAPABILITY
    2009-02-27 12:43:25,340 DEBUG [btpool0-8] [ds=yahoo;] imap - S: * CAPABILITY IMAP4rev1 LOGIN-REFERRALS AUTH=XYMCOOKIE AUTH=XYMCOOKIEB64 AUTH=XYMPKI AUTH=XYMECOOKIE ID
    2009-02-27 12:43:25,340 DEBUG [btpool0-8] [ds=yahoo;] imap - S: C03 OK CAPABILITY completed
    2009-02-27 12:43:25,340 DEBUG [btpool0-8] [ds=yahoo;] imap - C: C04 AUTHENTICATE XYMECOOKIE
    2009-02-27 12:43:25,590 DEBUG [btpool0-8] [ds=yahoo;] imap - S: +
    2009-02-27 12:43:25,590 DEBUG [btpool0-8] [ds=yahoo;] imap - C: <authentication data>
    2009-02-27 12:43:25,870 DEBUG [btpool0-8] [ds=yahoo;] imap - S: C04 NO AUTHENTICATE failure. Invalid auth-token. Error code 2
    2009-02-27 12:43:25,870 WARN [btpool0-8] [ds=yahoo;] datasource - Test failed: DataSource: { id=76ac78b2-99ef-439f-ad40-a403fe0fb494, type=imap, isEnabled=true, name=yahoo, host=zimbra.imap.mail.yahoo.com, port=993, connectionType=ssl, username=xxxxxxx, folderId=1 }
    com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=76ac78b2-99ef-439f-ad40-a403fe0fb494, type=imap, isEnabled=true, name=yahoo, host=zimbra.imap.mail.yahoo.com, port=993, connectionType=ssl, username=xxxxxxx, folderId=1 }
    ExceptionId:btpool0-8:1235718805870:6e9da4003d73238a
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
    at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:156)
    at com.zimbra.cs.offline.YMailImport.connect(YMailImp ort.java:69)
    at com.zimbra.cs.datasource.ImapSync.test(ImapSync.ja va:112)
    at com.zimbra.cs.offline.YMailImport.test(YMailImport .java:53)
    at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:64)
    at com.zimbra.cs.account.offline.OfflineProvisioning. testDataSource(OfflineProvisioning.java:565)
    at com.zimbra.cs.account.offline.OfflineProvisioning. modifyDataSource(OfflineProvisioning.java:2110)
    at com.zimbra.cs.account.offline.OfflineProvisioning. modifyDataSource(OfflineProvisioning.java:2030)
    at com.zimbra.cs.service.admin.ModifyDataSource.handl e(ModifyDataSource.java:84)
    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:269)
    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.handle(Se rvletHandler.java:362)
    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: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: javax.security.auth.login.LoginException: AUTHENTICATE failure. Invalid auth-token. Error code 2
    at com.zimbra.cs.datasource.ImapSync.connect(ImapSync .java:151)
    ... 34 more
    Attached Images Attached Images

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. [SOLVED] Upgraded to 5.0 OSS - Sendmail Problem
    By Chewie71 in forum Installation
    Replies: 11
    Last Post: 12-28-2007, 07:07 PM
  2. Update Received Date in Folder-Listing
    By Oswald-Kolle in forum Installation
    Replies: 25
    Last Post: 08-21-2007, 04:21 PM
  3. need advice on configuring zimbra to work with fax server
    By pheonix1t in forum Administrators
    Replies: 0
    Last Post: 07-11-2007, 07:46 PM
  4. upgrade to 4.0.3 antispam does'nt work
    By lucanannipieri in forum Administrators
    Replies: 14
    Last Post: 11-07-2006, 03:56 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
  •