Identities Introduction
An Identity in Mailofly represents an authorized, connected email mailbox—such as a personal Gmail account, Google Workspace mailbox, or custom SMTP server—that Mailofly uses to dispatch emails on your behalf. While verified Domains route outbound traffic through Mailofly’s enterprise Amazon SES relay with dedicated IP pools and custom DKIM keys, Identities dispatch emails directly through your existing mailbox provider using OAuth 2.0 or SMTP credentials.What is an Identity?
An identity connects your Mailofly workspace directly to an existing email provider:- Google (Gmail & Google Workspace): Connected via secure, 1-click Google OAuth 2.0. Mailofly obtains scoped sending permissions to dispatch emails through the official Gmail API / transport.
- Custom SMTP: Connected via standard SMTP credentials (host, port, username, password, and SSL/TLS encryption). Mailofly connects directly to your external mail server (such as SendGrid, Mailgun, Postmark, Amazon SES, or self-hosted servers like Postfix/cPanel) to transmit mail.
Identities vs. Domains
Mailofly supports both sending models. Here is how they compare:How Users Can Use Identities
Identities can be used across all Mailofly interfaces:- REST API & SDKs:
Specify the identity’s email in the
fromfield:Or explicitly pass theaccount_key(acc_...): - Visual Dashboard (Compose): Select your connected identity from the From dropdown when composing single emails.
- Marketing Campaigns & Broadcasts: Assign one or more connected identities as the sending accounts for automated campaigns.
Important Limitations
Before using identities for mission-critical production traffic, keep the following constraints in mind:For full delivery verification, bounce suppression, unsubscribe compliance, and custom domain DKIM signing, we recommend adding a Custom Sending Domain.