Smart. Focused. Email.
Fast, cross-platform email designed to filter out the noise - so you can focus on what's important.
💡 SMTP server: The system responsible for sending your outgoing email. When you hit Send, your email goes to an SMTP server first. It processes the message, figures out where it needs to go, and relays it to the recipient's mail server. SMTP is the sending half of email. Receiving is handled by IMAP or POP3. The protocol is defined in RFC 5321.
For most people, SMTP is invisible. You add Gmail or Outlook to Spark, sign in with your account, and it's done. Spark and most modern email clients configure everything automatically using OAuth. You never see a server address.
But there's one situation where SMTP settings become your problem: when you're setting up a custom or less common email account manually. A work email running on your company's own server. A domain email from a hosting provider like SiteGround or Namecheap. An older provider that doesn't support OAuth. In those cases, the app will ask you for an outgoing mail server address, a port number, and an encryption type. That's SMTP configuration. This article gives you what you need to fill those fields correctly.
When you hit Send, your email client connects to an SMTP server, typically on port 587. The client hands off the message: recipient address, subject, body, attachments. The SMTP server then does a DNS lookup to find the mail exchange record for the recipient's domain, which tells it where to deliver the message.
If you're both on the same mail server, delivery is direct. Usually you're not, so the server relays the message through one or more intermediate servers until it lands in the recipient's incoming mail server. From there, IMAP takes over, storing it in the recipient's mailbox until they check their email.
The whole thing typically takes a few seconds. SMTP just moves the message. It doesn't store anything, and it doesn't read anything. When delivery fails (wrong address, full mailbox, server rejection), you get a non-delivery report back in your inbox.
Here are the verified SMTP settings for the most common providers. Use these if you're configuring an account manually in Spark or any other email client.
Gmail
Outlook.com / Hotmail / Live (personal accounts — see Microsoft's full settings page)
Microsoft 365 (work/school accounts)
Yahoo Mail
iCloud Mail
One thing that trips people up: if 2-step verification is enabled on your account, your regular password usually won't work for manual SMTP setup. You need to generate an app-specific password from your provider's security settings instead. Google, Microsoft, and Apple all support this.
When you add a custom email account to Spark and it can't connect automatically, here's how to enter your SMTP settings manually.
On Mac or Windows:
On iOS or Android:
For the most current steps, Spark's account setup guide has the full walkthrough.
Wrong server address. Outlook personal accounts (@outlook.com, @hotmail.com, @live.com) use smtp-mail.outlook.com. Microsoft 365 work accounts use smtp.office365.com. They're different. Using the wrong one is a very common mistake.
Using the wrong port. Port 587 is the current standard for sending email securely. Port 25 is the old SMTP port and is blocked by most internet providers to prevent spam. If your settings aren't working and you're on port 25, switch to 587.
Sending without encryption. Always enable TLS. Without it, your credentials and email content travel in plain text. There's no good reason to skip it, and some providers will reject the connection anyway.
2-step verification is on. If you've enabled 2FA on your account and you're trying to use your regular password for SMTP, it won't work. Generate an app-specific password from your provider's security settings and use that instead.