I think the first, simplified version could be just a switch - remove extra payload/do not remove without even specifying what the extra payload is. This should be fairly easy to implement and would solve most of the user's problems with this function.

patch attached. adds

{muc-component-name}/muc-allow-all-namespaces[B]

{muc-component-name}/muc-allowed-namespaces[{string array}]

configuration options. muc-allow-all-namespaces defaults to false, preserving current behavior, and may be set to true to simply pass all optional muc traffic. muc-allowed-namespaces can be set to an array of strings representing namespaces which are allowed. This has no effect if muc-allow-all-namespaces is true, because all namespaces will be passed anyway.

I wasn't able to test muc-allowed-namespaces because I couldn't find documentation on setting a string array in the configuration file, just S for string.

patch is against muc package root.

ah, it's lowercase s for string array. I will give it a shot.

ah, it's lowercase s for string array. I will give it a shot.

I had trouble debugging muc-allowed-namespaces for some reason nothing ended up in the logs. I did manage to see one bug visually, and here is an improved patch, but it still doesn't seem to work, so something else is still wrong.