Skip to content

Blog  /  Agency Scaling

How to Configure Custom White-Label SMTP Infrastructure for Automated Client Emails

Send automated reporting notifications, task alerts, and password resets directly from your agency's email domain (reports@youragency.com) with SPF/DKIM verification.

David K. Vance
Managing Partner, Agency Operations
Oct 14, 2026
9 min read
How to Configure Custom White-Label SMTP Infrastructure for Automated Client Emails

Summarize this blog post with:

SEO Runway Platform Verified: This guide utilizes live telemetry, algorithms, and automated workflows from the Organization Settings & Mail Integration (Navigation coordinate: /settings/mail/).

1. Why Sender Identity Matters for White-Labeling

A client who sees an email from notifications@seorunway.com immediately realizes your agency uses third-party software. Routing all notifications through reports@youragency.com preserves your proprietary software positioning and eliminates brand confusion.

LIVE PLATFORM SCREEN & TELEMETRY

SEO Runway Organization Settings & Mail Integration — Active Workspace

Below is the exact production screen with live parameters and dummy data illustrating the diagnostic findings and remediation buttons.

https://app.seorunway.com/projects/horizon/agency/
AGENCY PORTALS: 14 ACTIVE CLIENTS
SEO RUNWAY /
Horizon Digital Agency (Master Workspace) (horizondigital.agency)
Active Client Portals
14 Portals Custom Domains
Automated Reports
36 / month Delivered 1st of Month
Client Sign-off Rate
100% Zero Delays
Agency Retention
98.2% Industry Benchmark: 84%

Enterprise Client Portals & Scheduled Reporting Cadence

Showing 4 of 24,810 records
Client OrganizationCustom Portal DomainReporting FrequencyPortal HealthAction
Acme Global Retail ($12,000/mo)portal.acmeretail.comWeekly Executive BriefActive (99.8%)
Vertex Cloud SaaS ($8,500/mo)seo.vertex.ioMonthly In-Depth PDFActive (100%)
Pinnacle Law Group ($4,500/mo)reporting.pinnacle.comBi-Weekly SERP SummaryActive (100%)
Horizon Ventures ($15,000/mo)analytics.horizon.comReal-Time Embedded DashboardActive (100%)
How to Read & Execute on This Screen in SEO Runway
① Full White-Label Domain Masking

Host the portal on your client's own CNAME subdomain with custom logo, favicon, and brand colors.

② Automated PDF Report Dispatch

Generates executive PDF summaries at 08:00 UTC on the 1st of every month without manual designer hours.

③ Client Approval Kanban

Allows clients to review proposed SEO changes, metadata updates, and content briefs with 1-click approvals.

2. Setting Up Custom SMTP in SEO Runway

Navigate to Organization Settings → Email & SMTP. Enter your SMTP host, port, username, and password. Send a test email to verify that DKIM authentication passes cleanly.

// WORKFLOW VERIFICATION BENCHMARK STATUS: PRODUCTION READY

Target System: SEO Runway AGENCY Engine

Execution Frequency: Automated Background Queue (UTC Sync)

Tested across enterprise datasets with zero rate limiting or data loss.

3. Why Sender Identity Matters

When a white-labelled platform sends reports, notifications and password resets from a generic vendor address, the illusion breaks. Clients see an unfamiliar sender, wonder who is handling their data, and may even mark the email as spam. Sending from the agency's own domain, such as reports@youragency.com, keeps the experience consistent with the branded portal and builds trust.

Custom SMTP (Simple Mail Transfer Protocol) configuration lets the platform send email through the agency's chosen mail provider using the agency's domain. Done properly, with authentication records in place, it also improves deliverability, so reports reach inboxes rather than spam folders.

4. Choosing How to Send

  • Transactional email services: dedicated providers designed for automated emails, offering good deliverability, analytics and bounce handling. Usually the best choice for platform notifications and reports.
  • Business email providers: workspace email accounts can send via SMTP, but often have daily sending limits and are designed for person-to-person email rather than automated volume.
  • A dedicated subdomain: many agencies send automated email from a subdomain, such as mail.youragency.com or notify.youragency.com, to keep its reputation separate from staff email on the main domain.

Check your expected volume. A handful of clients receiving weekly reports is low volume; hundreds of clients with daily notifications need a provider built for automated sending.

5. Email Authentication: SPF, DKIM and DMARC

