Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When you issue a 3pid invite that resolves to a mxid on a dead homeserver, your invite request is 500ed (rather than just forwarded to the email address as a regular 3pid) #1527

Open
lampholder opened this issue Nov 1, 2017 · 4 comments
Open

When you issue a 3pid invite that resolves to a mxid on a dead homeserver, your invite request is 500ed (rather than just forwarded to the email address as a regular 3pid) #1527

lampholder opened this issue Nov 1, 2017 · 4 comments
Labels
P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Z-Synapse

Comments

@lampholder
Copy link
Member

I feel like I already filed this, so it might be a dup :\

Anyway, this is hindering the effectiveness of Sync Bot
@turt2live
Copy link
Member

I suspect this is this?
image

@lampholder
Copy link
Member Author

No - that's actually Sync Bot killing off the threepid invites it thinks are associated with no-longer-elligable email addresses. Riot just renders that messily :(

@turt2live turt2live mentioned this issue Nov 1, 2017
Closed
@lampholder lampholder changed the title When you issue a 3pid invite that reconciles to a mxid on a dead homeserver, your invite request is 500ed (rather than just forwarded to the email address as a regular 3pid) When you issue a 3pid invite that resolves to a mxid on a dead homeserver, your invite request is 500ed (rather than just forwarded to the email address as a regular 3pid) Nov 2, 2017
@lampholder
Copy link
Member Author

Sort of a bug and a feature request :\

500 is not useful, and we're certainly not doing everything we could do to get the invite to the invitee, so I'm going to call this a bug for now.

It feels like the 'right thing' to do is to leave how synapse/sydent sends the invite entirely hidden from the inviter - we needn't reveal the details of the invitee's homeserver and status thereof.

@lampholder lampholder added P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround and removed P3 labels Nov 2, 2017
@lampholder lampholder mentioned this issue Apr 8, 2019
Open
@t3chguy t3chguy transferred this issue from element-hq/element-web Apr 28, 2023
@t3chguy
Copy link
Member

t3chguy commented Apr 28, 2023

This isn't an EW issue but likely a spec/sydent one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P2 S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Z-Synapse
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@turt2live @lampholder @t3chguy