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.

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

MAM implementation should include urn:xmpp:mam:2 #5

akrherz opened this issue Jan 4, 2019 · 0 comments


None yet
1 participant
Copy link

commented Jan 4, 2019

...Migrated from Ignite Jira OF-1576... defines:

If a server or other entity hosts archives and supports MAM queries, it MUST advertise the 'urn:xmpp:mam:2' feature in response to Service Discovery (XEP-0030) [15 requests made to archiving JIDs (i.e. JIDs hosting an archive, such as users' bare JIDs)

The monitoring plugin should add the MAM feature to the response of such requests made against user JIDs.

@deleolajide wrote

Add support for urn:xmpp:mam:2.
Only urn:xmpp:mam:0 and urn:xmpp:mam:1 namespaces are actually currently supported. The requirement for :2 support is that openfire guarantees that all live messages are tagged with a stanza ID. This is already been implemented in Openfire for Message Carbons.
We only need to bump the namespace.

@guusdk wrote

And add support for

@guusdk guusdk changed the title MAM implementation should properly advertise support MAM implementation should include urn:xmpp:mam:2 Jan 17, 2019

guusdk added a commit to guusdk/openfire-monitoring-plugin that referenced this issue Jan 17, 2019

Add support for MAM:2 (MUC only)
Support for MAM:2 is possible from Openfire 4.3.1 onwards, assuming that
igniterealtime/Openfire#1265 makes it in that version.

This partially fixes igniterealtime#5
(partially, as this commit adds support only for MUC).

@guusdk guusdk closed this in f1adbc6 Jan 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.