Self-hosted email API for seamless integrations
“Render provides managed hosting with automatic SSL, built-in monitoring, and Redis add-ons. Quick DeployUse the "Deploy to Render" button for automated setup with EmailEngine + Redis configured automatically.”
“By default, EmailEngine stores all data in cleartext in Redis. ... The tool will: Connect to Redis Find all unencrypted secrets Encrypt them with the provided secret Store encrypted values back to Redis Exit”
“EmailEngine requires Redis as its caching database. As long as you have a reasonably recent version of Redis installed, you should be good to go.”
“EnvironmentNodeRequiredBuild Commandnpm install --omit=devInstalls dependenciesStart Commandnpm startStarts EmailEngine”
“Docker Secrets # Create secretecho "your-secret-password" | docker secret create ee_encryption_key -# Use in servicedocker service create \ --name emailengine \ --secret ee_encryption_key \ --env EENGINE_SECRET_FILE=/run/secrets/ee_encryption_key \ emailengine/emailengine”
“Using Secret Management Systems Kubernetes Secrets apiVersion: v1kind: Secretmetadata: name: emailengine-secretstype: OpaquestringData: encryption-key: your-secret-here---apiVersion: v1kind: Podmetadata: name: emailenginespec: containers: - name: emailengine image: emailengine/emailengine env: ...”
“EmailEngine exposes a Prometheus metrics collection endpoint for easier monitoring. Grafana Prometheus”
“Generate a random secret: echo "EENGINE_SECRET=$(openssl rand -hex 32)" > .env”
“Using Secret Management Systems HashiCorp Vault #!/bin/bash# Fetch secret from Vaultexport EENGINE_SECRET=$(vault kv get -field=encryption_key secret/emailengine)emailengine”
“Environment Variable Best Practices tipDon't provide environment variables using the export command in production. Instead:SystemD Service:[Service]Environment="EENGINE_SECRET=secret-password"”
“EmailEngine exposes a Prometheus metrics collection endpoint for easier monitoring.”
“I use CLA assistant for managing CLAs in my projects”
“This guide shows you how to configure EmailEngine to use Gmail REST API as the email backend instead of IMAP/SMTP. With this setup, EmailEngine uses direct Gmail API calls for all operations and receives change notifications via Google Cloud Pub/Sub.”
“Connect Repository: Select "Deploy an existing image from a registry" OR Use public repository: https://github.com/postalsys/emailengine Click "Connect" next to postalsys/emailengine”
“EmailEngine uses BullMQ for reliable message queuing.”