proton-bridge-email

Secure local SMTP email sending through Proton Mail Bridge is handled by decrypting age-encrypted credentials at runtime. The provided Python script connects to localhost SMTP to send automated reports or alerts without exposing plaintext secrets.

Sending local SMTP requires a running Proton Mail Bridge instance, an age identity file at ~/.config/age/keys.txt, and an encrypted environment file at ~/openclaw/secrets/proton.env.age containing your SMTP details.

Age encryption protects Proton Bridge credentials by storing SMTP details in an encrypted .env file rather than plaintext. The automation script decrypts this file at runtime using your age identity, ensuring credentials are only exposed in memory during email sending.

Yes, the local SMTP sender is specifically designed for automation workflows like daily reports and alerts. It securely connects to Proton Mail Bridge on localhost to dispatch emails using your encrypted credentials.

You can encrypt your Proton Bridge environment file using the included helper script, scripts/encrypt_env.sh. This script processes your plaintext SMTP credentials into an age-encrypted file required by the email sender.

No, sending email through Proton Bridge does not require storing plaintext SMTP credentials. The workflow uses age-encrypted credential files and decrypts them locally at runtime to securely authenticate with the Proton Mail Bridge SMTP server.