#chatmail does secure email federation that works. Using lean "relay" servers that enforce metadata-minimized end-to-end encryption.

There is a new little tool that checks whether two relays are interacting well for messaging, and how fast. You need a terminal window and be able to execute:

pip install cmping

you can then run for example:

cmping mailchat.pl nine.testrun.org

to perform a "ping" test for e2ee-messaging. Also see chatmail.at/relays

github.com/chatmail/cmping/

in reply to Radasbona

If the problem boils down to the users allowing UnifiedPush client to run and denying the same permission to Delta Chat, then it is not interesting to spend development effort on it as the problem can be solved by allowing DC to run in the background. We do support FCM (besides Ubuntu Touch and Apple) notifications for the phones that do not allow to run apps in background, but there you cannot run UnifiedPush as well.
in reply to Radasbona

I think we could argue until the dogs come home about whether or not it's enough of an "established standard" when the number of users who refuse to use Google Play Services on their phones is dangerously close to zero and the number of apps available that implemented Unified Push is a rounding error when compared to the entire Android apps ecosystem

Delta has to target the common user first before it can expend the effort satisfying a very niche userbase

in reply to LΞX/NØVΛ 🇪🇺

we need more docker testers

github.com/chatmail/relay/pull…

in reply to Jarrod Urban

@jarrodu @lexinova There are tons of moving parts in the diagrams: chatmail.at/doc/relay/overview…

When I see a bunch of moving parts like that, I get cold feet, that it'll be as easy as people make out. Is there a Youtube/Peertube video on this? If it's as easy as you claim, then I'd like to see a from-scratch install on #Debian 12, using python's uv for the package manager of chatrelay (in a uv venv). Including sending initial testing messages proving it's working in production.

in reply to Jarrod Urban

@jarrodu main blocker for upgrading to Debian 13 is this issue: github.com/chatmail/relay/issu… if you subscribe there, you'll hear news when they come in. For now, we regard debian 12 as a fine target environment. If dovecot folks would finally merge our speed-patch github.com/dovecot/core/pull/2… then that would be a incentive for us to move to a new debian.
in reply to LΞX/NØVΛ 🇪🇺

@lexinova @jarrodu @d1 Use venv, e.g. `python3 -m venv ~/.venv/chatmail` + `. ~/.venv/chatmail/bin/activate`

docs.python.org/3/library/venv…

in reply to Teoh Han Hui

@teohhanhui @lexinova @jarrodu Thanks for that. I've used venvs before for a couple other python projects (copyparty being the most server-like). It becomes non-trivial when you want to set up a systemd service to start a server at boot time, and the venv must be invoked from systemd. Can systemd start, stop, disable, and enable the service reliably from the command line (systemctl)? Everyone apparently assumes these things are simple; hand-waving away such details as trivialities, but no they aren't trivial.
in reply to Dusty

@d1 Chatmail relay uses systemd to run services in a venv. All the work setting this up is done by "cmdeploy" script, so you don't need to manage this yourself: chatmail.at/doc/relay/getting_…

As for "cmping", if you just want to run the command, you can install pipx.pypa.io/ and run `pipx run cmping example.org example.net`. pipx will manage creation of venv and setting up cmping package from PyPI.

in reply to Delta Chat

Ok.. I love DC, here I have no problems with it, but why (without going into technical details, implementation).... On my phone, pure Lineage OS without Google services, without anything! Notifications are received on Telegram and WhatsApp, but there are always difficulties in Deltachat. Why! Just explain to me (maybe not even to me, in simple terms... for those who are very far from programming) why is there no simple implementation?! What's in the way?!