Skip to content

Latest commit

 

History

History
76 lines (50 loc) · 3.72 KB

configuring-playbook-email2matrix.md

File metadata and controls

76 lines (50 loc) · 3.72 KB
Raw

Setting up Email2Matrix (optional)

Note: email bridging can also happen via the Postmoogle bot supported by the playbook. Postmoogle is much more powerful and easier to use, so we recommend that you use it, instead of Email2Matrix.

The playbook can install and configure email2matrix for you.

See the project's documentation to learn what it does and why it might be useful to you.

Preparation

DNS configuration

It's not strictly necessary, but you may increase the chances that incoming emails reach your server by adding an MX record for matrix.DOMAIN, as described in the Configuring DNS documentation page.

Port availability

Ensure that port 25 is available on your Matrix server and open in your firewall. If you have postfix or some other email server software installed, you may need to manually remove it first (unless you need it, of course).

If you really need to run an email server on the Matrix machine for other purposes, it may be possible to run Email2Matrix on another port (with a configuration like matrix_email2matrix_smtp_host_bind_port: "127.0.0.01:2525") and have your other email server relay messages there. For details about using Email2Matrix alongside Postfix, see here.

Creating a user

Before enabling Email2Matrix, you'd most likely wish to create a dedicated user (or more) that would be sending messages on the Matrix side. Refer to Registering users for ways to do that. A regular (non-admin) user works best.

Creating a shared room

After creating a sender user, you should create one or more Matrix rooms that you share with that user. It doesn't matter who creates and owns the rooms and who joins later (you or the sender user).

What matters is that both you and the sender user are part of the same room and that the sender user has enough privileges in the room to be able to send messages there. Inviting additional people to the room is okay too.

Take note of each room's room id (different clients show the room id in a different place). You'll need the room id when doing Configuration below.

Obtaining an access token for the sender user

In order for the sender user created above to be able to send messages to the room, we'll need to obtain an access token for it. Refer to the documentation on how to obtain an access token.

Configuration

After doing the preparation steps above, adjust your inventory/host_vars/matrix.DOMAIN/vars.yml configuration like this:

matrix_email2matrix_enabled: true

matrix_email2matrix_matrix_mappings:
  - MailboxName: "my-mailbox"
    MatrixRoomId: "!someRoom:DOMAIN"
    MatrixHomeserverUrl: "https://matrix.DOMAIN"
    MatrixUserId: "@email2matrix:DOMAIN"
    MatrixAccessToken: "ACCESS_TOKEN_GOES_HERE"
    IgnoreSubject: false
    IgnoreBody: false
    SkipMarkdown: false

  - MailboxName: "my-mailbox2"
    MatrixRoomId: "!anotherRoom:DOMAIN"
    MatrixHomeserverUrl: "https://matrix.DOMAIN"
    MatrixUserId: "@email2matrix:DOMAIN"
    MatrixAccessToken: "ACCESS_TOKEN_GOES_HERE"
    IgnoreSubject: true
    IgnoreBody: false
    SkipMarkdown: true

You can also set MatrixHomeserverUrl to http://matrix-synapse:8008, instead of the public https://matrix.DOMAIN. However, that's more likely to break in the future if you switch to another server implementation than Synapse.

Re-run the playbook (--tags=setup-email2matrix,start) and try sending an email to [email protected].