Problem
When screening or auditing mail with the HEY CLI (hey --json), there is no reliable way to see the envelope recipient (SMTP RCPT TO / Delivered-To / alias that actually received the message). Billing portals and payment processors often show a different address than the mailbox you are looking at, and without envelope recipient data it is hard to confirm which alias or forward path a message hit.
Request
Please expose in CLI JSON (thread and/or message payloads) at least one of:
- envelope
To / RCPT TO
Delivered-To
- the HEY alias / address that received the message
Even a read-only field would unblock scripting and support workflows.
Context
Filed after hitting this while reconciling a billing receipt against mailbox state. Soft-delete / Trash via CLI works; hard-delete is out of scope here. This is only about recipient metadata visibility.
Problem
When screening or auditing mail with the HEY CLI (
hey --json), there is no reliable way to see the envelope recipient (SMTPRCPT TO/Delivered-To/ alias that actually received the message). Billing portals and payment processors often show a different address than the mailbox you are looking at, and without envelope recipient data it is hard to confirm which alias or forward path a message hit.Request
Please expose in CLI JSON (thread and/or message payloads) at least one of:
To/RCPT TODelivered-ToEven a read-only field would unblock scripting and support workflows.
Context
Filed after hitting this while reconciling a billing receipt against mailbox state. Soft-delete / Trash via CLI works; hard-delete is out of scope here. This is only about recipient metadata visibility.