Airmail / Developer guides
SMTP Relay for Indian Developers
A practical SMTP option for India-focused products, without promising a special inbox route or unlimited delivery speed.
Free Developer beta. Verified domain and manual sending approval required.
Evaluate operational fit
Check the current INR plan catalog, applicable taxes, monthly allowance and daily safety limits before migrating. Public paid subscriptions are request-access during beta. Local currency does not imply a data-residency certification, a dedicated Indian sending IP, 24/7 support, or a guaranteed Gmail delivery time. Ask support about your use case and provider concentration before committing a larger stream.
SMTP settings
Use smtp.airmailai.tech, port 587, STARTTLS required, and the username/password created in your workspace SMTP settings. These are not your dashboard login or REST API key. Keep certificate verification enabled. Do not choose implicit TLS on port 587. SMTP is submission only: it is not an IMAP/POP mailbox. Set a verified From address and monitored Reply-To. Preserve Message-ID and identical MIME content when retrying an uncertain SMTP transaction.
Host: smtp.airmailai.tech
Port: 587
Encryption: STARTTLS (required)
Username: your Airmail SMTP username
Password: your one-time SMTP passwordPlan for destination concentration
Ten thousand emails spread across a month is different from ten thousand Gmail messages at once. Start with genuine transactional activity, monitor queue wait and delivered outcomes, and request a capacity review before material growth. Buying allowance does not bypass pacing. Keep security-critical email on your current validated transport until a separate latency review supports a change.
Before your first production message
Start with the free Developer beta. Verify your account, create a workspace and add a domain you control: example.com and mail.example.com are both supported. Publish the records shown in Domains. Merge an existing SPF policy rather than adding another; preserve a valid existing DMARC policy. Create an API key after verification, use the dashboard for one owner-controlled validation, and request production approval. SMTP credentials become available after activation. No repository or SSH access is needed.
Know the boundaries
Airmail is a controlled public beta. Production sending requires manual approval. Paid plans remain request-access for general signups; payment never grants sending approval. Monthly allowance, daily safety quota and provider pacing are different limits. Sending is transactional by default; partnership/campaign access needs separate approval and is not a purchased-list service. Dedicated reputation isolation is not currently included. There is no inbox-placement guarantee or published OTP delivery SLA.