MAPIProvider->imtoinet(): got no stream or content from mapi_inetmapi_imtoinet()

deHoeninger

Hi @Manfred
I’ve already provided a wbxml log, so what additional information should I take from Felix post? I only told you in my last post, thats inposible to provide you the requested eml file, cause in Outlook mail is not present/empty and in WebApp export of this particular email is failing with a MAPI error.
Nevertheless, I’ve enabled the raw log message parameter but this will only catch future mails.
Best Jan

Manfred

Hi Jan,

@deHoeninger said in MAPIProvider->imtoinet(): got no stream or content from mapi_inetmapi_imtoinet():

Hi @Manfred
I’ve already provided a wbxml log, so what additional information should I take from Felix post? I only told you in my last post, thats inposible to provide you the requested eml file, cause in Outlook mail is not present/empty and in WebApp export of this particular email is failing with a MAPI error.
Nevertheless, I’ve enabled the raw log message parameter but this will only catch future mails.

my comment was regarding the log_raw_message parameter. I’m aware that this will only work with the future emails, but the current Z-Push WBXML log is not helpful because it doesn’t contain the email body and you said that the email body is not empty, so we have to debug what kind of incoming emails cause this issue.

Manfred

deHoeninger

@Manfred
Understood, I will try to collect some more information and will come back to you.

Best Jan

robgnu

@Manfred
I’ve sent you an Link to a WBXML file I’ve created yesterday. I hope it helps debugging.
bye, robgnu.

robgnu

@fbartels said in MAPIProvider->imtoinet(): got no stream or content from mapi_inetmapi_imtoinet():

But koe has no influence on the connection between Outlook and the server.

Ok, I will give it another try and give you a reply. Thanks.

fbartels

Hi everyone,

thanks for your input. We have an idea where to problem could result from and a case to reproduce the issue. I have created https://jira.kopano.io/browse/KC-1351 for followup.

deHoeninger

Hi @fbartels
I’ve noticed, that a possible fix was merged to the 8.6.x branch. Can we expect a merge to Master as well? I would be happy to have a working nightly soon.

Best Jan

fbartels

Hi @deHoeninger ,

yes it will eventually trickle down into the master branch.

BusinessTux

Hi, everybody,

is the described error also the cause for completely empty emails in Outlook, which are connected via KOE?

0_1543431696725_513f6323-6d9f-4729-b16c-0e4d5eb8f982-grafik.png

I use Outlook 2016 with Kopano on UCS

UCS: 4.3-2 errata332
Installed: cups=2.2.1 dhcp-server=12.0 kopano-core=8.6.8.2 kopano-webapp=3.4.22.1782 nagios=4.3 pkgdb=11.0 samba4=4.7 squid=3.5 z-push-kopano=2.4.4

kopano-server                                       8.6.8.10-0+23.1
kopano-webapp                                       3.4.24.1929+84.1
z-push-kopano                                       2.4.5+0-0

Thanks
Ulf

fbartels

@BusinessTux see https://forum.kopano.io/topic/1847/empty-mails-with-kopano-ol-extension

Ps: there is already a 8.6.9 in our repositories which will resolve the issue.

darootler

I am receiving this error too with the following versions:

Kopano 8.7.80
Z-Push 2.4.5

Should that already be fixed?

Regards
Richard

deHoeninger

@darootler

As far as I know, there is already a fix and it should be already part of the git-Master. But no new nighlty build so far.

So at least with no valid subscription, we still have to wait for an updated version to download.

Best Jan

BusinessTux

Thanks @fbartels

With
kopano-server kopano-server 8.6.9.0-0+24.1,
z-push-kopano 2.4.5+0-0,
KopanoOLExtension-2.0-331

from final repository the most emails are readable again. The last two email, which where still empty, I moved to subfolder and then I could read it.

Regards
Ulf

deHoeninger

@fbartels

Is there already a schedule for an upcoming Nightly Build, last one is from 20th of Nov.

Best Jan

joja

My Outlook is looking like the picture @BusinessTux posted. Messages completely empty.

z-push.log shows: 06/12/2018 09:56:31 [44833] [ERROR] [jstahl] MAPIProvider->imtoinet(): got no stream or content from mapi_inetmapi_imtoinet()

I’m using Univention UCS 4.3-2 and installed Kopano via the App Center.

apt list output:

kopano4ucs/unbekannt,now 1.5.13 all
kopano-server/unbekannt,now 8.6.8.10-0+23.1 amd64
kopano-webapp/unbekannt,now 3.4.22.1782+80.1 all
z-push-kopano/unbekannt,now 2.4.4+0-0 all

I tried univention-upgrade but I cannot get kopano-server 8.6.9.0-0+24.1. How can I get them?

–
Jojakim

fbartels

@deHoeninger i am currently not in the office, but the last I know is that nightly uploads were failing because of failing builds for Rhel/centos (because of missing python3). I have the feeling that we should disable Rhel builds until dependencies can be resolved again. Will make that a topic next week.

@joja 8.6.9 is available from the Kopano repository (if you have a Kopano subscription). You can enable it from the app settings in the Univention app center.

joja

@joja 8.6.9 is available from the Kopano repository (if you have a Kopano subscription). You can enable it from the app settings in the Univention app center.

Is there any plan when this will be available via regular Univention app center?

–
Jojakim

fbartels

Hi @joja,

I have no immediate plans to upload this version to the appcenter. But a Kopano subscription already starts at 75€ for up to five users. See https://kopano.com/pricing/

robgnu

Hello,
what is about migration? When I am using the latest community build, can I simply change to the latest subscription version without database trouble? The latest community build is much newer, I think?

Thanks.
Robert

fbartels

@robgnu said in MAPIProvider->imtoinet(): got no stream or content from mapi_inetmapi_imtoinet():

When I am using the latest community build, can I simply change to the latest subscription version without database trouble?

I can’t say. We are only testing upgrades, not downgrades. Generally speaking a downgrade to the 8.7 release should be easier. This should materialise next week.