gog-email-send

To send email with a human approval gate, you must reply with the exact confirmation string "YES, SEND". This operational safety mechanism blocks paraphrased consent and prevents unintended outgoing communication.

Audit logging for email sending records each send attempt, including recipients and subject, to an audit trail for accountability. It avoids logging the full body content to maintain security while tracking operational success or failure.

To use the gog CLI for email sending, you need an approved draft and must provide the exact "YES, SEND" confirmation string. The system validates the recipient list and subject before executing the delivery.

Implied consent or paraphrased approval cannot trigger confirmed email sending. The system requires the exact phrase "YES, SEND" as a strict confirmation gate to ensure operational safety and prevent unauthorized transmission.

The best way to verify recipients and subject before sending is through the pre-send disclosure view. This presents a final "Ready to Send" summary, allowing you to validate the recipient list, subject, and body snippet before execution.

Yes, the audit trail logging limitation is that it records recipients and subject but avoids storing the full body content. This ensures accountability for the send attempt while maintaining message privacy during email delivery operations.