feedback: z-push package from z-push repo ( debian stretch )

thctlo

Hai,

I notice the following in the packages of z-push
Some minor things.

The old config file : config.php

Created : 01.10.2007

new config file z-push.conf.php

Created : 01.10.2007

i dont believe that the z-push.conf.php is created in 2007,.

Adding Version number in the config files whould be great, that makes it more easy to track changes. … Yes i did see “version.php” also in the web folder. ;-)

The installer does not check if the current folder is a folder.
in my case it was a symlink to z-push-2.3.1
i suggest, in case of a symlink, rename it and create a new folder.
the logrotate can be bit better.
The ADM group should be able to read these logs.
This works fine : create 640 www-data adm
the z-push autodiscovery.
I noticed the small problem with some devices. ! i have not checked if this is still the case but
i used :
Alias /Autodiscover/Autodiscover.xml /usr/share/z-push/autodiscover/autodiscover.php
Alias /AutoDiscover/AutoDiscover.xml /usr/share/z-push/autodiscover/autodiscover.php
Alias /autodiscover/autodiscover.xml /usr/share/z-push/autodiscover/autodiscover.php

Sorry cant recall which devices, i use these for years now.
(Im oldschool zarafa users as of 4.x )

So some small suggestions that make life bit more easier.

its great to see the way its going, i really like kopano+z-push.
Keep up the great work.

Greetz,
Louis

Manfred

Hi Louis,

@thctlo said in feedback: z-push package from z-push repo ( debian stretch ):

The old config file : config.php

Created : 01.10.2007

new config file z-push.conf.php

Created : 01.10.2007

i dont believe that the z-push.conf.php is created in 2007,.

Adding Version number in the config files whould be great, that makes it more easy to track changes. … Yes i did see “version.php” also in the web folder. ;-)

All config files in Z-Push are named config.php (the main config file, backends’ config files). As the config files are now all under /etc folder, they are renamed during installation, so the main config file is z-push.conf.php. Yes, it’s a different name, but it was indeed created on 01.10.2007.
How do you imagine version number in the config file? And how it’s easier to track changes?
In the release announcement we post a link to code changes since the previous release (and one can also check code changes of a file in bitbucket).

The installer does not check if the current folder is a folder.
in my case it was a symlink to z-push-2.3.1
i suggest, in case of a symlink, rename it and create a new folder.

There might be users who intentionally created a symlink and your suggestion wouldn’t be appreciated by them.

the logrotate can be bit better.
The ADM group should be able to read these logs.
This works fine : create 640 www-data adm

It’s something to discuss in larger group. I suppose adm or root group instead of www-data would be fine.

the z-push autodiscovery.
I noticed the small problem with some devices. ! i have not checked if this is still the case but
i used :
Alias /Autodiscover/Autodiscover.xml /usr/share/z-push/autodiscover/autodiscover.php
Alias /AutoDiscover/AutoDiscover.xml /usr/share/z-push/autodiscover/autodiscover.php
Alias /autodiscover/autodiscover.xml /usr/share/z-push/autodiscover/autodiscover.php

Sorry cant recall which devices, i use these for years now.
(Im oldschool zarafa users as of 4.x )

What is the question or suggestion here?
In the INSTALL of autodiscover there’s this line:

Add the following line to the apache site configuration file.
    AliasMatch (?i)/Autodiscover/Autodiscover.xml "/usr/share/z-push/autodiscover/autodiscover.php"

And in the configs for apache, lighttpd and nginx packages the alias for autodiscover is also case-insensitive.

Manfred

thctlo

Hai Manfred,
Thank your for the responce.
1)
How do you imagine version number in the config file?
how thats what we make of it, but an message “updated d.d. 2018-04-08” for example would be nice if the (defaults) content in the config is updated or when new settings are added/removed.
And how it’s easier to track changes? If you use the community version, you easaly miss small changes.
Im running a “scripted” unattended update and upgrade for the communitie version i use it for things like that.
2) I am such a user that had symlinks.
but if you switch from source z-push to repo, then you easly forget the symlink, like i did.
and Yes, it keeps working but my 2.4.0 z-push from repo ended up in z-push-2.3.1 folder due to the symlink.

this depends a bit per os, but in the debian case.
www-data is needed so the webuser can write, group adm is used for system monitoring tasks.
But needs to be set per OS, i only do debian, please discuss this, it helps.
Thanks, i totaly missed that. Very usefull.

I have one addon punt for the documentation of Kopano.
At least i could not find it.
SMTPUTF8 Support for kopano, If you use postfix 3.0+ and you use Kopano with LMTP, some mails might get lost. ( DSN 5.8.1 )
You need to disable smtputf8 in postfix.
sudo postconf “smtputf8_enable = no”
sudo postfix reload

Best regards,

Louis