Upgrade from 5.0.18->6.0 External Pop?

[dselvey]

Before the upgrade i had Windows Live mail being fetched perfectly.

Now i get "leaving messages on server requires support for UIDL" even if i choose delete messages on the server?

A few of my users have the same issue.

Is there a solution to this?

[Hivos]

Exactly the same problem here. Haven't found a solution though...

[gregor]

hi,

i have the same problem anybody found a solution?

gregor

[dselvey]

Is there no solution for this?

Cheers

[Hivos]

Filed a bug report for this one:

Bug 41213 – Upgrade from 5.0.18 to 6.0.0 breaks external pop hotmail

[karlmdavis]

Just to confirm: yes, this feature worked in ZCS 5.x, but the upgrade to ZCS 6.x broke it. It is not fixed as of 6.0.1. Apparently, the bug was present in earlier versions of the Zimbra desktop and has migrated into ZCS as of the 6.0 release.

My users are trying to access external POP accounts from Hotmail/Windows Live Mail and are running into this bug. Unfortunately, they very much need to leave messages on the server.

Please be sure to vote for Bug #30643 and Bug #41213 to let the Zimbra team know this bug is important to resolve.

[profondorosso]

The same error with any pop3/pop3s account, not only hotmail.
with ZCS OSS 5 --> all work fine
after upgrade Release 6.0.1_GA_1816.UBUNTU8 UBUNTU8 FOSS edition ...
doesn't work !!!

I hope someone can help us.

bye
R.

the output of "zmprov gds account@domain.net":

# name ABCD
# type pop3
objectClass: zimbraDataSource
objectClass: zimbraPop3DataSource
zimbraDataSourceConnectionType: ssl
zimbraDataSourceEmailAddress: foo@bar.it
zimbraDataSourceEnabled: FALSE
zimbraDataSourceFailingSince: 20091001125552Z
zimbraDataSourceFolderId: 2
zimbraDataSourceHost: mail.bar.it
zimbraDataSourceId: 3e98e824-9391-4e9b-b2d2-4439c7abccdc
zimbraDataSourceLastError: system failure: Unable to connect to POP3 server: DataSource: { id=3e98e824-9391-4e9b-b2d2-4439c7abccdc, type=pop3, isEnabled=false, name=FOOBAR, host=mail.bar.it, port=995, connectionType=ssl, username=foo, folderId=2 }, java.security.cert.CertificateException: d2:CN12:mail.bar.it1:O8:ABCD spa2:OU22:Area Sistemi - WebMail6:accept4:true5:alias14:mail.bar.it:94:from i1224054543000e4:host12:mail.bar.it3:icn11:www.bar.it2:io8:ABCD Spa3:iou15:Networking Unit3:md532:4AB6B27714F1FBD25133E9683A90C9B48:mism atch5:false1:s1:94:sha140:69AA10201851179B3ABB7C62 4580CC5FFFFAFA812:toi1350198543000ee, d2:CN12:mail.bar.it1:O8:Kion spa2:OU22:Area Sistemi - WebMail6:accept4:true5:alias14:mail.bar.it:94:from i1224054543000e4:host12:mail.bar.it3:icn11:www.bar.it2:io8:ABCD Spa3:iou15:Networking Unit3:md532:4AB6B27714F1FBD25133E9683A90C9B48:mism atch5:false1:s1:94:sha140:69AA10201851179B3ABB7C62 4580CC5FFFFAFA812:toi1350198543000ee
zimbraDataSourceLeaveOnServer: FALSE
zimbraDataSourceName: ACBD
zimbraDataSourcePollingInterval: 180
zimbraDataSourcePort: 995
zimbraDataSourceType: pop3
zimbraDataSourceUsername: foo
zimbraPrefFromAddress: foo@bar.it
zimbraPrefFromDisplay: Foo Bar


the mailbox.log ...


2009-10-01 16:03:12,593 WARN [btpool0-14] [name=xxxx@xxxxxxxxx.net;mid=3;ip=192.168.5.1;ua=Zi mbraWebClient - FF3.0 (Win)/6.0.1_GA_1816.UBU
NTU8;] datasource - Test failed: DataSource: { id=TestId, type=pop3, isEnabled=false, name=Test, host=mail.bar.it, port=995, connectionType
=ssl, username=foo, folderId=-1 }
com.zimbra.common.service.ServiceException: system failure: Unable to connect to POP3 server: DataSource: { id=TestId, type=pop3, isEnabled=
false, name=Test, host=mail.bar.it, port=995, connectionType=ssl, username=foo, folderId=-1 }
ExceptionId:btpool0-14:1254405792593:e1b3e2578e8d496c
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:251)
at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:136)
at com.zimbra.cs.datasource.Pop3Sync.test(Pop3Sync.ja va:81)
at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:57)
at com.zimbra.cs.service.mail.TestDataSource.handle(T estDataSource.java:125)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:417)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:272)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:187)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1148)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:129)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1139)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:378)
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:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:417)
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.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:517)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:868)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:386)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: d2:CN12:mail.bar.it1:O8:ABCD spa2:OU22:Area Sistem
i - WebMail6:accept4:true5:alias14:mail.bar.it:94:from i1224054543000e4:host12:mail.bar.it3:icn11:www.bar.it2:io8:ABCD Spa3:iou15:Networki
ng Unit3:md532:4AB6B27714F1FBD25133E9683A90C9B48:mism atch5:false1:s1:94:sha140:69AA10201851179B3ABB7C62 4580CC5FFFFAFA812:toi1350198543000ee
at com.sun.net.ssl.internal.ssl.Alerts.getSSLExceptio n(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(S SLSocketImpl.java:1611)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:187)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Ha ndshaker.java:181)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:1035)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.proc essMessage(ClientHandshaker.java:124)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoo p(Handshaker.java:516)
at com.sun.net.ssl.internal.ssl.Handshaker.process_re cord(Handshaker.java:454)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:884)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1139)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1123)
at com.zimbra.common.util.CustomSSLSocket.startHandsh ake(CustomSSLSocket.java:213)
at com.zimbra.common.util.CustomSSLSocket.getInputStr eam(CustomSSLSocket.java:347)
at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:83)
at com.zimbra.cs.datasource.Pop3Sync.connect(Pop3Sync .java:128)
... 34 more
Caused by: java.security.cert.CertificateException: d2:CN12:mail.bar.it1:O8:ABCD spa2:OU22:Area Sistemi - WebMail6:accept4:true5:alias14:ma
il.bar.it:94:fromi1224054543000e4:host12:mail.bar. it3:icn11:www.bar.it2:io8:ABCD Spa3:iou15:Networking Unit3:md532:4AB6B27714F1FBD25133E9
683A90C9B48:mismatch5:false1:s1:94:sha140:69AA1020 1851179B3ABB7C624580CC5FFFFAFA812:toi1350198543000 ee
at com.zimbra.common.util.CustomTrustManager.checkSer verTrusted(CustomTrustManager.java:89)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serv erCertificate(ClientHandshaker.java:1027)
... 45 more

[profondorosso]

Errata corrige: the trouble is only for "pops" account.
with "pop" cleartext is working
Ciao,
DR

[Hivos]

^^ Thanks, I have updated the bugtracker

[LeoOfVenice]

Please tell me why in bugzilla

https://bugzilla.zimbra.com/show_bug.cgi?id=41213

SEE ALSO



this bug seems Status: RESOLVED

but I've installed version 6.0.2 and I have ever the same problem ....