Skip to main content

Enterprise Mail Relays and Ingestion Adapters

BrokerOS isolates external mail transport logic within dedicated, self-contained TypeScript packages inside integrations/mail/. Neither apps/api nor apps/workers makes direct HTTP calls to mail providers; all transmission, signature validation, and error normalization route through these typed adapters. Through the Email Provider Configuration Studio (EmailProviderConfigCard.tsx), administrators can connect and manage eight enterprise email services simultaneously.

Provider Connection Architecture


The Eight Supported Mail Providers

Amazon SES

High-volume transactional and marketing relay. Connects via IAM Access Key ID, Secret Access Key, and AWS Region (ap-south-1, us-east-1). Supports Amazon SNS bounce/complaint webhooks.

Twilio SendGrid

Cloud SMTP and Web API relay. Connects via SendGrid API Key. Supports Event Webhooks for live delivery receipts and Inbound Parse for team inbox replies.

Brevo (Sendinblue)

European transactional relay with dedicated IP support. Connects via Brevo API Key. Full webhook tracking for opens, clicks, and hard bounces.

Mailchimp / Mandrill

Transactional email engine. Connects via Mandrill API Key and server data center prefix (us20). Includes inbound webhook integration.

Mailgun

Developer email API with built-in email validation. Connects via Mailgun API Key, verified sending domain, and regional endpoint (US or EU).

Google Workspace / Gmail

1-on-1 executive communication and small team inboxes. Connects via OAuth2 Client Credentials or secure Google App Passwords.

Microsoft 365 / Outlook

Corporate Microsoft Exchange integration. Connects via Microsoft Graph API using Azure AD OAuth2 Client ID, Client Secret, and Tenant ID.

Constant Contact

Integrated email service. Connects via developer Client ID and OAuth2 Access Token for scheduled list delivery.

Required Provider Configuration Parameters


Managing Sender Domains and Daily Quotas

Through the Provider Configuration Studio, administrators manage sender identities across integrations:
  • Add Sender Identity: Define the verified fromEmail (for example, sales@skyline-residences.com) and default fromName (for example, Skyline Realty Sales Team).
  • Daily Quota Enforcement: Configure daily volume limits per provider (such as 2,000 emails/day for newly connected domains or 50,000/day for established SES relays).
  • Domain Verification Sync: One-click action to query provider APIs and verify whether DNS records have propagated successfully.