Also, I think having a Dockernized SOGo v6 would be great. On Mon, Jul 27, 2026 at 11:07 AM Washington Odhiambo <[email protected]> wrote:
> Yes, for user sources. > > Many of us are allergic to LDAP and not having MariaDB/PostgreSQL > relegates us to the outer sanctums of SOGo :) > > On Mon, Jul 27, 2026 at 11:03 AM "Quentin HIVERT" <[email protected]> wrote: > >> For user sources? I'm working right on it + autocompletion. Will also >> fixed https://github.com/Alinto/SOGo6-server/issues/59 for mariadb. >> >> >> Regards, >> -- >> >> * Quentin Hivert * >> Lead Dev R&D >> [email protected] >> >> *Alinto* >> 19, quai Perrache >> FR-69002 Lyon >> https://www.alinto.com >> Linkedin FR <https://www.linkedin.com/company/alinto> >> >> >> >> On Monday, July 27, 2026 09:39 CEST, "Washington Odhiambo" ( >> [email protected]) <[email protected]> wrote: >> >> >> >> When will MariaDB/PostgreSQL bits be integrated? >> >> >> >> >> On Mon, Jul 27, 2026 at 10:28 AM Tobias Weiß <[email protected]> wrote: >> >> >>> Hello SOGo community, >>> >>> I've been working with the SOGo 6 codebase (both `sogo6-server` and >>> `SOGo6-UI`) and wanted to share a feature development effort I've >>> completed. The following repository is packaged with Docker Compose >>> (Stalwart + OpenLDAP) and implements some roadmap features. >>> >>> ## Repository (a bit hidden in dev branch) >>> >>> >>> https://github.com/tobias-weiss-ai-xr/sogo6-stalwart-openldap-dockerized/tree/dev >>> >>> ## What Was Built >>> >>> ### Core SOGo 6 Features >>> - Full mail stack — send, read, folders, search, bulk operations, Sieve >>> filters >>> - Calendar — CRUD, events, tasks, reminders, free/busy, external iCal >>> sync >>> - Contacts — address books, contacts, distribution lists, collected >>> addresses >>> - Admin panel — user CRUD (LDAP), domain settings, system settings, >>> session management >>> - Multi-language — English, German, French, Spanish (~2,100 strings each) >>> - Production-ready Dockerfiles — multi-stage, non-root, healthcheck >>> >>> ## Tools Used >>> >>> This repo was developed with assistance from **Mistral AI** (model >>> **Mistral Medium 3.5 128B**, accessed via >>> [hessian.ai](https://hessian.ai) and hosted at TU Darmstadt) for code >>> generation, debugging, and architectural guidance. Many thanks to both >>> Mistral AI and hessian.ai for their excellent tools and services. >>> >>> ## Next Steps >>> >>> I believe the code could serve as a reference implementation or starting >>> point for the broader SOGo 6 ecosystem. Key areas I'd love feedback on: >>> >>> 1. The SSO implementation (OIDC + SAML) — is this aligned with your >>> internal plans? >>> 2. The MFA/TOTP login flow — we integrated code verification directly >>> into the existing `POST /login` endpoint rather than a separate >>> challenge flow >>> 3. Any interest in upstreaming the sharing infrastructure (calendar + >>> contact ACL engines)? >>> >>> Happy to discuss any part of the implementation in more detail, maybe >>> during the next CoP that I annouce shortly. >>> >>> Best regards, Tobias Weiß >>> >>> >> >> >> >> -- >> >> Best regards, >> Odhiambo WASHINGTON, >> Nairobi,KE >> +254 7 3200 0004/+254 7 2274 3223 >> In an Internet failure case, the #1 suspect is a constant: DNS. >> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) >> [How to ask smart questions: >> http://www.catb.org/~esr/faqs/smart-questions.html] >> >> > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
