This is the generic guide for any third-party software that accepts SMTP credentials: WordPress mail plugins, Mautic, ActiveCampaign, GitLab, Jira, custom apps, marketing tools, internal scripts, and so on. If your software has a “Server / Host / Username / Password” form, this guide is for you. For dedicated walkthroughs of common platforms, see the Plugins and Integrations sections.Documentation Index
Fetch the complete documentation index at: https://support.jetemail.com/llms.txt
Use this file to discover all available pages before exploring further.
Sign up for JetEmail
Create an account at jetemail.com, then open the dashboard at dash.jetemail.com.
Add and verify your sending domain
- In the dashboard, go to Outbound → Domains
- Add the domain you send from (e.g.
example.com) - Publish every DNS record the dashboard shows (SPF, return-path, DKIM, DMARC, feedback) at your DNS provider
- Wait until the domain shows as verified
Create an SMTP user
- Go to Outbound → SMTP in the dashboard
- Click Create SMTP
- Set a Username and strong Password
- Leave Quota at
0for unlimited, or set a per-user limit if you want to cap how much this app can send
Use a separate SMTP user per app. That way you can rotate or revoke credentials for one app without affecting the others, and the dashboard logs will show you which app is sending what.
Plug the values into your software
Open your software’s outgoing mail / SMTP settings and use these values:
| Setting | Value |
|---|---|
| SMTP host / server | relay.jetsmtp.net |
| Port | 587 (STARTTLS) — recommended.465 works if your software requires implicit SSL/TLS.25 and 2525 are also available. |
| Encryption | STARTTLS on 25, 587, 2525. SSL/TLS on 465. |
| Authentication | PLAIN or LOGIN |
| Username | The SMTP username from step 3 |
| Password | The SMTP password from step 3 |
| From address | Any address on a verified domain |
EU region. If you need an EU-only endpoint, use
relay-eu.jetsmtp.net with the same settings. Otherwise stick to the global anycast endpoint (relay.jetsmtp.net) for the best routing.Send a test message
Most apps have a “Send test email” button in the SMTP settings — use it. If they don’t, trigger any email-sending action (signup, password reset, transactional notification) and confirm it lands.Then open the JetEmail dashboard’s Logs view to confirm the message was accepted and authenticated. If something looks wrong, the SMTP block error reference explains the most common rejection codes.
Common pitfalls
- From address must be on a verified domain. Sending from
gmail.com,yahoo.com, or any address you don’t own will fail authentication. - Don’t put
@in the username. The SMTP username is the literal string you set in step 3, not an email address. - Port 25 is often blocked by residential ISPs and some cloud providers. Use 587 if your network blocks 25.
- One credential per app. Sharing a single SMTP user across multiple apps makes rotation and incident response much harder.
Next steps
Domain Lockdown
Stop other JetEmail accounts from sending as your domains.
DMARC
Tighten your authentication policy once mail is flowing.