#1410 mod_block_strangers filters out MAM messages from MUCs
Reporter
Ralph Meijer
Owner
Nobody
Created
Updated
Stars
★★ (2)
Tags
Type-Defect
Status-New
Priority-Medium
Ralph Meijer
on
What steps will reproduce the problem?
1. Enable mod_block_strangers
2. Join a MUC
3. Perform a MAM request resulting in a non-empty result.
What is the expected output?
Archived messages matching the result should not be filtered.
What do you see instead?
Archived messages are filtered.
What version of the product are you using? On what operating system?
38365c1f1fe4
Please provide any additional information below.
The cause is that the archived messages come from the bare JID of the room, whereas directed presence is stored only for the (full) occupant JID. On its own, mod_block_strangers cannot know what the occupant JID is, so the messages are indeed from a 'stranger'. Zash suggested mod_track_muc_joins may be used to remedy this issue.
What steps will reproduce the problem? 1. Enable mod_block_strangers 2. Join a MUC 3. Perform a MAM request resulting in a non-empty result. What is the expected output? Archived messages matching the result should not be filtered. What do you see instead? Archived messages are filtered. What version of the product are you using? On what operating system? 38365c1f1fe4 Please provide any additional information below. The cause is that the archived messages come from the bare JID of the room, whereas directed presence is stored only for the (full) occupant JID. On its own, mod_block_strangers cannot know what the occupant JID is, so the messages are indeed from a 'stranger'. Zash suggested mod_track_muc_joins may be used to remedy this issue.