email-skill

You can send automated email notifications from both a platform public mail service and a personal SMTP account using a unified gateway. This gateway routes messages based on your chosen provider configuration, automatically handling checks, verification, and sending via an HTTP proxy.

Yes, you can retrieve emails and attachments from your personal IMAP mailbox using this gateway. By selecting the personal provider option, the system optionally utilizes Node.js to perform full-featured email sending and inbox management operations.

You need Node.js to send emails through a personal SMTP provider only as a fallback for personal provider operations. Cross-platform bash scripts for macOS/Linux and CMD scripts for Windows handle the primary binding, verification, and sending tasks.

The best way to route daily summary reports to yourself versus notifying teammates is through explicit provider selection. Choosing the platform provider sends self-notifications, while choosing the personal provider enables full-featured email sending to teammates.

The platform email binding workflow requires verification code handling to securely link your account to the public mail service. This automatic process checks configurations and processes verification codes to ensure authorized email sending via the HTTP proxy.

Yes, curl and jq are required dependencies for sending email notifications. The underlying scripts rely on these tools to execute binding, verification, and sending operations via an HTTP proxy across both macOS/Linux and Windows environments.