YMail no longer can connect

If Zimbra Desktop had a sync failure, it may have told you to post your error in this section.
jsmneedshelp
Posts: 6
Joined: Sat Sep 13, 2014 2:08 am

YMail no longer can connect

Postby jsmneedshelp » Sun Jul 24, 2011 10:29 am

Well, Yahoo forced me to reset my password for my mail PLUS account, now Zimbra Desktop can not access anymore! I tried to "edit" and reset the password and I received the following message:
"Account is locked. To resolve this issue, login using a web browser here.

Display error details"
The display error details are listed below, but it would appear that Yahoo is requiring Captcha which Zimbra can't handle.
When I follow the instuctions and "login using a browser here" there is no Captcha and the login goes just fine. But this does not resolve the error, I get the same one.
I got desperate and deleted the account and tried to create one from scratch to get around the issue, same exact thing.
Help!!!!!!!

Details on error:
com.zimbra.common.soap.SoapFaultException: Captcha is required ExceptionId:com.zimbra.cs.util.yauth.AuthenticationException: Captcha is required ExceptionId:btpool0-30:1311520883743:30c05036bc57c0b2 Code:yauth.CAPTCHA_REQUIRED at com.zimbra.cs.util.yauth.RawAuth.doGet(RawAuth.java:159) at com.zimbra.cs.util.yauth.RawAuth.getToken(RawAuth.java:82) at com.zimbra.cs.util.yauth.TokenStore.newToken(TokenStore.java:23) at com.zimbra.cs.util.yauth.MetadataTokenStore.newToken(MetadataTokenStore.java:62) at com.zimbra.cs.util.yauth.RawAuthManager.authenticate(RawAuthManager.java:41) at com.zimbra.cs.util.yauth.RawAuthManager$1.authenticate(RawAuthManager.java:74) at com.zimbra.cs.offline.ab.yab.YabImport.test(YabImport.java:49) at com.zimbra.cs.offline.OfflineImport.test(OfflineImport.java:89) at com.zimbra.cs.offline.YMailImport.test(YMailImport.java:41) at com.zimbra.cs.datasource.DataSourceManager.test(DataSourceManager.java:208) at com.zimbra.cs.account.offline.OfflineProvisioning.testDataSource(OfflineProvisioning.java:616) at com.zimbra.cs.account.offline.OfflineProvisioning.createDataSourceAccount(OfflineProvisioning.java:706) at com.zimbra.cs.account.offline.OfflineProvisioning.createAccount(OfflineProvisioning.java:511) at com.zimbra.cs.service.admin.CreateAccount.handle(CreateAccount.java:64) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) 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: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(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.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) 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:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Code:yauth.CAPTCHA_REQUIRED at com.zimbra.common.soap.Soap12Protocol.soapFault(Soap12Protocol.java:88) at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:344) at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:303) at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:260) at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:164) at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:397) at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:360) at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:321) at com.zimbra.cs.account.soap.SoapProvisioning.createAccount(SoapProvisioning.java:464) at com.zimbra.cs.offline.jsp.JspProvStub.createOfflineDataSource(JspProvStub.java:126) at com.zimbra.cs.offline.jsp.XmailBean.doRequest(XmailBean.java:267) at com.zimbra.cs.offline.jsp.YmailBean.doRequest(YmailBean.java:44) at com.zimbra.cs.offline.jsp.FormBean.doRequest(FormBean.java:150) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.el.parser.AstFunction.getValue(AstFunction.java:127) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206) at org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:1001) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_when_5(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_choose_0(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspService(Unknown Source) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814">HttpServlet.service(HttpServlet.java:814) at com.zimbra.webClient.servlet.JspServlet.service(JspServlet.java:64) 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 com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:239) 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:218) 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: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(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.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) 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:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)


phoenix
Ambassador
Ambassador
Posts: 26699
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

YMail no longer can connect

Postby phoenix » Sun Jul 24, 2011 10:52 am

How about telling us which version of Zimbra Desktop you're using? If it's not the current ZD 7.1 beta then I'd suggest downloading and using that (make sure you read the documentation and the product FAQ before installing it, you should also backup your user data).
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
jsmneedshelp
Posts: 6
Joined: Sat Sep 13, 2014 2:08 am

YMail no longer can connect

Postby jsmneedshelp » Sun Jul 24, 2011 11:44 am

Hi. Thanks for the quick reply.
Very valid question on the version. According to the Read me file it is:

7.0.1 (build 10791)
Not sure if there is another way to tell as there doesn't appear to be another way to determine the version. This was from like 2 weeks ago (if that).
Your email says I should upgrade to 7.1. But the website only lists 7.01 as the latest. Is there some hiddent 7.1 beta version? And will this really materially impact this error? My guess is no...
Please advise.
Annoyed
Posts: 6
Joined: Sat Sep 13, 2014 12:48 am

YMail no longer can connect

Postby Annoyed » Wed Jul 27, 2011 2:03 am

EDIT: Rude comments removed. Since Zimbra is no longer owned by Yahoo, I was out of line and an apology is due.
Zimbra has no further need to support Yahoo policy changes. If you are locked out of Zimbra access by Yahoo or any other webmail provider, you can install Thunderbird Portable instead

along">http://portableapps.com/apps/internet/thunderbird_portable
along
with appropriate Webmail add-ins and be up and running in a few minutes.
http://webmail.mozdev.org/
phoenix
Ambassador
Ambassador
Posts: 26699
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

YMail no longer can connect

Postby phoenix » Wed Jul 27, 2011 4:19 am

[quote user="Annoyed"]Zimbra has no further need to support Yahoo policy changes. If you are locked out of Zimbra access by Yahoo or any other webmail provider, you can install Thunderbird Portable instead[/QUOTE]If you search bugzilla you will find an RFE for support of 'captcha' verification, vote on it if you like.
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
fyd
Outstanding Member
Outstanding Member
Posts: 356
Joined: Sat Sep 13, 2014 1:36 am

YMail no longer can connect

Postby fyd » Wed Jul 27, 2011 5:44 am

[quote user="jsmneedshelp"]Not sure if there is another way to tell as there doesn't appear to be another way to determine the version. This was from like 2 weeks ago (if that).

Please advise.[/QUOTE]
Hello, look for the heading "How do I know which version/build I'm running?" in the zimbra official doc. Zimbra Desktop 2 FAQ - Zimbra :: Wiki
[quote user="jsmneedshelp"]

Your email says I should upgrade to 7.1. But the website only lists 7.01 as the latest. Is there some hiddent 7.1 beta version? And will this really materially impact this error? My guess is no...

[/QUOTE]
The beta downloads page is very next to the latest build link. Zimbra - Products: Zimbra Desktop Beta Downloads
I'm quoting what Bill stated. It will give you some idea on the build.

[QUOTE](make sure you read the documentation and the product FAQ before installing it, you should also backup your user data).[/QUOTE]

I cannot confirm if it will solve your problem, but its good to try.
Annoyed
Posts: 6
Joined: Sat Sep 13, 2014 12:48 am

YMail no longer can connect

Postby Annoyed » Wed Jul 27, 2011 10:16 am

I'll not be voting for captcha verification.



If Zimbra were still a Yahoo product I would expect it to work, but bothering new owners about Yahoo silliness is inappropriate. I'd not noticed the VMWare buyout hence rant withdrawn from previous post.
If anything, don't support Yahoo since the only people still running it are using legacy addresses and Yahoo was content to dump Zimbra. Turnabout is fair play, and enterprises don't need to cater to webmail accounts since they have their own domains.
fyd
Outstanding Member
Outstanding Member
Posts: 356
Joined: Sat Sep 13, 2014 1:36 am

YMail no longer can connect

Postby fyd » Wed Jul 27, 2011 12:10 pm

[quote user="Annoyed"]

If anything, don't support Yahoo since the only people still running it are using legacy addresses and Yahoo was content to dump Zimbra. Turnabout is fair play, and enterprises don't need to cater to webmail accounts since they have their own domains.[/QUOTE]

I would agree to that hatred against yahoo. But I guess it isn't clever and practical to turn back at them .. atleast from a business point of view.
jsmneedshelp
Posts: 6
Joined: Sat Sep 13, 2014 2:08 am

YMail no longer can connect

Postby jsmneedshelp » Wed Jul 27, 2011 1:03 pm

Well, at least we've got some replies.
First off, after getting a bunch of useless boilerplate answers back from Yahoo, I finally got an answer stating that I could call their "account verification" department at 866-562-7219
But, I decided to give adding the YMail account again to Zimbra. Lo and behold it successfully created a new account. I had not attempted this in over 48 hours due to travel. Did time heal all wounds? Who knows...
Also, I hardly want to start a flamewar, or get into it about Yahoo, but I think that stating that no one needs to use yahoo email addresses is a bit biased. I suppose it is my "legacy" address, but why would i want to give up my address I've had for over 15 years that is my name @ yahoo? YMail and Yahoo may have their issues, but, it has great spam control and I find very little wrong with it (except this last issue). Hopefully Zimbra will continue to support it....
phoenix
Ambassador
Ambassador
Posts: 26699
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

YMail no longer can connect

Postby phoenix » Wed Jul 27, 2011 1:48 pm

[quote user="jsmneedshelp"]Hopefully Zimbra will continue to support it....[/QUOTE]There would be no reason to do otherwise, it's a popular mail service. :)
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra

Return to “Error Reports”

Who is online

Users browsing this forum: No registered users and 2 guests