Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix iMessage channel shows as unavailable despite being enabled [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61629•Fetched 2026-04-08 02:56:37
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
joemcurryjoemcurry
Participants
joemcurryjoemcurry

Root Cause

  1. Initial Configuration:

    • dmPolicy was set to "pairing"
    • allowFrom was empty []

  2. Required for dmPolicy: "open":

    • allowFrom must include ["*"] (or specific contacts)
RAW_BUFFERClick to expand / collapse

OpenClaw Issue Report - iMessage Channel Configuration

Date: 2026-04-05

Issue: iMessage Channel Unavailability

Problem

Despite enabling the iMessage channel in OpenClaw configuration, the channel showed status as "ON, OK, configured" but returned "unavailable" when attempting to send messages.

Root Cause Analysis

  1. Initial Configuration:

    • dmPolicy was set to "pairing"
    • allowFrom was empty []

  2. Required for dmPolicy: "open":

    • allowFrom must include ["*"] (or specific contacts)

Resolution Applied

  1. Changed dmPolicy from "pairing" to "open"
  2. Added allowFrom: ["*"]
  3. Restarted OpenClaw gateway
  4. Result: ✅ iMessage now working

Verification

Recommended Fix for OpenClaw

To avoid manual intervention, the iMessage channel configuration should:

  • Default dmPolicy to "pairing" (secure-by-default)
  • Require explicit allowFrom configuration
  • Document: iMessage requires device pairing or explicit allowlist

Affected Channels

ChannelInitial StateRequired Fix
iMessagedmPolicy: "pairing"Set allowFrom: ["*"] or use pairing
TelegramWorkingNo changes needed
DiscordWorkingNo changes needed

Suggested Improvement

Update OpenClaw channel defaults to require explicit allowlist configuration for iMessage to prevent "unavailable" status when dmPolicy is "open" but allowFrom is empty.

Reported by: Jarvis (on behalf of user) Status: Documented for user review before sending to GitHub

extent analysis

TL;DR

To fix the iMessage channel unavailability issue in OpenClaw, change the dmPolicy from "pairing" to "open" and add allowFrom: ["*"] to the configuration.

Guidance

  • Verify that dmPolicy is set to "open" and allowFrom includes ["*"] for the iMessage channel to function correctly.
  • If using dmPolicy: "pairing", ensure that the necessary pairing steps are completed to avoid the "unavailable" status.
  • Restart the OpenClaw gateway after making configuration changes to apply the updates.
  • Test the iMessage channel using a command like imsg send --to "[email protected]" --text "Test" to verify that messages are sent successfully.

Example

No explicit code snippet is provided, but the configuration change can be represented as:

{
  "dmPolicy": "open",
  "allowFrom": ["*"]
}

Notes

This fix assumes that the issue is solely related to the iMessage channel configuration in OpenClaw. Other channels like Telegram and Discord are reported to be working and do not require changes.

Recommendation

Apply the workaround by changing the dmPolicy to "open" and adding allowFrom: ["*"] to the iMessage channel configuration, as this directly addresses the reported issue and allows for successful message sending.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING