I agree. Please estimate work effort and then we can decide for which version this will be implemented.

I set estimated time including creation of proper test for this feature.

If we want additional property to disable this enabled by default feature then please add 1 hour to time estimated by me.

Then, go ahead with implementation. I added an additional hour.

I added storage of message delivery receipts to offline store by default.

I also changed implementation of mechanism to allow storage of additional type of packets to offline store developed in #2426. Now settings passed by this feature override default storage features.

Now it is possible to set:

sess-man/plugins-conf/amp/msg-store-offline-paths[s]=/message/received[urn:xmpp:receipts],/message/store-offline,-/message/do-not-store

which will result in storage of:

• message with received subelement with xmlns set to urn:xmpp:receipts

• message with store-offline subelement without checking for xmlns

and will stop storage of:

• message with do-not-store element

Messages will be checked first by matchers and if any of them will match then result returned by this mather will override default settings and will override any other matcher which is listed later in matchers list.

This way it is possible to override any default setting and create custom order of matchers used to decide if message will be stored or not.

Andrzej,

Do we have this documented somewhere? I mean this extension and all other extensions we have done to the UA?

I think our UA implementation deserves good documentation if we want people to start using it.

This is additional feature created for Tigase XMPP Server and is not related to UA in any way.

As for UA and it's feature, it was developed as extension for clients only and project is not public so we did not need any documentation for users, as mostly it use was suggested by use with relation to particular feature.

Also features were added based on particular project and I think there is no list of all features available in UA.

I think it may be good to create on project wiki list of features with proper configuration options - if so then I think it would be good to create new task for this.

But I still have tasks #3543, #3548 and #3542 which I think should be done in new version of UA (Message Archiving 2.0.0 and UA 2.0.0 for Tigase XMPP Server 7.2.0) as this is rather big change in storage and repository implementation. I would rather prepare documentation for 2.0.0 when I do this listed tasks as they may change configuration options for UA and MA.

Understand, thank you for explanation.

Added documentation to AMP section in Admin Guide.