Self hosted riot web uses vector.im when adding email #1338

New Issue

2019-09-23T11:53:04Z

afonari commented

2019-09-23 11:53:04 +00:00

(Migrated from github.com)

Might be related to #1049.

Open riot.privacytools.io Set home server and identity server to chat.privacytools.io (this is currently defaults). You should see orange message about connection failure to the identity server. Login with your account. From the settings, try to add email address. Receive email from vector.im.

Might be related to #1049. Open riot.privacytools.io Set home server and identity server to chat.privacytools.io (this is currently defaults). You should see orange message about connection failure to the identity server. Login with your account. From the settings, try to add email address. Receive email from vector.im.

👀 1

blacklight447 commented

2019-09-24 10:26:03 +00:00

(Migrated from github.com)

@JonahAragon

jryans commented

2019-10-02 09:19:52 +00:00

(Migrated from github.com)

The recent privacy work in Riot 1.4 and Synapse 1.4 fixes this issue by ensuring that the HS manages validating your email when you are adding it to your HS account. The IS is no longer involved in adding an email to your HS account.

Please note that you must be using both Riot 1.4 and Synapse 1.4 (which is currently only an RC, full release expected in a few days) for this issue to be fixed. The HS privacy changes are already live on matrix.org, so you could use that to test the experience if you like.

So, what you are seeing is expected for now, but will be fixed once the privacytools.io HS is updated to Synapse 1.4 and configured to handle email validation itself.

The recent privacy work in Riot 1.4 and Synapse 1.4 fixes this issue by ensuring that the HS manages validating your email when you are adding it to your HS account. The IS is no longer involved in adding an email to your HS account. Please note that you must be using both Riot 1.4 and Synapse 1.4 (which is currently only an RC, full release expected in a few days) for this issue to be fixed. The HS privacy changes are already live on matrix.org, so you could use that to test the experience if you like. So, what you are seeing is expected for now, but will be fixed once the privacytools.io HS is updated to Synapse 1.4 and configured to handle email validation itself.

afonari commented

2019-10-03 18:06:05 +00:00

(Migrated from github.com)

I've tried with Riot-web and Synapse 1.4 on matrix.org. I still get the email when I try to add one, even without any identity Server set. So I guess HS is managing the emails now.

afonari commented

2019-10-03 18:11:30 +00:00

(Migrated from github.com)

1.4.0 is out: https://github.com/matrix-org/synapse/releases
Hopefully PIO can update soon.

1.4.0 is out: https://github.com/matrix-org/synapse/releases Hopefully PIO can update soon.

jonah commented

2019-10-05 22:47:06 +00:00

The actual reason this was happening was because of an apparent bug in an earlier version of Synapse that did not allow me to set custom email settings. After updating to 1.4.0 I was also able to configure my own mailserver.

Just tested this myself, email verification messages are sent from matrix-notifications@privacytools.io. Closing issue :)

The actual reason this was happening was because of an apparent bug in an earlier version of Synapse that did not allow me to set custom email settings. After updating to 1.4.0 I was also able to configure my own mailserver. Just tested this myself, email verification messages are sent from `matrix-notifications@privacytools.io`. Closing issue :)

afonari commented

2019-10-05 23:42:38 +00:00

(Migrated from github.com)

Noice! Thanks!

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1338