Connect your email.
In about five minutes.

1. 1Open your Google Account and go to Security.
2. 2Turn on 2-Step Verification. The App Passwords page does not appear until you do.
3. 3Go to myaccount.google.com/apppasswords, type a name like Rechlio, and select Create.
4. 4Copy the 16 characters. Spaces in the displayed value are for readability — they are ignored either way.
5. 5For Google Workspace, an administrator may need to allow app passwords in the Admin console under Security, then Less secure apps and app passwords.

Gmail applies a sending limit of roughly 500 recipients a day on personal accounts and 2,000 on Workspace. Campaigns above that will start failing partway through, from Google rather than from Rechlio.

1. 1Sign in at accounts.zoho.in and open Security.
2. 2Turn on Multi-Factor Authentication if it is not already on — app passwords do not exist without it.
3. 3Open App Passwords, choose Generate New Password, and name it Rechlio.
4. 4Copy the password that appears. It is shown once.
5. 5In Zoho Mail, open Settings, then Mail Accounts, and confirm IMAP Access is enabled — this is what lets replies be read.

1. 1Sign in at accounts.zoho.in and open Security.
2. 2Turn on Multi-Factor Authentication, then open App Passwords and generate one.
3. 3In Zoho Mail, go to Settings, then Mail Accounts, and enable both IMAP Access and SMTP.
4. 4Use smtp.zoho.in, not smtppro — the pro host rejects free accounts.

1. 1Sign in at accounts.zoho.com — the .com console, not .in.
2. 2Open Security, enable Multi-Factor Authentication, then generate an App Password.
3. 3If you are on a paid Workplace plan, change the host to smtppro.zoho.com.

Zoho runs separate data centres. An account created in the US will not authenticate against the .in hosts and vice versa. If the password is right and login still fails, you are on the wrong region.

1. 1Open login.yahoo.com/account/security.
2. 2Turn on 2-Step Verification.
3. 3Select Generate app password, choose Other App, and name it Rechlio.
4. 4Copy the password shown.

1. 1An administrator opens the Microsoft 365 admin centre, finds the user, and enables Authenticated SMTP on that mailbox.
2. 2Turn on multi-factor authentication for the account at mysignins.microsoft.com/security-info.
3. 3Create an app password from the same page, under Add sign-in method.
4. 4Use port 587 with STARTTLS. Port 465 is not offered.

Two dated limits, both from Microsoft. Replies cannot be read at all — basic authentication on IMAP is already switched off permanently across Exchange Online and nobody, including Microsoft support, can re-enable it. And sending is on a clock: from the end of December 2026, basic auth for SMTP AUTH is disabled by default on existing tenants and unavailable on new ones. If you are choosing a provider today, choose a different one.

1. 1Open account.microsoft.com/security and turn on two-step verification.
2. 2Create an app password under Advanced security options.
3. 3Use port 587 with STARTTLS.

Microsoft has been progressively closing basic authentication on personal accounts for third-party apps, and app passwords are basic authentication. This may already have stopped working on your account. Replies cannot be read.

1. 1Open hPanel, then Emails, and select your domain.
2. 2Find the mailbox and use its password, or set a new one.
3. 3Use port 465 with SSL.

1. 1Sign in to your GoDaddy Email & Office dashboard.
2. 2Confirm the mailbox is active and note its password.
3. 3Use smtpout.secureserver.net on port 465 with SSL.

GoDaddy applies low hourly send limits on Workspace Email. Large campaigns will be throttled by the provider.

1. 1Open the Namecheap Private Email dashboard.
2. 2Confirm the mailbox exists and note its password.
3. 3Use mail.privateemail.com on port 465 with SSL.

1. 1Open Settings, then API Keys, in the SendGrid dashboard.
2. 2Create an API Key with Restricted Access and enable Mail Send.
3. 3Copy the key. It is shown once and starts with SG.
4. 4Verify your sending domain under Settings, then Sender Authentication, before sending anything real.
5. 5Put the word apikey in the username field, exactly that, and the key in the password field.

SendGrid is a send-only relay. There is no mailbox behind it, so replies cannot be read and a sequence will not stop when somebody answers. Set a Reply-To address on a mailbox you can also connect if you need that.

1. 1Open the Amazon SES console and pick the region you send from.
2. 2Go to SMTP settings, then Create SMTP credentials. This creates an IAM user and derives an SMTP password from it.
3. 3Download the credentials CSV. The password cannot be shown again.
4. 4Change the host to match your region — the default here is Mumbai, ap-south-1.
5. 5Move out of the SES sandbox before sending to addresses you have not verified.

Your AWS access key and secret will not work here. SES derives a separate SMTP password, and pasting the IAM secret is the single most common SES setup failure. SES is also send-only: no inbox, so no reply detection.

1. 1Open Sending, then Domains, and select your domain.
2. 2Open SMTP credentials and copy the login, or create a new one.
3. 3Reset the password if you do not have it — it is not shown again after creation.
4. 4Complete DNS verification for the domain first, or Mailgun will accept the connection and refuse the mail.

Send-only. No inbox, so replies cannot be read.