Hi all! Since Kopano appears to have officially gone dark now I'm looking to migrate away from Kopano to something else. I'm evaluating the Grommunio appliance and I'm trying to look at the differences with Kopano. Quite a lot! I like what has happened with the configuration for the most part so far.

Things that I can't seem to work out:

  • GAB user photo. Previously this came from my LDAP server through the thumbnailPhoto attribute by adding an ldap_user_attributes=thumbnailPhoto 0x8C9E0102 This does not work however, it appears that at least webmail can't use that attribute?
  • Previously I used the kopanoSendAsPermission attribute in LDAP to allow, well, sending as. It appears that Grommunio does not have this feature and it all has to go through the database?
  • Where are attachments stored? In Kopano there was an option to either store in the database or on the filesystem. Does grommunio only allow storing in the database?
  • In kopano-webapp I used ENABLE_REMOTE_USER_LOGIN together with oauth2_proxy to have true single signon, it appears that that option is still present in the webapp code but removed from the config.php.default, does this still work as it used to?
  • My email server only uses LDAP accounts, and my secondary MXses all have a copy of the LDAP tree, this way my postfix servers can just do user validation and alias expansion locally. Is it still possible to use this with grommunio? I realize that if there are users that ONLY exist in the database this won't work, but that is not true for any of my users.
  • Is grommunio-webapp still compatible with kopano json themes?

Thanks for reading this and hopefully for your response :) So far grommunio looks pretty good, I'm excited to poke at it more in the coming days.

  • crpb replied to this.

    Hey,

    i can't answer everything but i will try with the parts i know.
    Well, the Basic Info is here as you might already know:

    https://docs.grommunio.com

    TMM Where are attachments stored? In Kopano there was an option to either store in the database or on the filesystem. Does grommunio only allow storing in the database?

    https://docs.grommunio.com/man/gromox.7.html#databases

    All E-Mails are Stored on the Filesystem and there are two sqlite.databases in the corresponding "mailbox"-folder with additional Information.
    The MySQL-Database mainly consists of administrative Settings and that the User is actually "registered" there so to speak. (my local Backup with ~25 Users uncompressed it "87K Dec 5 05:35 grommunio.sql" ;P)
    https://docs.grommunio.com/admin/operations.html?highlight=backup#file-based-backup

    TMM My email server only uses LDAP accounts, and my secondary MXses all have a copy of the LDAP tree, this way my postfix servers can just do user validation and alias expansion locally. Is it still possible to use this with grommunio? I realize that if there are users that ONLY exist in the database this won't work, but that is not true for any of my users.

    The builtin Postfix is already configured and you don't really have to think about it, not like with Zarafa/Kopano.
    I only set a few settings and my Relayhost/Password. That's it.

    For Migration there is also a Script from @WalterH which works pretty good.
    https://github.com/grommunio/gromox/blob/master/tools/kopano2grommunio.sh
    https://github.com/grommunio/gromox/blob/master/tools/create_k2g_migration_lists.sh

    So far for now.. i also shared a few of my Helpers which you might find useful.
    https://community.grommunio.com/d/444-grommunio-scripting-snippets-notepad

        TMM In kopano-webapp I used ENABLE_REMOTE_USER_LOGIN together with oauth2_proxy to have true single signon, it appears that that option is still present in the webapp code but removed from the config.php.default, does this still work as it used to?

        And i think that / or similiar should soon be possible with the comming release..
        https://docs.grommunio.com/admin/roadmap.html

          Having the same issue with the thumbnails, in our case we are using the jpegPhoto attribute. Any clues?

          In the LDAP synchronization tool, you would enter a custom mapping from jpegPhoto to thumbnailphoto, at which point the data should synchronize over to mysql. The address book modules do not extract photos from the (mysql) db currently (because hardcoded to look in the filesystem for $mbox/config/portrait.jpg), so some coding work is still needed.

          Thanks for all the answers so far! I'll probably wait until the next grommunio release to reevaluate. It's looking quite good though!

          © 2020-2024 grommunio GmbH. All rights reserved. | https://grommunio.com | Data Protection | Legal notice