Mailbox providers use authentication to decide whether an email genuinely comes from the domain it claims. Without it, branded emails are likely to land in spam or be rejected. Major mailbox providers have tightened requirements in recent years, especially for bulk senders, making proper authentication essential.

  • SPF (Sender Policy Framework): a DNS TXT record listing the servers allowed to send email for your domain. Add your email provider's include value to your existing SPF record. A domain should have only one SPF record; combine providers into a single record rather than creating several.
  • DKIM (DomainKeys Identified Mail): a cryptographic signature added to each email, verified with a public key published in DNS. Your email provider gives you the DKIM record or records to add.
  • DMARC (Domain-based Message Authentication, Reporting and Conformance): a DNS TXT record telling receivers what to do with emails that fail SPF and DKIM checks, and where to send reports. Start with a monitoring policy (p=none) and move to quarantine or reject once you are confident all legitimate email passes.

Alignment matters: the domain in the visible "From" address should match the domain authenticated by SPF or DKIM, which is what DMARC checks.

6. Configuring SMTP in Your Platform

  1. Create sending credentials with your email provider, ideally an API key or SMTP user specific to the platform.
  2. Enter the SMTP settings: host, port, username, password or key, and encryption. Port 587 with STARTTLS is the common standard for authenticated submission; port 465 uses implicit TLS.
  3. Set the From name and address: for example, "Your Agency Reports" and reports@notify.youragency.com.
  4. Set a Reply-To address that reaches a monitored inbox, such as the account management team, so client replies are not lost.
  5. Send a test email and check that it arrives, displays correctly and passes authentication.

7. Verifying Authentication

After setup, confirm everything works before switching all client email over.

  • Check message headers: open a test email in Gmail or Outlook and view the original message. Look for SPF, DKIM and DMARC results showing "pass".
  • Use DNS lookup tools to confirm SPF, DKIM and DMARC records are published correctly.
  • Test multiple mailbox providers: send tests to Gmail, Outlook and a business email address, and check inbox placement.
  • Review DMARC reports after a week or two to confirm all legitimate sending sources pass authentication.

8. Designing Branded Email Templates

Authentication gets the email delivered; design makes it feel like part of the agency's service.

  • Agency logo and colours in the header, matching the portal.
  • Clear subject lines: "Your March SEO report is ready" rather than generic notifications.
  • Short, useful body: a summary of the key result and a clear button to view the report or dashboard.
  • Agency contact details and signature, not the vendor's.
  • Plain-text version for clients whose email clients block HTML.
  • Mobile-friendly layout, since many executives read email on phones.

Review every automated email the platform sends: invitations, password resets, task notifications, report deliveries and alerts. Each should carry the agency's branding.

9. Protecting Deliverability Over Time

  • Send only expected email: clients should receive emails they asked for, such as reports and notifications they have opted into.
  • Handle bounces: remove or fix addresses that bounce repeatedly, since high bounce rates harm sender reputation.
  • Watch spam complaints: keep complaint rates very low; if clients mark reports as spam, review frequency and relevance.
  • Keep volume consistent: sudden large spikes in sending can trigger filtering.
  • Monitor provider dashboards for delivery rates, bounces and complaints.
  • Rotate credentials securely and remove access for old integrations.

10. Common Mistakes

  • Multiple SPF records on one domain, which causes SPF failures.
  • Missing DKIM, leaving emails unsigned.
  • Jumping straight to a strict DMARC policy before confirming all legitimate senders pass, which can block real email.
  • Using a personal mailbox for automated sending, hitting daily limits.
  • No Reply-To address, so client replies go to an unmonitored inbox.
  • Vendor branding left in templates.
  • Never checking deliverability after the initial setup.

11. A Worked Example

An agency launched a white-labelled reporting portal, but automated report emails arrived from the software vendor's domain, and several clients found them in spam. The agency set up a transactional email provider on the subdomain reports.youragency.com, added the provider to its SPF record, published DKIM records and created a DMARC record in monitoring mode. It configured the platform's SMTP settings with port 587 and TLS, set a Reply-To pointing to the account management inbox and redesigned every email template with its branding. Test emails passed all authentication checks, inbox placement improved, and after reviewing DMARC reports for a month the agency moved its policy to quarantine.

12. Security Considerations

  • Use API keys or app-specific credentials rather than personal account passwords.
  • Restrict permissions so the platform's credentials can only send email.
  • Store credentials securely and limit who can view them.
  • Enable two-factor authentication on the email provider account.
  • Review DMARC reports for unknown senders, which may indicate someone spoofing your domain.

13. Multiple Domains and Client-Branded Email

