Description of problem: Unix backend doesn't support UTF-8 characters in realname somehow. Version-Release number of selected component (if applicable): zarafa-7.0.0-1 How reproducible: Everytime, see below. Steps to Reproduce: 1. Have a normal and working Zarafa installation 2. Edit /etc/zarafa/server.cfg as follows: a) user_plugin = unix b) user_plugin_config = /etc/zarafa/unix.cfg 3. Edit /etc/zarafa/unix.cfg as follows: a) fullname_charset = utf-8 4. /etc/init.d/zarafa-server restart 5. groupadd -g 2000 tux 6. useradd -u 2000 -g tux -c "123 äöü くらとみ 456" tux 7. zarafa-admin --sync 8. zarafa-admin -l Actual results: # zarafa-admin -l User list for Default(2): Username Fullname Homeserver ------------------------------------------- SYSTEM SYSTEM Zarafa tux 123 456 # Where are my German umlauts? Where are my Japanese glyphs? Expected results: Just working stuff as it should be. Additional info: This issue also happens with the official Zarafa RPM packages on RHEL 5.
A bit funny: mysql> select * from users; +----+----------+-------------+--------------------------------+---------+ | id | externid | objectclass | signature | company | +----+----------+-------------+--------------------------------+---------+ | 1 | NULL | 196610 | | 0 | | 2 | NULL | 65537 | | 0 | | 5 | 2000 | 65537 | 123 äöü くらとみ 456tux | 0 | | 6 | 2000 | 196610 | tux | 0 | +----+----------+-------------+--------------------------------+---------+ 4 rows in set (0.00 sec) Not so funny is, that Zarafa Webaccess doesn't display the non-ASCII chars, too. Important: All these nice characters work with the "db" backend. This is really specific to the "unix" backend.
In a Fedora build, this issue results in: # zarafa-admin -l Unable to list users, object not found # The server.log then shows (log level 6) something like: Unable to retrieve details from external user source: Invalid or incomplete multibyte or wide character Error synchronizing user list: 8000001D
This issue has been reported to upstream as Ticket#2011080210000013 for now.
Upstream returned id ZCP-7936, which is a blocker for the 7.0.1 release.
zarafa-7.0.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc16
zarafa-7.0.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc15
zarafa-7.0.1-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc14
zarafa-7.0.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.el6
php53-mapi-7.0.1-1.el5,zarafa-7.0.1-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/php53-mapi-7.0.1-1.el5,zarafa-7.0.1-1.el5
Package zarafa-7.0.1-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zarafa-7.0.1-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc16 then log in and leave karma (feedback).
zarafa-7.0.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.0.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
php53-mapi-7.0.1-1.el5, zarafa-7.0.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.0.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.0.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.