Cannot get external account collection working

[sparticle]

I cannot get any external accounts to work. When I setup the external account and press the test button I get a dialog box with the following error

Error: SSL peer shut down incorrectly
Note: If you continue to save, account will be marked inactive.
Press Cancel to return to editing accounts.

The account details are fine and can be logged into form the same client machine. I have tried various external accounts with different providers and the error is the same.

Also nothing shows up in the zimbra log file when I watch in real time as I press the test button.

I really need this feature to work otherwise zimbra is not going to work for us.

Any help apprecaited.

Cheers
Stephen
Edit/Delete Message

[phoenix]

Have a look in your /opt/zimbra/log/mailbox.log and see if you have any errors in there that relate to certificate problems, you can grep the file for "fatal alert".

[sparticle]

Bill,

Many thanks for your support, PSB the log output.

Originally Posted by phoenix

Have a look in your /opt/zimbra/log/mailbox.log and see if you have any errors in there that relate to certificate problems, you can grep the file for "fatal alert".

2010-10-31 14:09:23,382 INFO [btpool0-14://zimbra.local.home:7071/service/admin/soap/NoOpRequest] [name=admin@zimbra.local.home;mid=1;ip=192.168.0.35 ;ua=ZimbraWebClient - FF3.0 (Win);] soap - NoOpRequest
2010-10-31 14:09:35,513 INFO [MailboxPurge] [name=spam.zyuqoxzu@zimbra.local.home;mid=3;] purge - Purging messages.
2010-10-31 14:10:03,478 INFO [btpool0-1://zimbra/service/soap/TestDataSourceRequest] [name=user@zimbra.local.home;mid=2;ip=192.168.0.35; ua=ZimbraWebClient - FF3.0 (Win)/7.0.0_BETA1_2816;] soap - TestDataSourceRequest
2010-10-31 14:10:03,483 INFO [btpool0-1://zimbra/service/soap/TestDataSourceRequest] [name=user@zimbra.local.home;mid=2;ip=192.168.0.35; ua=ZimbraWebClient - FF3.0 (Win)/7.0.0_BETA1_2816;] datasource - Testing: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=external.mail.server, port=143, connectionType=cleartext, username=user@external.mail.account, folderId=-1 }
2010-10-31 14:10:07,765 WARN [btpool0-1://zimbra/service/soap/TestDataSourceRequest] [name=user@zimbra.local.home;mid=2;ip=192.168.0.35; ua=ZimbraWebClient - FF3.0 (Win)/7.0.0_BETA1_2816;] datasource - Test failed: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=external.mail.server, port=143, connectionType=cleartext, username=user@external.mail.account, folderId=-1 }
com.zimbra.common.service.ServiceException: system failure: Unable to connect to IMAP server: DataSource: { id=TestId, type=imap, isEnabled=false, name=Test, host=external.mail.server, port=143, connectionType=cleartext, username=user@external.mail.account, folderId=-1 }
ExceptionId:btpool0-1://zimbra/service/soap/TestDataSourceRequest:1288534207764:ad4f975b9c3c33 a2
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.datasource.imap.ConnectionManager.ne wConnection(ConnectionManager.java:166)
at com.zimbra.cs.datasource.imap.ConnectionManager.op enConnection(ConnectionManager.java:84)
at com.zimbra.cs.datasource.imap.ImapSync.connect(Ima pSync.java:111)
at com.zimbra.cs.datasource.imap.ImapSync.test(ImapSy nc.java:73)
at com.zimbra.cs.datasource.DataSourceManager.test(Da taSourceManager.java:181)
at com.zimbra.cs.service.mail.TestDataSource.handle(T estDataSource.java:129)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:426)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:280)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:293)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:214)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
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:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:418)
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.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:413)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1120)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1147)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHa ndshake(SSLSocketImpl.java:1131)
at com.zimbra.common.net.CustomSSLSocket.startHandsha ke(CustomSSLSocket.java:90)
at com.zimbra.cs.mailclient.MailConnection.startTls(M ailConnection.java:108)
at com.zimbra.cs.mailclient.MailConnection.connect(Ma ilConnection.java:92)
at com.zimbra.cs.datasource.imap.ConnectionManager.ne wConnection(ConnectionManager.java:144)
... 40 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
... 47 more
2010-10-31 14:10:15,503 INFO [btpool0-1://localhost:7071/service/admin/soap/AuthRequest] [ip=127.0.0.1;ua=zmprov/7.0.0_BETA1_2816;] soap - AuthRequest
2010-10-31 14:10:16,431 INFO [btpool0-1://localhost:7071/service/admin/soap/GetAllServersRequest] [name=zimbra;ip=127.0.0.1;ua=zmprov/7.0.0_BETA1_2816;] soap - GetAllServersRequest
2010-10-31 14:10:32,298 INFO [Timer-Zimbra] [] SessionCache - Removed 1 idle sessions (ADMIN). 3 active sessions remain.
2010-10-31 14:10:35,697 INFO [MailboxPurge] [name=ham.lvr_geiurc@zimbra.local.home;mid=4;] purge - Purging messages.

I have also tried this with the clear text setting FALSE

[zimbra@zimbra ~]$ zmprov mcf zimbraImapCleartextLoginEnabled FALSE

Above messages happen whenever I press the test button. The external mail server is not using SSL I can login to it using any mail client like thunderbird with the details I supplied on port 143 and the account and password details.

Any suggestion would be really helpful, as without this feature zimbra will not work for us. Currently everything else is working. local to local, local to external, masquearading.

Cheers
Stephen

[sparticle]

Having re read the documentation. This must be a bug. I cannot find anything that seems to point to any flag or other setting that affects the behaviour of this tab in the account preferences.

We are simply providing server, username and password info for the external account.

Now completely stumped.

Cheers
Stephen

[phoenix]

Originally Posted by sparticle

Having re read the documentation. This must be a bug.

I would tend to agree with you. I see you're using the 7.x beta, do you have a 6.0.x version server available to test the external connections? In any case can you try the following:

openssl s_client -host external_server -port 995

That should get details of your certificate, if you can test that on a 6.0.x server then please file a bug report with full details of the problem and log output - mark the bug private if there's any confidential information in it.

[sparticle]

Thanks for the note Bill,

Originally Posted by phoenix

I would tend to agree with you. I see you're using the 7.x beta, do you have a 6.0.x version server available to test the external connections?

No I don't have a 6.x server. I guess I could blat this install and re-install with the last GA version. Just reluctant to do this now we have the base server working apart from the external account inssues, but if there is nothing else to check this looks like the only answer.

Originally Posted by phoenix

In any case can you try the following:

openssl s_client -host external_server -port 995

That should get details of your certificate, if you can test that on a 6.0.x server then please file a bug report with full details of the problem and log output - mark the bug private if there's any confidential information in it.

The command seems to find the certificate fine with no errors.

Cheers
Stephen

[phoenix]

Originally Posted by sparticle

No I don't have a 6.x server. I guess I could blat this install and re-install with the last GA version.

There is a section in bugzilla for the 7.x release but that's normally for released version, you can try your luck in filing a report against that.

[sparticle]

Started again with 6.0.8 GA release. Weird that the DNS config fot 2 beta did not work for 6.0.8.

Had to start again.

Hopefuly I can get the thing working and external accoutns work on this verison.

Cheers
Stephen

[sparticle]

6.0.8 does exactly the same thing. I am sure there are other that have got thi sworking but this falls into the category of too hard. I can't see the point in producing an admin gui that does not give you enough control of the basic functions of a mail server.

Like external authentication and relay functions. Too much like black magic that you have to piece together.

Looks like my Mdaemon server lives on.....

Cheers
Stephen

[fyd]

Struck the same way as stephen. Configuring extenal account first showed

Error: SSL peer shut down incorrectly.

But then I tried giving 'javamail_imap_enable_starttls' as false in localconfig.xml and restarting mailbox. Well before it was a blow and then it gave me a kick!

Error: Re-Authentication Failure

grepping for error in /opt/zimbra/log/mailbox.log gives me nothing, so she is just messing with me. Sometimes I get this too while trying the same way

Error: Generic Test Failure

Bill can you confirm if this is a bug? cause I am using 6.0.8! Before testing with 8 I had the same results with 6.0.7.