SMTP Configuration

Every outgoing email — signup confirmations, password resets, campaign approvals, payment notifications — goes through the SMTP server you configure here. Until it is set up, none of them are delivered.

Why Configure SMTP

Sending through your own mail server means email arrives from your domain rather than a shared platform address. That matters for two reasons: partners recognise and trust it, and your domain's own authentication records decide whether it reaches the inbox.

Go to Settings → Email → SMTP.

AffClix SMTP configuration screen showing server settings, port and encryption, authentication credentials, sender identity and a test connection panel
SMTP settings — server, authentication, sender identity, and a test send.

Settings Reference

SettingNotes
SMTP ServerYour provider's hostname — for example smtp.gmail.com, smtp.sendgrid.net, or your own mail host.
Port & EncryptionNone, SSL or TLS. TLS is recommended.
UsernameThe SMTP login, usually the full email address.
PasswordThe SMTP password. For Gmail this must be an App Password, not the account password.
From NameThe sender name recipients see. Use your network's name.
Sender EmailThe From address. Must be authorised by the SMTP server's domain.
Save before testing

The Send Test Email button uses the stored settings, not what is currently on screen. Save first, then test — otherwise you will be testing the previous configuration and drawing the wrong conclusion.

Ports and Encryption

PortEncryptionNotes
587TLSThe modern default. Try this first.
465SSLWidely supported, still common.
25None or TLSBlocked by most hosting providers. Avoid.
2525TLSOffered by some providers as an alternative when 587 is blocked.

Port 587 with TLS, or 465 with SSL, are the two combinations that work almost everywhere.

Provider Guides

ProviderGuide
Gmail / Google WorkspaceGmail SMTP setup
Microsoft 365 / OutlookMicrosoft SMTP setup
Zoho MailZoho SMTP setup
Consider a transactional provider at volume

Mailbox providers like Gmail and Microsoft 365 apply per-account sending limits that a growing network will hit. A dedicated transactional service — SendGrid, Postmark, Amazon SES and similar — is built for this traffic and gives you delivery and bounce reporting alongside it.

Deliverability

Correct SMTP settings get mail sent. Getting it delivered depends on DNS records published on your sending domain, which sit outside AffClix.

RecordWhat it does
SPFLists which servers may send for your domain.
DKIMCryptographically signs your mail so recipients can verify it was not altered.
DMARCTells recipients what to do when SPF or DKIM fails, and sends you reports.
Without SPF and DKIM, expect the spam folder

Password resets and payment notifications that silently land in spam generate support tickets that look like platform bugs. Publish these records before you invite partners.

Troubleshooting

SymptomLikely cause
Authentication failedWrong username or password. For Gmail, you need an App Password rather than the account password.
Connection timed outThe port is blocked by your host. Try 587, then 465, then 2525.
Connection refusedWrong hostname, or the wrong encryption setting for that port.
Sender address rejectedThe From address is not authorised on the SMTP account.
Test succeeds, real emails do not arriveDelivered but filtered. Check spam, then check SPF and DKIM.
Worked, then stoppedA rotated password, an expired App Password, or a provider sending limit.
Rate this article
★★★★★
Thanks for rating!

Was this article helpful?