Sigil documentation
ReferenceJSON-RPC

sigil_resolveMail

Resolve a `.sigil` route or mailbox ID into mail delivery metadata.

Method

sigil_resolveMail is registered in the canonical JSON-RPC catalog. Use POST /rpc, Content-Type: application/json, JSON-RPC 2.0 and a caller-controlled request id. Node RPC profile, build feature and runtime activation checks still apply.

Resolve a .sigil route or mailbox ID into mail delivery metadata.

Request binding

Source handler: rpc_mail::handle_resolve_mail in sigil/node/sigil-node/src/rpc_mail.rs, line 267.

The handler uses no directly named params.get fields, or delegates input parsing to a typed helper. Use the request types below rather than assuming an empty parameter object.

Parsing excerpt

These source excerpts show binding and validation; they are not runnable client code.

    let route_or_name = match extract_string_param(&req.params, 0, "route_or_name")
        .or_else(|| extract_string_param(&req.params, 0, "name"))
    {
        Some(v) => v,
        None => return missing(req, "route_or_name"),
    };

        .or_else(|| extract_string_param(&req.params, 0, "name"))
    {
        Some(v) => v,
        None => return missing(req, "route_or_name"),
    };

Responses and failures

Check HTTP status, parse the JSON-RPC envelope, reject error, and require result on success. Preserve large base-unit integers without floating-point rounding. A catalog method does not bypass authentication, capability, policy or activation requirements.

On this page