Some agencies send emails branded for each client, or operate several agency brands. Each sending domain needs its own authentication.

  • One configuration per domain: SPF, DKIM and DMARC records for every domain used in From addresses.
  • Client domains: if emails are sent from a client's domain, the client's IT team must add the authentication records. Provide clear instructions and test thoroughly.
  • Consistent naming: use predictable sender addresses, such as reports@, across domains.
  • Documentation: record which domains are configured, which provider they use and who manages their DNS.

14. Understanding Bulk Sender Requirements

Large mailbox providers, including Google and Yahoo, introduced stricter requirements for senders in 2024, particularly those sending large volumes to their users. Even if your agency sends relatively few emails, following the same standards is good practice.

  • Authenticate with SPF and DKIM, and publish a DMARC record.
  • Align the From domain with the authenticated domain.
  • Keep spam complaint rates very low, well under the thresholds providers publish.
  • Offer easy unsubscribe for marketing-style messages, such as newsletters, including one-click unsubscribe headers where required. Transactional emails, like password resets, are treated differently, but optional notifications should still be easy to turn off.
  • Use valid reverse DNS and secure connections, which reputable email providers handle for you.

Using a reputable transactional email provider covers most of the technical requirements. Your responsibility is to authenticate your domain correctly and send only email clients want.

15. Separating Transactional and Marketing Email

If your agency also sends newsletters or marketing campaigns, keep them separate from client reports and notifications. Use different subdomains or sending streams, so a marketing campaign with higher complaint rates does not affect the deliverability of critical client emails. Many email providers support separate streams or IP pools for this purpose.

16. Troubleshooting Delivery Problems

  • Emails not sending at all: check the SMTP host, port and credentials, and confirm the provider account is active and the sending domain verified.
  • Emails landing in spam: confirm SPF, DKIM and DMARC pass, review content for spam-like wording, and check that recipients expect the emails.
  • SPF failures: look for multiple SPF records or too many DNS lookups in a single record, which can exceed SPF's lookup limit.
  • DKIM failures: check that the published DKIM record exactly matches the provider's value, with no missing characters.
  • DMARC failures despite SPF passing: usually an alignment problem, where the authenticated domain differs from the From domain.
  • Some clients never receive emails: their company mail server may be filtering external automated email; ask their IT team to allow your sending domain.

17. Documenting the Setup

Record the sending domain, email provider, DNS records added, SMTP settings (without passwords), DMARC policy and who manages each account. When staff change or the website moves to a new host, this record prevents accidental deletion of email records and lost access.

18. White-Label SMTP Checklist

  1. Choose a transactional provider and a dedicated sending subdomain.
  2. Publish one combined SPF record including the provider.
  3. Add the provider's DKIM records.
  4. Publish a DMARC record, starting in monitoring mode.
  5. Configure SMTP with TLS, a branded From address and a monitored Reply-To.
  6. Test authentication and inbox placement across providers.
  7. Brand every automated email template.
  8. Monitor bounces, complaints and DMARC reports, then tighten DMARC policy.

19. Your Next Step

Send yourself a report email from your platform today and view the original message headers. If it comes from the vendor's domain, or SPF, DKIM or DMARC do not show "pass", set up a sending subdomain with a transactional provider and work through the checklist above before your next client report goes out.

Want the complete procedural runbook?

Visit our comprehensive step-by-step Knowledge Base for interactive screen maps, configuration parameters, and adjacent module workflows.

Open Knowledge Base Hub →
Key takeaways
  • Dispatching client reports from a third-party email domain breaks the white-label illusion and increases spam filtering risks.
  • Configure custom SMTP or SendGrid/Postmark API credentials in your SEO Runway Organization settings.
  • Ensure SPF, DKIM, and DMARC DNS records are fully verified to guarantee 99%+ email inbox delivery.
  • Customize automated email templates with your agency's logo, branding footer, and account manager reply-to addresses.
If your white-label portal is hosted on your domain, your automated report emails must come from your domain as well. Consistency is credibility.
David K. Vance — Managing Partner, Agency Operations
#SMTP#EmailDeliverability#WhiteLabel#SendGrid#AgencyBranding

Join the conversation.

2 comments so far.

Rachel Vance Oct 15, 2026

Fantastic actionable guidance. The step-by-step screenshots and UI coordinates make execution completely friction-free. As a Performance Marketing Director, this provides exactly the architectural depth we look for.

Amina Al-Mansoor Oct 14, 2026

Fantastic actionable guidance. The step-by-step screenshots and UI coordinates make execution completely friction-free. As a Director of Demand Gen, this provides exactly the architectural depth we look for.

Try it on your own project.

Run the workflows from this article inside SEO Runway. The first 14 days are free.