Connect the approved route
Map SMTP authentication or a supported API, sending identity, account permissions and traffic separation.
← ALL CAPABILITIES
02 / CONNECT
Connect your sending account. See what happens next.
Bring your approved SMTP service or sending server into one campaign and delivery workflow. Sky uses Email Engine to set up schedules, route messages and bring available bounces and complaints back into the process.
Book a discovery callSKY / DELIVERY PRACTICE02 / ROUTE TOPOLOGY
One control point. Your approved route.
CAMPAIGN CONTROLEmail EngineAudience, schedule, sending identity and route selection
PATH 01Approved SMTPYour authenticated sending service
PATH 02Supported APIProvider-specific sending connection
PATH 03Your mail serversDedicated route you control
The return path matters. Bring available bounces, complaints and unsubscribes back to the suppression and review process.
01WHEN THIS HELPS
For teams using an approved SMTP service, multiple sending accounts or their own mail servers.
02EVIDENCE & INPUTS
Read the evidence
across layers.
01
SMTP settings, supported provider API or sending-server configuration
02
Domain, subdomain, DKIM and return-path design
03
Traffic categories, schedules and route selection
04
Bounce, complaint and unsubscribe event integration
05
Provider terms, permissions and account isolation
03THE WORKFLOW
What happens after
we start looking.
Coordinate the sends
Set up the agreed campaign schedule, routing controls and return-event paths through Email Engine.
Test the full loop
Validate authentication, provider acceptance, bounce/complaint intake and suppression before scaling live traffic.
04A CLEAR WORKING BOUNDARY
We know which part
belongs to whom.
What we need
Your chosen provider's approved account, SMTP or API capabilities, traffic categories, domain ownership and event access. Do not share passwords through the enquiry form.
What we do
Configure the approved SMTP account, supported provider API or sending-server route, plus campaign controls and available bounce-to-suppression steps within the agreed scope.
What you retain
Ownership of its lists, domains and provider accounts, plus any required provider approval and usage fees.
05WHAT YOU LEAVE WITH
A next step you can act on.
An integration plan and validated connection or implementation milestones, as agreed. Provider accounts and sending capacity are not included by default.
See this engagement scope