processone / processone/ejabberd

Outcoming chat messages are not always stored in archive

Open
#3,377 15 comments 1 reaction 1 assignee View on GitHub

@jsautret is already working on this.

Since Jul 11, 2023.

Dominant language
Erlang
Stars
6.7k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Environment

  • ejabberd version: 20.07

Configuration

  mod_mam:         
    db_type: sql
    assume_mam_usage: true
    default: always                                       
    user_mucsub_from_muc_archive: true                  
    request_activates_archiving: false   

Only incoming chat messages are stored in archive table when we send messages with ejabberd send_message command and/or send_message API endpoint.

The outcoming chat messages are only stored when the from user has an active session.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.