如何在 ejabberd 中撤回消息?

Posted

技术标签:

【中文标题】如何在 ejabberd 中撤回消息?【英文标题】:How to retract a message in ejabberd? 【发布时间】:2020-01-22 12:31:17 【问题描述】:

我正在创建一个 MUC 客户端,我想在客户端中实现某种消息删除。我读到从 ejabberd 中删除单个消息是不可能的。但是我怎样才能使用XEP-0424 来达到类似的目的呢?我已经阅读、编写并测试了 XEP 中描述的用例,但没有成功。

客户端发送这样的消息:

<message xmlns="jabber:client" to="myroom@conference.localhost" type="groupchat">
   <body>9</body>
   <urls />
   <origin-id xmlns="urn:xmpp:sid:0" id="358f5b60-3d10-11ea-be33-5f58c62bedc3" />
</message>

服务器广播这个:

<message xmlns="jabber:client" to="user1@localhost/1132254315040517635831042" from="myroom@conference.localhost" id="1579690081679918">
   <archived xmlns="urn:xmpp:mam:tmp" by="user1@localhost" id="1579690081690608" />
   <stanza-id xmlns="urn:xmpp:sid:0" by="user1@localhost" id="1579690081690608" />
   <event xmlns="http://jabber.org/protocol/pubsub#event">
      <items node="urn:xmpp:mucsub:nodes:messages">
         <item id="1579690081679918">
            <message xmlns="jabber:client" xml:lang="en" to="user1@localhost" from="myroom@conference.localhost/user1" type="groupchat">
               <archived xmlns="urn:xmpp:mam:tmp" by="myroom@conference.localhost" id="1579690081679918" />
               <stanza-id xmlns="urn:xmpp:sid:0" by="myroom@conference.localhost" id="1579690081679918" />
               <urls />
               <origin-id xmlns="urn:xmpp:sid:0" id="358f5b60-3d10-11ea-be33-5f58c62bedc3" />
               <body>9</body>
            </message>
         </item>
      </items>
   </event>
</message>

已发送撤回消息:

<message xmlns="jabber:client" to="myroom@conference.localhost" type="groupchat">
   <apply-to xmlns="urn:xmpp:fasten:0" id="358f5b60-3d10-11ea-be33-5f58c62bedc3">
      <retract xmlns="urn:xmpp:message-retract:0" />
   </apply-to>
</message>

作为撤回消息发送的结果,服务器广播:

<message xmlns="jabber:client" to="user1@localhost/1132254315040517635831042" from="myroom@conference.localhost" id="2725765463385791444">
   <event xmlns="http://jabber.org/protocol/pubsub#event">
      <items node="urn:xmpp:mucsub:nodes:messages">
         <item id="2725765463385791444">
            <message xmlns="jabber:client" xml:lang="en" to="user1@localhost" from="myroom@conference.localhost/user1" type="groupchat">
               <apply-to xmlns="urn:xmpp:fasten:0" id="358f5b60-3d10-11ea-be33-5f58c62bedc3">
                  <retract xmlns="urn:xmpp:message-retract:0" />
               </apply-to>
            </message>
         </item>
      </items>
   </event>
</message>

当我查询房间的历史时,我会收到:

<message xmlns="jabber:client" to="user1@localhost/395000986606606742032146" from="myroom@conference.localhost">
   <result xmlns="urn:xmpp:mam:2" id="1579690081679918">
      <forwarded xmlns="urn:xmpp:forward:0">
         <message xmlns="jabber:client" xml:lang="en" from="myroom@conference.localhost/user1" type="groupchat">
            <x xmlns="http://jabber.org/protocol/muc#user">
               <item jid="user1@localhost/1132254315040517635831042" />
            </x>
            <archived xmlns="urn:xmpp:mam:tmp" by="myroom@conference.localhost" id="1579690081679918" />
            <stanza-id xmlns="urn:xmpp:sid:0" by="myroom@conference.localhost" id="1579690081679918" />
            <urls />
            <origin-id xmlns="urn:xmpp:sid:0" id="358f5b60-3d10-11ea-be33-5f58c62bedc3" />
            <body>9</body>
         </message>
         <delay xmlns="urn:xmpp:delay" from="conference.localhost" stamp="2020-01-22T10:48:01.679918Z" />
      </forwarded>
   </result>
</message>

我错过了什么?我不应该收到类似tombstone 的消息吗?

到目前为止,我的设置是:

ejabberd 19.09.1 使用MucSub 方法 mod_man 已配置 坚持使用 mysql 5.7 strophe.js 1.3.4

这是我的 ejabberd.yml:

hosts:
  - "localhost"

loglevel: 4
log_rotate_size: 10485760
log_rotate_date: ""
log_rotate_count: 1
log_rate_limit: 100

certfiles:
  - "/etc/letsencrypt/live/localhost/fullchain.pem"
  - "/etc/letsencrypt/live/localhost/privkey.pem"

ca_file: "/etc/letsencrypt/live/localhost/cacert.pem"

sql_type: mysql
sql_server: "localhost"
sql_database: "ejabberd"
sql_username: "ejabberd"
sql_password: "****"
sql_port: 3306

auth_method: sql
default_db: sql

