Custom SMTP in Scoreapps | Full Guide

Custom SMTP Configuration in Scoreapps

Custom SMTP Configuration in Scoreapps

Custom SMTP allows emails sent by Scoreapps tools to use a consistent brand identity. It is especially useful for partners, agencies and accounts that need audits, notifications and automated communications to be sent from their own domain.

Goal of this guide: understand which details you need from your email provider, how to fill in each field and how to validate delivery before using it in real workflows.

Where to configure it

Custom SMTP screen with sender, server, port, encryption and test email fields.
Custom SMTP screen with sender, server, port, encryption and test email fields.

Main fields

FieldMeaning
Enable custom SMTPTurns this configuration on or off.
Sender nameVisible sender name for recipients.
Sender emailEmail address used to send messages.
Default Reply-To nameName shown when recipients reply.
Default Reply-To emailMailbox where replies should arrive.
SMTP serverProvider host, such as smtp.yourdomain.com.
SMTP portConnection port, commonly 587 for TLS or 465 for SSL.
SMTP usernameAuthorized sending user, usually the full email address.
SMTP passwordPassword or app password. Leave blank to keep the current saved password.
SMTP encryptionTLS, SSL or no encryption, depending on your provider.

Recommended setup flow

  1. Ask your email provider for SMTP host, port, encryption, username and password.
  2. Enable custom SMTP.
  3. Fill in sender and Reply-To details.
  4. Save the configuration.
  5. Send a test email to a mailbox controlled by your team.

Common errors

  • Wrong password or missing app password.
  • Port and encryption mismatch.
  • Sender domain not authorized for that SMTP server.
  • Missing SPF, DKIM or DMARC records affecting deliverability.

WordPress access, Google Workspace and Reply-To

  • SMTP settings cannot restore access to wp-admin. Use the official WordPress login, password reset or contact support.
  • For Google Workspace, use smtp.gmail.com, port 587, TLS and an app password when required by Google.
  • If Reply-To does not work, save the settings, send a test message to another mailbox and inspect the From and Reply-To headers using Show original. If the header is missing, send support a copy of the headers with sensitive data removed.