How to Set Up an SMTP Provider in Sparkforge
Use SMTP in Sparkforge only when the native Gmail, Outlook, or Sparkforge Email integrations don't fit. Match the sender email to the integrated SMTP email, expect daily volume limits, and verify with a test send.
SMTP lets you send Sparkforge email through a third-party provider like Amazon SES, SendGrid, Zoho, or a Microsoft 365 account. It is an advanced setup — most users should use the native Gmail or Outlook integration, or Sparkforge Email, instead.
Before you set up SMTP
Native integrations are simpler and more reliable:
- Gmail Sync — two-way email sync for Gmail.
- Outlook Sync — two-way email sync for Outlook.
- Sparkforge Email — managed sending with full statistics.
If you choose SMTP, you do so at your own discretion. Support is best-effort.
Sender email must match the integrated address
The sender email on the outgoing message must match the email you authenticated with your SMTP provider. If it doesn't match — or the address isn't verified with the provider — the message will fail to deliver.
In manual conversations, the sender defaults to your Sparkforge login email. Change it to the SMTP-integrated address before sending.
Daily sending limits
Most SMTP providers cap daily volume. Gmail, for example, limits roughly 100–150 emails per day when connected as a remote client. Check your provider's limits before scheduling large sends.
Why emails get stuck in "Sent" status
SMTP only returns sent, open, click, and bounce events — there is no delivered event. Sparkforge marks an email delivered after the first open. Until then, it shows as sent.
For full sending statistics, use Sparkforge Email or Mailgun.
Provider-specific setup
Amazon SES
- Use the server name listed on the SMTP Settings page.
- Use port 465.
- Use the IAM username and password you generated (save them — they cannot be viewed again).
- Use the Amazon AWS root user email address.
Outlook / Microsoft 365
An "Authentication unsuccessful" error is common. Microsoft requires SMTP Authentication to be explicitly enabled for third-party apps. Enable it in your tenant, then retry. If it still fails, contact Outlook support to authenticate the account.
Test your SMTP integration
- Disable Email Re-Billing while making changes to the default provider.
- Test credentials with the GMass SMTP test tool at gmass.co/smtp-test.
- Send a test email from Sparkforge to confirm delivery and statistics.
Common questions
The "Add Service" button is missing in SMTP services. How do I fix it?
Switch to Agency View > Sub-accounts, click the three dots next to the account, select Manage Client, then open Advanced Settings. Make sure Disable the Add Email Service button in the sub-account Email Services Settings is turned off.
How many SMTP providers can a sub-account have?
Multiple. The same SMTP credentials cannot be added twice — using the same email ID with different integrations is not allowed, and the same provider (e.g., Gmail) cannot be added twice.
Frequently Asked Questions
When should I use SMTP instead of the native email integration?
Why are my SMTP emails stuck on "Sent" status?
Can I use a free Gmail or Yahoo address as my SMTP sender?
Does SMTP support full email analytics?
What port should I use for Amazon SES?
Was this article helpful?
Thanks for the feedback.