Nested labels is a key feature available in Fastmail. Combined with label assignment rules and the archive button, it allow a smart and efficient user workflow.
Stalwart seems to have nestted folder, but not nested labels. Is this correct ? Can we expect that in the roadmap anytime soon ?
Hi there,
I'm hoping someone can help me. I have a .pw domain hosted on cloudflare and stalwart hosted on a contabo VPS. The IP reputation is good and not blacklisted.
I have DKIM, DMARC and SPF set up and functional, I have a BIMI logo hosted in a GitHub repo, for what it's worth.
I'm having trouble with Google's spam filters. Whatever I do, it seems to get triggered. Whether a new email is sent from user@domain.pw or an email is sent from email@gmail.com, any email sent from my domain to Gmail ends up in spam. This includes replies to Gmail.
Any ideas?
Thanks in advance.
UPDATE: It's mysteriously started working. Here's hoping it stays that way.
Hi everyone,
I’m building Jabali Panel, a free and open-source web hosting control panel for Debian servers.
The project is still young, but the community is slowly growing, and I’m now looking for testers and early users who want to try it, give feedback, report bugs, and help shape the direction of the panel.
Jabali now also supports Docker, so it can be used not only as a traditional web hosting panel, but also as a standalone Docker proxy server, mail server, DDNS server, DNS server, and more — depending on what you want to run.
It’s focused on WordPress hosting, small hosting providers, freelancers, and sysadmins who want a modern self-hosted alternative without license fees or vendor lock-in.
For testers who seriously try the panel and give feedback, I’ll provide full support during the testing period to help with installation, setup, issues, and questions.
GitHub: https://github.com/shukiv/jabali-panel
Demo: https://demo.jabali-panel.com
Thanks — any feedback, testing, or GitHub issues would help a lot.
I've been building Sterna Mail, an Android email app built around JMAP, and since this community actually runs JMAP servers I figured it might be useful here.
The short version: it's a fast, private email client built for JMAP first, with full IMAP/SMTP support too. No ads, no tracking, no analytics, no Google services of any kind. It's GPLv3 and open source.
Why JMAP first
Most mobile clients still treat IMAP as the only option, so JMAP servers like Stalwart rarely get a client that makes the most of them. Sterna uses JMAP for faster sync, less battery and data use, and push for new mail with no Google/FCM (JMAP EventSource, or IMAP IDLE on the classic side).
What works today (it's at 1.0 and daily-drivable)
Privacy is the point: nothing phones home, the only server it talks to is the one you choose.
It's not on an app store yet (working on F-Droid), but there's a signed APK on the release page. Repo, screenshots and download:
https://codeberg.org/emon/sterna-mail
Planned next: OpenPGP encrypted email and home-screen widgets.
It's a one-person project, so feedback from people actually running JMAP servers would be hugely helpful. If you try it against your Stalwart setup and something feels off, please open an issue. Happy to answer anything here too.
During the last few days I spent some time and tokens on creating a mail user agent for Stalwart (IMAP and Jmap)
Android builds are available here:
Code (open source) https://github.com/guettli/sharedinbox
Before getting it into Google PlayStore I need 12 Testers.
If you are interested, please send me a DM.
Later I plan to support iOS, too.
Currently, only Mail is supported. Calendar and contacts are planned.
Feel free to create feature requests and bug reports on GitHub.
Thank you for Stalwart!
(Should work with other IMAP/JMAP servers, too)
Hi everyone,
I'm trying to upgrade my production Stalwart installation from 0.15.2 to 0.16.7 (the latest version available when I started the migration).
My current setup is:
I followed the documented migration path and generated the migration plan (migration-plan.ndjson) using migrate_v015_to_plan.py. Importing the plan worked successfully for:
After that, I attempted to export user data using Vandelay. For some users, the export fails with errors indicating that certain blobs do not exist. For other users, the export completes with output similar to:
export: Mailbox ...
export: AddressBook ...
export: Calendar ...
export: Identity ...
export: ParticipantIdentity ...
export: Email ...
Mailbox: created=1 fetched=0 updated=0 deleted=0 skipped=5 failed=0
AddressBook: created=0 fetched=0 updated=0 deleted=0 skipped=1 failed=0
Calendar: created=0 fetched=0 updated=0 deleted=0 skipped=1 failed=0
Identity: created=0 fetched=0 updated=0 deleted=0 skipped=1 failed=0
ParticipantIdentity: created=0 fetched=0 updated=0 deleted=0 skipped=1 failed=0
Email: created=2 fetched=0 updated=0 deleted=0 skipped=0 failed=0
However, the resulting export files are much smaller than the actual mailbox sizes shown in Stalwart.
I also tested the migrated data using Bulwark. The mailbox counters appear correctly in the sidebar (for example, the Inbox shows the expected number of messages), but when I open the Inbox, it says that the mailbox is empty.
Has anyone experienced similar issues during a 0.15.x → 0.16.x migration?
My goal is to upgrade my production environment to the latest version, but at the moment I'm concerned about potential data loss. I would also prefer not to use the migration proxy because it adds another layer of complexity to the migration process.
Any advice or recommendations would be greatly appreciated.
Hej,
one of my last errors could not be delivered:
Your message could not be delivered to
the following recipients:
<vertrag@alfahosting.de> (connection to
'mx03.secure-mailgate.com' failed: lookup error:
DNS resolution error: DNS error: DNSSEC Negative
Record Response for mx03.secure-mailgate.com.
IN AAAA, Bogus)
I asked Manus AI to explain this to me but I still do not get it.
If an AAAA record is not found, why is the email not delivered via the A record of the target MX?
Thanks