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 callThe return path matters. Bring available bounces, complaints and unsubscribes back to the suppression and review process.
For teams using an approved SMTP service, multiple sending accounts or their own mail servers.
SMTP settings, supported provider API or sending-server configuration
Domain, subdomain, DKIM and return-path design
Traffic categories, schedules and route selection
Bounce, complaint and unsubscribe event integration
Provider terms, permissions and account isolation
Email Engine is founder-owned software used through Sky's managed services. Standalone self-service access is not currently offered. Your engagement defines the setup, operating responsibilities and support—not an independent software subscription.
Use an approved SMTP connection or supported provider interface, agreed sending controls and the return events available for that route. The connection method and event coverage are confirmed per account; catalog entries do not all provide the same functions.
Sky's team implements the agreed connection, verifies the available feedback path and manages approved delivery changes. You retain your audience and domain ownership, sending permissions and approval rights.
Technical connections and commercial relationships are separate. Any partner or reseller arrangement relevant to your proposal must be identified explicitly; a logo or catalog entry alone establishes neither. Provider accounts, fees and IP capacity are not included by default.
Sky's in-house team can implement authentication and sending-configuration changes, not just recommend them. The work depends on your requirements, system access and approval. Each change belongs to a defined implementation scope.
Required provider changes, external certificate fees and follow-up coverage are agreed separately. Google's BIMI requirements differ from Yahoo's BIMI policy.
Need a diagnosis before changing settings?Map SMTP authentication or a supported API, sending identity, account permissions and traffic separation.
Set up the agreed campaign schedule, routing controls and return-event paths through Email Engine.
Validate authentication, provider acceptance, bounce/complaint intake and suppression before scaling live traffic.
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.
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.
Ownership of its lists, domains and provider accounts, plus any required provider approval and usage fees.
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