Nach UCS Update (5.0-0 errata174) keine Verbindung zu externen Mail-Accounts in OX-APP 7.10.5-ucs4

[carstens]

Hallo nach Update unter Berücksichtigung folgenden Workarround:

Problem: OX Update fails

Problem An update of oxforucs fails with the following traceback in the updater.log: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/univention/management/console/base.py", line 344, in __error_handling six.reraise(etype, exc, etraceback) File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise raise value File "/usr/lib/python3/dist-packages/univention/management/console/base.py", line 247, in execute function.__func__(self, request, *args, **kwargs) File "/u…

echo ‘Acquire::AllowReleaseInfoChange::Suite “true”;’ > /etc/apt/apt.conf.d/50bug54099`

Ist in der App-Suite meines Kunden keine Verbindung zu ext. Mailadressen möglich, nachfolgen der Log:

/var/log/open-xchange/open-xchange.log.0 [----] 22 L:[1897+14 1911/2005] (159561/167510b) 0122 0x07A [][X]
at net.jodah.failsafe.SyncFailsafe.call(SyncFailsafe.java:145)
at net.jodah.failsafe.SyncFailsafe.get(SyncFailsafe.java:56)
at com.openexchange.mail.MailServletInterfaceImpl.executeWithRetryOnUnexpectedConnectionClosure(MailServletInterfaceImpl.java:5278)
at com.openexchange.mail.MailServletInterfaceImpl.getAllSimpleThreadStructuredMessages(MailServletInterfaceImpl.java:1363)
at com.openexchange.mail.json.actions.SimpleThreadStructureAction.perform0(SimpleThreadStructureAction.java:368)
at com.openexchange.mail.json.actions.SimpleThreadStructureAction.perform(SimpleThreadStructureAction.java:185)
… 28 common frames omitted
2022-01-26T11:36:50,149+0100 ERROR [OXWorker-0000163] com.openexchange.ajax.requesthandler.DispatcherServlet.logException(DispatcherServlet.java:706)
Error processing request.
com.openexchange.ajax.action=all
com.openexchange.ajax.module=mail
com.openexchange.grizzly.method=GET
com.openexchange.grizzly.queryString=action=all&folder=default4%2FINBOX&columns=102%2C600%2C601%2C602%2C603%2C604%2C605%2C606%2C607%2C608%2C609%2C610%2C611%2C614%2C652%2C656%2C661%2CX-Open-Xchange-Share-URL%2C662&sort=661&order=desc&deleted=true&timezone=utc&limit=0%2C50&se
com.openexchange.grizzly.remoteAddress=172.17.158.54
com.openexchange.grizzly.remotePort=43928
com.openexchange.grizzly.requestURI=/ajax/mail
com.openexchange.grizzly.serverName=172.17.158.40
com.openexchange.grizzly.servletPath=/ajax/mail
com.openexchange.grizzly.threadName=OXWorker-0000163
com.openexchange.grizzly.userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0
com.openexchange.hostname=172.17.158.40
com.openexchange.localhost.ipAddress=172.17.158.40
com.openexchange.localhost.version=7.10.5-Rev31
com.openexchange.mail.accountId=4
com.openexchange.mail.host:993=imap.1und1.de
com.openexchange.mail.host.remoteAddress=212.227.15.188
com.openexchange.mail.login=xxxx@xxxxx-braunschweig.de
com.openexchange.mail.session=89826627022a4bb08b03c5228802c0cd-6-10-e0adedb40022ed35
com.openexchange.request.trackingId=911699721-455850613
com.openexchange.session.authId=3815d6e7654945da9932f715fe83cbd9
com.openexchange.session.clientId=open-xchange-appsuite
com.openexchange.session.contextId=10
com.openexchange.session.loginName=xxxxxx
com.openexchange.session.sessionId=89826627022a4bb08b03c5228802c0cd
com.openexchange.session.userId=6
com.openexchange.session.userName=xxxxxx
javax.servlet.queryString=action=all&folder=default4%2FINBOX&columns=102%2C600%2C601%2C602%2C603%2C604%2C605%2C606%2C607%2C608%2C609%2C610%2C611%2C614%2C652%2C656%2C661%2CX-Open-Xchange-Share-URL%2C662&sort=661&order=desc&deleted=true&timezone=utc&limit=0%2C50&session=89826
javax.servlet.servletPath=/ajax/mail
com.openexchange.exception.OXException: MSG-0008 Categories=ERROR Message=‘An I/O error occurred: Received BYE response from IMAP server: * BYE out-of-sync data before server greeting’ exceptionID=-911699721-446
com.openexchange.exception.locale: de_DE
at com.openexchange.exception.OXExceptionFactory.create(OXExceptionFactory.java:154)
at com.openexchange.exception.OXExceptionFactory.create(OXExceptionFactory.java:144)
at com.openexchange.exception.OXExceptionFactory.create(OXExceptionFactory.java:117)
at com.openexchange.mail.MailExceptionCode.create(MailExceptionCode.java:752)
at com.openexchange.imap.IMAPServerInfo.instanceFor(IMAPServerInfo.java:57)
at com.openexchange.imap.IMAPFolderWorker.(IMAPFolderWorker.java:198)
at com.openexchange.imap.IMAPMessageStorage.(IMAPMessageStorage.java:392)
at com.openexchange.imap.IMAPAccess.getMessageStorage(IMAPAccess.java:1165)
at com.openexchange.imap.IMAPAccess.getMessageStorage(IMAPAccess.java:121)
at com.openexchange.mail.MailServletInterfaceImpl.getMessageRange(MailServletInterfaceImpl.java:2622)
at com.openexchange.mail.MailServletInterfaceImpl.getMessagesInternal(MailServletInterfaceImpl.java:2438)
at com.openexchange.mail.MailServletInterfaceImpl$26.call(MailServletInterfaceImpl.java:2400)
at com.openexchange.mail.MailServletInterfaceImpl$26.call(MailServletInterfaceImpl.java:2396)
at net.jodah.failsafe.SyncFailsafe.call(SyncFailsafe.java:145)
at net.jodah.failsafe.SyncFailsafe.get(SyncFailsafe.java:56)

Gibt es hierzu Lösungen?
Gruß
Carsten S.

[DirkS]

Ich sehe jetzt erst einmal keinen Zusammenhang zwischen dem Workaround, der lediglich erlaubt, dass sich das Repo beim Update ändern darf und dem Konnektivitätsproblem.
Ich denke, dass Open Exchange für das Problem der bessere Ansprechpartner ist. Der Server erhält eine BYE Response bevor die Server die Verbindung überhaupt aufgebaut haben.

Kommt man manuell vom OX Server auf den entfernten Mailserver und kann man mit dem “sprechen”?

telnet 212.227.15.188
oder
nc --crlf --verbose 212.227.15.188

[carstens]

Hallo Dirk,
ja den Zusammenhang sehe ich auch nicht und manuell komme ich auf den Mailserver von 1und1.
Leider wird nicht genauer geloggt.