spacedriveapp / spacedriveapp/spacebot

Slack DMs still filtered after setting dm_allowed_users

Open
#261 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2.4k
Forks
367
PR merge metrics
No merged PRs in 30d

Description

Howdy! Been playing around with Spacebot, super cool so far! I stumbled into a issue with Slack DMs, that could very well be user error, but thought I should report it.

Environment

Spacebot v0.2.1
Linux (Ubuntu Server, systemd)
Socket Mode (no public endpoint)

Problem

Slack direct messages are not being received by Spacebot despite having dm_allowed_users configured in config.toml. This issue seems to be specific to DMs, as channel messages are working correctly. Logs don't provide any evidence the message is ever received.

Spacebot Config

[messaging.slack]
enabled = true
dm_allowed_users = ["Uxxxx"] # Profile -> kebab -> Copy User ID

[[messaging.slack.instances]]
name = "Tempest"
enabled = true
bot_token = "xoxb-..."

Slack Permissions

The Messages Tab is enabled with "Allow users to send Slash commands and messages from the messages tab" checked.

    "oauth_config": {
        "scopes": {
            "bot": [
                "app_mentions:read",
                "chat:write",
                "chat:write.public",
                "chat:write.customize",
                "reactions:read",
                "reactions:write",
                "channels:read",
                "channels:history",
                "groups:read",
                "groups:history",
                "im:read",
                "im:write",
                "im:history",
                "mpim:history",
                "mpim:read",
                "files:read",
                "files:write",
                "users:read"
            ]
        }
    },
    "settings": {
        "event_subscriptions": {
            "bot_events": [
                "app_mention",
                "message.channels",
                "message.groups",
                "message.im",
                "message.mpim"
            ]
        },
        "interactivity": {
            "is_enabled": true
        },
        "org_deploy_enabled": false,
        "socket_mode_enabled": true,
        "token_rotation_enabled": false
    }

App reinstalled, tested on browser slack and desktop slack.


Please let me know if more details are needed, thank you!

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.

Research direction

Start by tracing the Slack integration's handling of message.im events and the dm_allowed_users setting in config.toml. Reproduce the reported setup with an allowed user, then verify that direct messages are received while channel messages continue to work; add coverage for the regression if the existing test structure supports it.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.