himalaya tool for hermes not sending attachments ?When you use the Himalaya Email CLI for the Hermes Agent, attachments won't send if you are relying on the raw text interface. Himalaya requires the use of MIME Meta Language (MML) tags to process multipart attachments properly, and your text might be formatted incorrectly.How to Fix Attachment Sending IssuesIf you are instructing Hermes to send emails with attachments, follow these guidelines to ensure the himalaya template send pipeline processes them:Use MML Tags: Raw text arguments lack attachment parsing. You must include an MML part tag like this within the message body:<#part filename=/path/to/file.pdf><#/part>Use Piped Input: Instead of interactive compose mode, pipe your formatted email template directly into Himalaya for reliable handling:

cat << 'EOF' | himalaya template send
From: you@example.com
To: recipient@example.com
Subject: Test with Attachment
Please find the attached document.
<#part filename=/absolute/path/to/document.pdf><#/part>
EOF

Verify skip_attachments Config: Double-check your Himalaya configuration (usually in ~/.config/himalaya/config.toml) to ensure you haven't globally blocked attachments.Hermes CLI Mismatch: Occasionally, the built-in Hermes skills map to older or deprecated Himalaya CLI flags. Running himalaya --help within your terminal can verify the exact subcommands available to your installed binary.

The transcript shows Hermes repeatedly using regular CLI flags (--attachment), standard MIME boundaries (--my-boundary), or shell strings which the Himalaya Email CLI does not natively support.Himalaya treats everything in the body or template as plain text unless it sees specific Emacs-style MML (MIME Meta Language) tags embedded inside the message body.The SolutionTo get Hermes to successfully send the attachment, you need to command it to inject the MML syntax directly into the himalaya template send pipeline.Give Hermes this exact instruction:

Use the himalaya template send pipeline with the MML part tag syntax to attach /home/devon/.hermes/AGENTS.md. Do not use the --attachment flag."

What the correct command looks likeWhen Hermes executes it properly via terminal or stdin piping, the command will look like this:

cat << 'EOF' | himalaya template send --account nemo
From: nemo@souriscomputech.co.za
To: devon@solar-europe.co.za
Subject: Copy of AGENTS.md



Please find the requested AGENTS.md  file attached below.

<#part filename=/home/devon/.hermes/AGENTS.md
 type=text/markdown><#/part>
EOF

Why the previous attempts failedhimalaya send --attachment ... (Exit 2): Modern versions of Himalaya do not have a top-level send command or a universal --attachment flag for message creation.Raw Content-Type headers (Exit 101/No attachment): Trying to manually forge a raw multipart/mixed header via cat failed because Himalaya re-encodes the text body into a standard single-part message, ignoring your text-based boundaries.MML Tag Syntax: Without the literal <#part ...><#/part> snippet, Himalaya assumes the entire payload is a standard string and leaves the attachment behind.



