Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Also use when encountering AppleScript errors, unexpected Mail.app behavior, when adding new connector methods, or when debugging JSON output from ASObjC. Covers string escaping, attachment handling, Gmail compatibility, message ID lookup patterns, NSJSONSerialization gotchas, and known Mail.app automation limitations.
التثبيت
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Also use when encountering AppleScript errors, unexpected Mail.app behavior, when adding new connector methods, or when debugging JSON output from ASObjC. Covers string escaping, attachment handling, Gmail compatibility, message ID lookup patterns, NSJSONSerialization gotchas, and known Mail.app automation limitations.
AppleScript + Apple Mail Patterns
Emitting JSON from AppleScript
Scripts emit JSON via ASObjC + NSJSONSerialization (not pipe-delimited text). Use the _wrap_as_json_script(body) helper in mail_connector.py and parse responses with parse_applescript_json(result) from utils.py.
Tell-block contract: the body passed to _wrap_as_json_script must contain a tell application "Mail" ... end tell block and assign the final value to a variable named resultData (list, record, or scalar).
Record key gotcha — always quote name: Use |name|:(name of acc), never name:(name of acc). The bare form collides with NSObject's name selector and the key is silently dropped during NSDictionary conversion, leaving records without their name field.
missing value gotcha:NSJSONSerialization rejects missing value. For optional properties (e.g., email addresses of an account with none, unread count on some mailboxes), coerce before building the record:
set accEmails to email addresses of acc
if accEmails is missing value then set accEmails to {}
Error propagation: Do NOT wrap the tell-body in try / on error when you want typed exceptions (MailAccountNotFoundError, MailMessageNotFoundError, etc.). Let AppleScript errors bubble via stderr — _run_applescript maps them to the right exception type.
Gmail Label-Based System
Gmail doesn't support standard IMAP move operations. The update_message tool has a gmail_mode parameter (when used with destination_mailbox):
# Standard IMAP (Exchange, iCloud, etc.)
move message to destination_mailbox
# Gmail mode (copy + delete)
duplicate message to destination_mailbox
delete message # Removes from source label
Bug story: Early versions silently failed when moving Gmail messages. The move appeared to succeed but the message stayed in the source mailbox. gmail_mode was added to handle this.
When to use: Always expose gmail_mode as an optional parameter on any tool that moves or archives messages.
Message ID Lookup
Finding a specific message by ID requires searching across accounts and mailboxes:
tell application "Mail"
set allAccounts to every account
repeat with acct in allAccounts
set allMailboxes to every mailbox of acct
repeat with mbox in allMailboxes
set msgs to (messages of mbox whose id is targetId)
if (count of msgs) > 0 then
return first item of msgs
end if
end repeat
end repeat
end tell
Performance: This is O(accounts × mailboxes). For users with many accounts, this can be slow. The whose clause makes it tolerable but not fast.
Optimization: If the caller knows the account and mailbox, always accept them as optional parameters to narrow the search.
String Escaping
Always use escape_applescript_string() for user-provided text:
# In utils.py — escapes backslashes first, then double quotesdefescape_applescript_string(s: str) -> str:
return s.replace("\\", "\\\\").replace('"', '\\"')
Bug story: Unescaped quotes in email subjects caused AppleScript blocks to fail silently. The error appears as a generic "Can't make" error in stderr with no indication of the actual cause.
Rule: Every string interpolated into AppleScript MUST go through escape_applescript_string(). No exceptions. Check via check_applescript_safety.sh.
Attachment Handling
Attachments use POSIX file references:
-- Sending attachments
set theAttachment to POSIX file "/Users/user/file.pdf"
make new attachment with properties {file name: theAttachment} at after the last paragraph
-- Saving attachments
save attachment theAttach in POSIX file "/Users/user/Downloads/"
Extension not in blocklist (.exe, .bat, .sh, .app, etc.)
Size under 25MB limit
whose Clause Filtering
Use AppleScript whose clauses for server-side filtering instead of fetching all messages:
-- GOOD: Server-side filter (fast)
set msgs to (messages of mbox whose sender contains "user@example.com")
-- BAD: Fetch all then filter in Python (slow)
set msgs to every message of mbox
-- then filter in Python
Combine clauses for multi-field search:
messages whose sender contains "user" and subject contains "report"
Limitation:whose clauses don't support OR logic well. For OR conditions, use multiple whose queries and merge results in Python.
Known Mail.app Automation Limitations
No scheduled sending — Mail.app has no AppleScript support for delayed/scheduled sends
Thread reconstruction is possible but not native — Mail.app has no thread or conversation class. Reconstruct threads by reading headers of msg for in-reply-to, references, and matching against message id of msg (the RFC 822 header value) across candidate messages. whose message id is "X" is NOT indexed (~21s per lookup on a real mailbox); always subject-prefilter first. See get_thread in mail_connector.py.
Rule management is partial — Rules are readable (rules collection, name, enabled, conditions/actions), but have no stable id and must be addressed positionally or by non-unique name. Mutation paths (creating, updating, deleting) are more complex and not yet implemented.
No smart mailbox access — Smart mailboxes are not exposed to AppleScript
Rich text body — content of message returns plain text; HTML body requires alternate approach
Read receipt — Cannot request or detect read receipts
Draft management — Creating drafts is possible but managing them is limited
Error Handling Pattern
try
-- operation
return "result_data"
on error errMsg
return "ERROR: " & errMsg
end try
Python-side parsing:
if result.startswith("ERROR:"):
raise MailAppleScriptError(result[7:])
stderr-based errors are caught in _run_applescript() and routed to typed exceptions:
"Can't get account" → MailAccountNotFoundError
"Can't get mailbox" → MailMailboxNotFoundError
"Can't get message" → MailMessageNotFoundError
Everything else → MailAppleScriptError
Checklist: New AppleScript Operation
All user strings escaped with escape_applescript_string()
All inputs sanitized with sanitize_input()
Error handling with try/on error in AppleScript
Timeout considered (complex operations may need > 60s)
Integration test written against real Mail.app
check_applescript_safety.sh passes
Gmail compatibility considered (does this operation work with labels?)