Kopano Core 8.4.0 Sender Problems after upgrade

schmidt

Hi,

I have the same problems.

Some E-Mails does not open
empty recipient field when I answer a email.

Regards

MarcusRieche

The opening of e-mails is already mentionend here: https://forum.kopano.io/topic/296/bugreport-kc-8-4-0-667_139-error-while-accessing-html-mail-items-in-webapp/10

Also have the issue with missing sender informationen with devices using active sync / z-push.

Ubuntu 16.04
Core 8.4.0-728
WebApp 3.4.0.686-479.1
Z-Push 2.3.6

Sync with Nine on Android gives the effect of myself being the sender. Samsung Mail on Android just leaves the sender empty. Both have no recipient when pressing reply. So it is just empty.

fbartels

I have by now opened https://jira.kopano.io/browse/KC-709 to track these and similar reports.

@schmidt which versions of Kopano are you using and on which distribution?

MarcusRieche

@MacusRieche said in Kopano Core 8.4.0 Sender Problems after upgrade:

Ubuntu 16.04
Core 8.4.0-728
WebApp 3.4.0.686-479.1
Z-Push 2.3.6

Sync with Nine on Android gives the effect of myself being the sender. Samsung Mail on Android just leaves the sender empty. Both have no recipient when pressing reply. So it is just empty.

updated

fbartels

@MacusRieche thanks. a lot of different versions were reported, so its hard to keep track of everyone.

yep_DD

Okay, so at least I wasn’t the only one. I tried older versions of Z-Push 3.0->3.6 and also Webapp 3.4.0 and 3.30. The problem seems to be linked solely to Kopano Core. I can also confirm the iOS issues @MacusRieche

edit: Debian 8.8, 64-bit

MarcusRieche

@fbartels I see in the ticket you have trouble reproducing the z-push issue.
With Core-8.4.0-728 I see errors like these in the z-push-error.log

06/06/2017 10:32:13 [31228] [WARN] [hermann] SyncObject->Check(): object from type SyncMail: parameter ‘from’ contains an invalid email address ‘“notebooksbilliger.de” <>’. Address is removed.

This kind of message usually occurs regarding the to field. For example for undisclosed recipients or or just my name as receiver. That is not nessecary right and was always kind of wrong, since I was cleary the recipient and nine mail on android seems to replace empty from fields with my own address this was never an issue. Missing sender information in the from field is an issue.

I can try to help to debug this issue in the next days, if you want me to take special steps.

Hello same problem here. Happens after upgrading from ,core-8.4.0~344_74.1-Ubuntu_16.04-amd64" to ,core-8.4.0~792_150.1-Ubuntu_16.04-amd64".

With ,core-8.4.0~344_74.1-Ubuntu_16.04-amd64" everything was fine. But downgrading to this version doens’t help.

MarcusRieche

@Roger You may need to force a complete resync of a device. Cause there is no need to update already downloaded mails.

fbartels

@MarcusRieche that was my thought as well. If the error still persists either the webserver wasn’t restarted and the version of php-mapi is still in use or he is speaking about messages synced to mobile devices. The latter requires a resync.

@fbartels Resync didn’t helped (over Z-push right)? I have this problem after upgrading Kopano Core in mobile devices and WebApp. I restarted the entire Kopano Server after upgrade to ensure that everything is “fresh” loaded and this issue is still there. It’s also inconsistent . Some sender are not in WebApp but in mail Client (Nine Android). Some in the another direction.

MarcusRieche

@Roger Yes resync using z-push. By restarting entire kopano server you meant the whole machine? Because you should restart restart the web server/apache, too.

@MarcusRieche Yes whole machine. The webserver Apache2 also.

Seems to be fixed for me with ,core-8.4.0~813_153.1-Ubuntu_16.04-amd64.tar.gz". Older messages has still the problem but new messages not more that sender is not visible or the error message ,Message coulnd’t be loaded" in WebApp.

MarcusRieche

Did not occur again in 8.4.0-813. Fixed.

fbartels

Hi, thanks for all your feedback. I did not yet have the time to verify the fix myself, but its good to hear that the issue has been resolved for you.