listen:
  -
    port: 5222
    ip: "::"
    module: ejabberd_c2s
    max_stanza_size: 262144
    shaper: c2s_shaper
    access: c2s
    starttls_required: false
  -
    port: 5269
    ip: "::"
    module: ejabberd_s2s_in
    max_stanza_size: 524288
  -
    port: 5443
    ip: "::"
    module: ejabberd_http
    tls: true
    request_handlers:
      "/admin": ejabberd_web_admin
      "/api": mod_http_api
      "/bosh": mod_bosh
      "/captcha": ejabberd_captcha
      "/upload": mod_http_upload
###      "/ws": ejabberd_http_ws
      "/oauth": ejabberd_oauth
  -
    port: 5280
    ip: "::"
    module: ejabberd_http
    request_handlers:
      "/admin": ejabberd_web_admin
      "/websocket": ejabberd_http_ws
  -
    port: 1883
    ip: "::"
    module: mod_mqtt
    backlog: 1000

s2s_use_starttls: optional

acl:
  local:
    user_regexp: ""
  loopback:
    ip:
      - 127.0.0.0/8
      - ::1/128
      - ::FFFF:127.0.0.1/128
  admin:
    user:
      - "admin@localhost"

access_rules:
  local:
    allow: local
  c2s:
    deny: blocked
    allow: all
  announce:
    allow: admin
  configure:
    allow: admin
  muc_create:
    allow: admin
  pubsub_createnode:
    allow: local
  trusted_network:
    allow: loopback

api_permissions:
  "console commands":
    from:
      - ejabberd_ctl
    who: all
    what: "*"
  "admin access":
    who:
      access:
        allow:
          acl: loopback
          acl: admin
      oauth:
        scope: "ejabberd:admin"
        access:
          allow:
            acl: loopback
            acl: admin
    what:
      - "*"
      - "!stop"
      - "!start"
  "public commands":
    who:
      ip: 127.0.0.1/8
    what:
      - status
      - connected_users_number

shaper:
  normal: 1000
  fast: 50000

shaper_rules:
  max_user_sessions: 10
  max_user_offline_messages:
    5000: admin
    100: all
  c2s_shaper:
    none: admin
    normal: all
  s2s_shaper: fast

max_fsm_queue: 10000

acme:
   contact: "mailto:admin@localhost"
   ca_url: "https://acme-v01.api.letsencrypt.org"

modules:
  mod_adhoc: 
  mod_admin_extra: 
  mod_announce:
    access: announce
  mod_avatar: 
  mod_blocking: 
  mod_bosh: 
  mod_caps: 
  mod_carboncopy: 
  mod_client_state: 
  mod_configure: 
  mod_disco: 
  mod_fail2ban: 
  mod_http_api: 
  mod_http_upload:
    put_url: https://@HOST@:5443/upload
  mod_last: 
  mod_mam:
    ## Mnesia is limited to 2GB, better to use an SQL backend
    ## For small servers SQLite is a good fit and is very easy
    ## to configure. Uncomment this when you have SQL configured:
    db_type: sql
    assume_mam_usage: true
    default: always
  mod_mqtt: 
  mod_muc:
    access:
      - allow
    access_admin:
      - allow: admin
    access_create: muc_create
    access_persistent: muc_create
    access_mam:
      - allow
    default_room_options:
      allow_query_users: false
      allow_subscription: true  # enable MucSub
      mam: true
      persistent: true
      public: false
      public_list: false
  mod_muc_admin: 
  mod_offline:
    access_max_user_messages: max_user_offline_messages
  mod_ping: 
  mod_privacy: 
  mod_private: 
  mod_proxy65:
    access: local
    max_connections: 5
  mod_pubsub:
    access_createnode: pubsub_createnode
    plugins:
      - flat
      - pep
    force_node_config:
      ## Avoid buggy clients to make their bookmarks public
      storage:bookmarks:
        access_model: whitelist
  mod_push: 
  mod_push_keepalive: 
  mod_register:
    ## Only accept registration requests from the "trusted"
    ## network (see access_rules section above).
    ## Think twice before enabling registration from any
    ## address. See the Jabber SPAM Manifesto for details:
    ## https://github.com/ge0rg/jabber-spam-fighting-manifesto
    ip_access: trusted_network
  mod_roster:
    versioning: true
  mod_s2s_dialback: 
  mod_shared_roster: 
  mod_stream_mgmt:
    resend_on_timeout: if_offline
  mod_vcard: 
  mod_vcard_xupdate: 
  mod_version:
    show_os: false


### Local Variables:
### mode: yaml
### End:
### vim: set filetype=yaml tabstop=8

我为那篇长消息道歉,但它提供了上下文。

【问题讨论】:

你的服务器有support XEP-0424吗? @Flow,我正在使用 ejabberd 19.09.1 社区。在您询问后,我访问了他们的页面 (process-one.net/en/ejabberd/protocols),我认为它的核心不支持它。 【参考方案1】:

目前 ejabberd 不支持 XEP-0424,所以这不起作用。

【讨论】:

以上是关于如何在 ejabberd 中撤回消息?的主要内容,如果未能解决你的问题,请参考以下文章

如何在 Ejabberd 中归档消息并存储在 MongoDB 中

如何在 ejabberd 中的 xmpp 消息正文中附加自定义数据

微信电脑版如何防止撤回

如何在 ejabberd 上为 muc(多用户聊天)设置不同的消息间隔?

从 ejabberd 检索聊天记录时如何识别已发送和未发送的消息?

如何使用 XMPPFramework 从 ejabberd 中删除两个用户之间的特定消息?