Skip to main content
/ Docs
Quickstart API SDKs

Email Configuration

Complete guide to configuring the Trix email system.

Updated

Overview

Trix supports both inbound and outbound email processing. Inbound emails let you store memories, search, and query via email. Outbound emails power notifications, digests, and alerts.

Inbound Email Setup

Enable inbound email to interact with Trix via email. Once configured, you'll receive a unique email address that you can send commands to.

Configuration

.env 
# Enable inbound email processing
EMAIL_INBOUND_ENABLED=true

# Rate limiting
EMAIL_RATE_LIMIT_PER_MINUTE=10
EMAIL_RATE_LIMIT_PER_HOUR=100

Supported Commands

Send emails to your Trix email address with these commands in the subject line:

  • STORE - Save the email body as a memory
  • SEARCH [query] - Search your memories
  • ASK [question] - Ask a question using your memory context

Outbound Email Setup

Configure outbound email for notifications, digests, and transactional emails.

.env 
# Enable notifications
ENABLE_NOTIFICATIONS=true

Notification Types

Trix sends the following types of transactional emails:

Authentication

  • Welcome email on signup
  • Password reset requests
  • Email verification
  • Password change confirmation

Billing & Credits

  • Low credit alerts
  • Credit depletion warnings
  • Payment receipts
  • Subscription lifecycle updates

Webhook Security

Inbound email webhooks are secured with HMAC-SHA256 signature verification and replay prevention. All webhook payloads include a timestamp and signature that must be verified before processing.

See the Webhooks documentation for details on signature verification and replay prevention.

Email Deliverability

For reliable email delivery, ensure the following DNS records are configured for your email domain:

  • SPF - Authorizes sending servers
  • DKIM - Cryptographic email authentication
  • DMARC - Policy for handling authentication failures
  • MX - Mail exchange records for receiving

Trix Cloud handles all DNS and deliverability configuration automatically. These settings are only relevant for self-hosted deployments.

Development Configuration

Mock Email Provider

For development without sending real emails:

.env 
EMAIL_PROVIDER=mock
EMAIL_INBOUND_ENABLED=true

Enable verbose logging in development with LOG_LEVEL=debug and EMAIL_DEBUG=true

Production Checklist

  • Webhook signing key is configured
  • Rate limits are appropriate for your usage
  • HTTPS is enforced for webhook endpoints
  • SPF, DKIM, and DMARC records are configured
  • Sender reputation is monitored