element-hq / element-hq/synapse

Adding a room ACL that denies a server does not prevent typing notifications

Open
#11,456 0 comments 0 reactions 0 assignees View on GitHub
S-Minor T-Defect
Dominant language
Python
Stars
4.6k
Forks
600
Avg merge
5d 22h
Merged PRs (30d)
51

Description

This issue has been migrated from [#11456](https://github.com/matrix-org/synapse/issues/11456).

---

### Description

Hi, I have a user who hosts his own dendrite server who I have banned from a room. He however has been sending typing notifications to my room for the last 13 hours to annoy my users. I have tried sending an acl that denies his server from communicating, but that has not prevented his typing notifications.

Unfortunately, I do not know how he has been sending these typing notifications.

I would expect sending a room acl to deny a server would prevent users from sending typing notifications.

Here is the acl
![image](https://user-images.githubusercontent.com/28763729/143958524-bd3e8a48-1218-431c-983c-6ad06ca63961.png)

### Version information

If not matrix.org:

- **Version**: 1.47.1
- **python_version**: 3.9.2

- **Install method**: Official Debian package

- **Platform**: apt

Running on Debian 11 (Bullseye)

Contributor guide

Open the contributing guide

Research direction

The report names no source file or test entry point; start by reproducing the room ACL and typing-notification behavior on Synapse 1.47.1, using the homeserver.log guidance if relevant. Trace how server ACLs are applied to typing notifications, then add coverage showing that a denied server's notifications are blocked and run the affected test suite.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.