iMessage From the Server — Send Reminders Without Touching Your Phone

The Problem

iMessage is non-negotiable for certain contacts. Board members, some French business contacts, family. "Just text me" means iMessage, not Telegram, not Signal.

But iMessage is locked to Apple devices. I can't send an iMessage from my Linux server. I can't script it through an API. I can't integrate it into my agent workflows. Apple designed it as a walled garden, and I respect the engineering — but I need the garden gate open.

The specific pain points:

1. Reminders: "Remind Pierre about tomorrow's board meeting." I'd have to pick up my phone, open Messages, find Pierre, type the message. For one reminder, fine. For ten, that's ten minutes of thumb-typing.

2. Batch messages: "Invite 20 people to the Paris event." Twenty individual iMessages, each personalized. From a phone. No.

3. Unified inbox: Urgent iMessages while I'm on my laptop go unseen until I glance at my phone. Could be minutes. Could be hours.

4. Meeting auto-responder: When I'm in back-to-back meetings, iMessages pile up unanswered. No "away" status. No auto-reply.

The Solution

BlueBubbles running on my Mac node, connected to Mr.Chief via the imsg bridge. My Mac stays on, acts as the iMessage gateway. The server sends commands to the Mac, the Mac sends iMessages. Incoming iMessages route to Telegram. It's Apple's walled garden with a tunnel underneath.

The Process

Architecture:

Mr.Chief Server (Linux)
    ↓ (API call)
BlueBubbles Server (Bilal's Mac)
    ↓ (native iMessage API)
iMessage (Apple's servers)
    ↓
Recipient's iPhone/Mac

Configuration:

# mrchief.yaml — iMessage bridge
channels:
  imessage:
    enabled: true
    bridge: bluebubbles
    node: bilals-mac              # Tailscale node name
    node_ip: 100.75.113.94       # Tailscale IP

    forwarding:
      target: telegram
      format: |
        📱 iMessage — [sender_name]
        [message_content]
        → Reply: "imsg reply [sender_name] [message]"

    auto_respond:
      enabled: true
      trigger: "calendar_busy"     # When calendar shows I'm in a meeting
      message: "Bilal is in a meeting, back at [next_free_time].
               For urgent matters, message @Alfrawd on Telegram."

Sending a reminder:

Me (in Telegram): "Remind Pierre about tomorrow's board meeting at 9am"

Alfrawd: Sending iMessage to Pierre Dumont...
📱 Sent: "Pierre — reminder: board meeting tomorrow at 9am.
Agenda and deck are in the shared Drive folder. See you there."
✅ Delivered

Batch messaging:

Me: "Send the Paris meetup invite to all 20 contacts on the VIP list"

Alfrawd: Generating personalized invites for 20 contacts...

Preview (first 3):
1. Pierre: "Pierre — Mr.Chief Paris #4 is March 25 at Station F.
   Topic: multi-agent orchestration. You mentioned wanting to see
   the demo last time. Saving you a seat?"

2. Sarah: "Sarah — next Mr.Chief Paris is March 25. Given your work
   on agent pipelines at Mistral, I think you'd enjoy this one. In?"

3. Marc: "Marc — Mr.Chief Paris #4, March 25, Station F. Theme is
   orchestration — right up your alley. Want me to add you?"

Approve batch send? [Send All ✅] [Edit ✏️] [Cancel ❌]

Me: [Send All ✅]

Alfrawd: 📱 Sending 20 iMessages...
✅ 20/20 delivered. 3 read receipts already.

Forwarding urgent iMessages:

# Incoming iMessage routing rules
forwarding_rules:
  immediate:
    - contacts: ["board members", "co-founders", "family"]
    - contains: ["urgent", "emergency", "call me", "ASAP"]

  batch_hourly:
    - contacts: ["known contacts"]

  silent:
    - group_chats: true
    - contacts: ["unknown"]

Meeting auto-responder:

- name: imessage-auto-respond
  trigger: calendar_event_active
  task: |
    When I'm in a meeting (calendar shows busy):
    - Any incoming iMessage from known contacts gets auto-reply:
      "In a meeting until [end_time]. I'll get back to you after.
       For anything urgent, reach me at [Telegram handle]."
    - Don't auto-reply to the same person twice within an hour
    - Don't auto-reply to group chats
    - Log all auto-replies for my review after the meeting

The Results

The auto-responder alone is worth the setup. Before, people would text me during meetings and think I was ignoring them. Now they get an instant, polite reply that sets expectations. Two board members independently told me they appreciated the professionalism. They don't know it's automated.

Try It Yourself

1. Set up BlueBubbles on a Mac that stays on (Mac Mini is ideal)
2. Connect the Mac to your Tailscale network for secure remote access
3. Configure Mr.Chief's iMessage bridge to point to the Mac node
4. Start with forwarding only — get comfortable seeing iMessages in Telegram
5. Add sending capability once forwarding is reliable
6. Enable auto-respond last — test thoroughly to avoid embarrassing misfires

Critical caveat: the Mac must stay on and logged in. BlueBubbles runs as a background service, but if the Mac sleeps or logs out, the bridge goes down. Set up energy preferences to prevent sleep, and add a health check to alert you if the Mac goes offline.

iMessage from the server. Batch invites to 20 people. Auto-respond during meetings. Forward urgencies to Telegram. Apple built the walled garden. I built the tunnel.