Suggestion: C-S API endpoint to test push notifications

[Eirikr70]

When making a notification test, the notification is issued by the client side. It would make sense to have it issued by the homeserver side in order to be closer to the real notification process.
That might be made by adding to the client-server-api for push notif (https://spec.matrix.org/v1.9/client-server-api/#client-behaviour-11) the endpoint POST /_matrix/client/v3/pushers/test with the request body containing app_id.

[p1gp1g]

For context: many android users self-hosting synapse and their push gateway (which is usually built in ntfy or nextpush) struggle to find out they need to whitelist the IP of their push gateway (https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#ip_range_whitelist).

When they run the Element troubleshooting feature, they don't see anything wrong because the test request to the push gateway is sent from the phone and this doesn't show that synapse doesn't accept it.

If there were this endpoint, an additional test could be done : the HS send a test request with a fake event id, for instance $FAKE_ID_FOR_TEST. Like it is done from Android: https://github.com/element-hq/element-android/blob/develop/vector/src/main/java/im/vector/app/core/pushers/PushersManager.kt#L117

[turt2live]

Which "notification test" feature is this referencing?

[p1gp1g]

It refers to this test, on the android application: https://github.com/element-hq/element-android/blob/d418525748f6b4c9c42049fedf7d3ebf8963f20c/vector/src/main/java/im/vector/app/features/settings/troubleshoot/TestPushFromPushGateway.kt#L39

The application send a push message to the registered push gateway directly. But the HS may not be able to push to this gateway