On April 7th, Kopano made a public statement on their website (https://kopano.com/core/statement-about-kopano/) accusing us (grammm) of copyright infringement.
In an article published on 7-April by Heise Online (https://www.heise.de/news/Streit-um-Open-Source-Groupware-Kopano-vs-grammm-6007100.html – German only) Kopano also accuses grammm of using code from an internal development project.
grammm firmly rejects these allegations. grammm has never violated the copyrights of any person or organization. Rather, it was the case that the entire code was distributed under an open source license (especially the GPL v.2). This means that grammm is free to use it.
Should Kopano not take back these baseless allegations, grammm will take legal action against Kopano B.V. because of the credit-damaging allegations.
For our partners and customers, we expressly point out the following details:
The claim in the Heise article that gromox was created as a component of grammm on the basis of the Steep system is correct and is hereby expressly confirmed by grammm. For this purpose, the public (under an open source license) repository of Steep system was forked. As development progresses, the code base of gromox only corresponds to a very small extent to the original code of Steep-System, as the following graphics underline.
- Support for PHP7 and PHP8
- Support for authentication with LDAP server
- Support von MS-OXOABKT (Global Address Book User Detail Forms)
- Support for defining any address book properties
- AutoConfig (Thunderbird) support
- Support of IPv6
- Complete documentation amounting to 58 A4 pages.
- Extensive code quality improvements:
- Steep system shows 17210 compiler warnings
- gromox currently has 310 warnings
- According to Synopsys® Coverity®
- contains steep-system 2408 defects – resource leaks, illegal memory access and memory corruption
- 2169 of these defects were corrected in gromox
- Support for built-in standards and reduction of the necessary configuration effort:
- Steep system requires configuration files with around 1100 configuration directives.
- gromox needs configuration files with about 33 configuration directives.
- Interoperability with the vCard standard
- Industrial level when decoding e-mails, e.g. defective RTF and ical files
- Compliance with the File Hierarchy Standard
- Integration with industry standard systemd
- Upgrade security through database update procedures (dbop)
- Continuous improvements based on C ++ techniques
- Replacement of self-made containers with containers from the C ++ standard
- Use of managed pointers and reduction of memory leaks
- Use of the RAII concept to prevent use-after-free and related resource problems
- Independent mail queue management
- Integration of rspamd as an anti-spam solution
- Improved diagnostics and log management
- Correction of defective functions, e.g. public folders
- Removed library dependencies, including libiconv, libspf2 and libxls
- Support of libc’s iconv library
- Hardening and code audit, e.g. the option to switch off RFC2971 commands