Google Workspace + MailKite

Google Workspace (Gmail) is the enterprise email standard from Google. Use MailKite alongside Workspace — MailKite for transactional email and inbound parsing, Gmail for employee mailboxes.

What you need

• A verified domain with SPF + DKIM published
• Your API key (mk_live_…)
• Google Workspace tenant

Send email

Use MailKite SMTP for transactional email. Keep Gmail for employee mailboxes.

# Use MailKite for transactional, Gmail for employee mail
# Configure Gmail SMTP relay or use MailKite directly

# MailKite SMTP (simpler):
SMTP Host: smtp.mailkite.dev
SMTP Port: 587
SMTP Username: mailkite
SMTP Password: mk_live_...
From: noreply@yourdomain.com

# Gmail SMTP relay (for reference):
# SMTP Host: smtp.gmail.com
# Port: 587 (STARTTLS)
# Requires App Password or OAuth2

Receive inbound email (optional)

Route specific addresses (support@, billing@) to MailKite for parsing. Keep employee mail in Gmail.

# MailKite inbound webhook for Gmail routing
# Forward specific addresses to MailKite for parsing
# Keep employee mail in Gmail

# Configure DNS MX to point at MailKite
# for addresses you want to parse (e.g., support@, billing@)

Test it

Send via MailKite SMTP or API.

# Quick test
echo "Test" | swaks --to test@example.com --from noreply@yourdomain.com \
  --server smtp.mailkite.dev --port 587 \
  --auth USER=mailkite --auth-password mk_live_...

Troubleshooting

• Gmail SMTP relay requires "less secure app access" (deprecated) or OAuth2 setup.
• MailKite has none of that — just an API key. No OAuth, no app passwords.
• Use DNS MX routing to split traffic: MailKite for support@, Gmail for employee addresses.

See the SMTP relay docs for the full connection reference, or all integrations for other platforms.