Table of Contents
New in version 0.8.0
The bridge can optionally encrypt messages between Matrix users and the bridge to hide messages from the homeserver. Using Postgres is strongly recommended when using end-to-bridge encryption.
To enable it, first make sure the bridge is installed with the e2be
optional dependency. After that, simply enable the option in the config (bridge
→ encryption
). If you only set allow: true
, the bridge won't enable encryption on its own, but will work in encrypted rooms. If you set default: true
, the bridge will automatically enable encryption in new portals.
Legacy instructions
Shared secret login
Prior to mautrix-telegram v0.9.0 / mautrix-python v0.8.0, you had to configure login_shared_secret. In new versions, you only need a homeserver with MSC2778 support, i.e. Synapse 1.21 or later.
Registration file workaround
In mautrix-telegram v0.8.0 release candidates, you had to manually apply a workaround for MSC2190. In newer versions (mautrix-telegram v0.8.0+, mautrix-python v0.5.0-rc3+) the workaround is applied automatically to all newly generated registration files. For old registration files, you can either regenerate the file or apply the workaround manually:
- Change
sender_localpart
in the registration to something else. Any random string will do. - Add a new entry in the
users
array for the bridge bot (the previous value ofsender_localpart
). If you used the defaulttelegrambot
, the result should look something like this:namespaces: users: - exclusive: true regex: '@telegram_.+:your.homeserver' - exclusive: true regex: '@telegrambot:your.homeserver'
- Using the
as_token
, make a call to register the bot user. It's fine if this says the user is already in use.$ curl -H "Authorization: Bearer <as_token>" -d '{"username": "telegrambot"}' -X POST https://your.homeserver/_matrix/client/r0/register?kind=user
Wiki deprecated
mautrix-telegram docs are now on docs.mau.fi