openclaw-email-bypass

What This Skill Does

The openclaw-email-bypass skill serves as a robust solution for developers and AI agents operating in cloud environments where standard SMTP ports (25, 465, and 587) are restricted. By leveraging Google Apps Script as a secure, private relay, this skill shifts email transmission from high-risk SMTP protocols to standard HTTPS (Port 443). This ensures that your agents can reliably send notifications, alerts, or transactional emails from restricted VPS environments like AWS or DigitalOcean without triggering spam filters or encountering port-level blocks. The architecture is entirely self-hosted, ensuring that your organization retains full ownership of the data pipeline.

Installation

Installation is streamlined through the ClawKit ecosystem. Execute the following command in your terminal: clawhub install openclaw/skills/skills/rishikreddyl/openclaw-email-bypass Once installed, you must deploy the provided assets/Code.gs to a private Google Apps Script project. Upon deployment, ensure you configure the GOOGLE_SCRIPT_URL and GOOGLE_SCRIPT_TOKEN in your environment variables to authorize the connection between your agent and the script.

Use Cases

This skill is ideal for:

1. Automated alert systems for infrastructure monitoring agents.
2. Sending reports directly from headless data analysis agents.
3. Handling transactional communications where direct SMTP relaying is blocked by cloud provider policies.
4. Maintaining agent sovereignty by avoiding third-party email APIs that require extensive KYC or API keys.

Example Prompts

1. "Send an email to [email protected] with the subject 'System Alert' and body 'The server CPU load has exceeded 90%.'"
2. "Please notify the user at [email protected] using the email skill. Use the subject 'Weekly Report' and attach the HTML formatted report provided in the latest data output."
3. "Email the security team at [email protected] with the subject 'Security Breach Detected' and detail the anomalous login activity identified in the logs."

Tips & Limitations

• Security: Always treat your GOOGLE_SCRIPT_TOKEN as a sensitive credential. Never expose it in logs.
• Reliability: While Google Apps Script is highly reliable, it is subject to standard Google quotas for email sending. Ensure your agent does not exceed daily email limits defined by your Google account type.
• Debugging: If messages fail to arrive, check the execution logs within the Google Apps Script project dashboard to confirm the token is being passed correctly.