On this page we would like to share our product development strategy.

Please note that the active development of TEGU (Freeware) and TEGU Professional products is over. This is because we consider the maildir storage-based architecture to be hopelessly outdated. That’s why we keep support for these products, but we stop development of new functionality in these editions.

Besides, this will allow us to focus on the development of the flagship TEGU Enterprise, which we consider promising. Here are some of the product development directions:

2024

Implemented changes for 2024

• Fundamentally new engine for the web-based administrator and user interface (design, structure, prerequisites for the development of dialog functions (see planning assistant))
• Interface structure redesigned for a multitenant scenario.
• There is a new block “routing”, which develops functions for processing incoming and outgoing messages both at MTA and MDA stages and during an SMTP session. Thus TEGU is not only a mail server but also a mail router (see documentation ).
• Mailbox maintenance functions have been developed (export, migration and renaming functions for both mailboxes and domains have been added).
• The second-level Recycle Bin has been implemented (auto-mounting and management on behalf of the user).
• Implemented a lot of new features (limitation of correspondence intensity, limitation of client access from subnets, premoderation, etc.).
• Integration with VCS and any resource systems is being finalized during the current month.
• The new proprietary 2TMTP protocol is fully realized and implemented in the code.
• API development for 2TMTP is almost completed.
• Started development of our own web and desktop clients (horizon 2025).
• Along with the ability to share IMAP folders, calendars and address books, the possibility of account sharding is now available.
• Round-trip mail notification based on the results of resource sharings.

Changes to be finalized in 2024

• Deletion of selected message across the entire domain.
• Auto-add header and footer to a message.
• Archive mailboxes (not counted in license, read-only).
• Publication of dynamic calendar of user’s free time by external link.
• Integration with VCS.
• Event scheduler.
• Role model of administration.

2025

Development of own web and thick client

The need for custom client applications is rather low at this stage as TEGU with its IMAP/SMTP implementation is compatible with all existing standard mail applications. However, with the advent of the functionality described in the 2TMTP protocol, the functions of standard mail programs will not be sufficient. Realizing this, we plan to develop our own clients for the 2TMTP protocol. See the list of available functions in the section “Development of new 2TMTP transport protocol”.

Implementing WebDAV file storage

Equip the WebDAV server with a file repository with the ability to create both system and user folders that can be shared over a wide range of time and permissions.

Porting TEGU to LoongArch64 hardware architecture

Chinese company Loongson Technology has developed a new LoongArch64 processor architecture from scratch, which allows these processors to be used on critical information infrastructure. In addition, the processors have already been launched into mass production, in connection with which they can be considered as a real alternative to Western analogs in our country and abroad.

Long-term support release

MBK Lab, developing the TEGU Enterprise product, aims at extensive (horizontal) development of functionality in 2024 in order to bring it closer to MS Exchange capabilities (possible within standard IMAP/SMTP/DAV protocols). All these changes are available within the major timeframe – 1.

Intensive (innovative) development of functionality is planned for 2025 in order to fully implement the Exchang+Outlook pair on the basis of its own 2TMTP protocol, as well as the realization of fundamentally new features. The solution of this task will require, among other things, the development of our own web, desktop and mobile clients. This solution (own server and client) will be available to users in version 2.

In order to allow users to stay within one version for a long time before the release of TEGU v2, we plan to release TEGU v1 LTS (long term support release) with a period of 3 years. Functionally, version 1 will not be developed, but legislative support, consulting and bug fixes will be provided.

Users for whom the new functionality is not critical and migration costs need to be minimized may remain on version 1 for the duration of support.

How to improve TEGU

We are not engaged in program improvements for specific projects, but if your proposal will be interesting for a wide audience, we will implement your proposed feature – write to us: support@mbk-lab.ru.