Newsletters, subscribers and delivery
Configure tenant SMTP, subscribers, consent, campaigns, scheduling and delivery reporting.
Last reviewed 24 July 2026OrbitPage newsletters use the sender's own SMTP service. The workspace manages the audience and campaign workflow; the provider remains responsible for delivering the email.
Connect an address intended for legitimate campaign mail.
Paid managed plans can configure an SMTP host, port, security mode and credentials. Test the connection before collecting subscribers and use a sender domain with the DNS records recommended by the mail provider.
Credentials are server-side configuration. They are not included in the public page or exported campaign content.
Use explicit consent and a list people can leave.
The public subscription flow supports confirmation before a subscriber becomes active. Every campaign should provide a working unsubscribe path and the sender should keep the audience relevant to the reason people joined.
Import only contacts for whom the sender has an appropriate basis to communicate. OrbitPage is not a cold-email list source.
Build around one update and one primary action.
A restaurant can announce a seasonal menu; a venue can summarize the week's events; a studio can publish new availability. Subject, preview text, body and action should tell the same story.
Campaigns can be saved, scheduled, sent or deleted. Send a test to more than one mail client before addressing the full list.
Delivery signals are useful but incomplete.
OrbitPage records campaign and recipient state and can report delivery workflow, opens and tracked clicks where available. Privacy features in mail clients make open counts approximate.
Use replies, clicks and downstream actions as stronger signals than a single open percentage.
