SMTP email setup

Email in SaaS and OSS

SaaS Shop offers Use OrbitPage email through our managed mail service, or Use custom SMTP through your own provider. The same choice handles purchase confirmations, seller notifications, questionnaires, booking changes and reminders.

Newsletter always requires your own SMTP in both editions. OSS provides no email hosting or managed OrbitPage sender: Shop also requires your SMTP. Shop and Newsletter settings are separate; credentials are not copied between them.

Choose and authorize a provider

Choose a provider that supports password or app-password SMTP and permits your traffic. Shop email is transactional; newsletters are marketing mail. Separate credentials or message streams may be required. A mailbox provider may work if SMTP authentication and your sending volume are supported; OAuth-only SMTP is not implemented.

Verify your sending address or domain and add the provider's SPF, DKIM and recommended DMARC records. The From address must be authorized; Reply-to does not grant that authorization.

Enter the SMTP fields

Enter the host as a hostname without https:// or a path. Use port 465 for TLS from connection start, or 587/2525 with mandatory STARTTLS. Port 25 and unencrypted sending are unsupported. Keep certificate verification enabled.

Enter the SMTP username and password/app password supplied by your provider; these can differ from your mailbox login. Set a public sender name and permitted sender email, with an optional monitored Reply-to. SaaS and OSS Newsletter block private/reserved network destinations. OSS Shop administrators may use a private SMTP relay.

Passwords are encrypted and never returned. Leave the password blank only to keep it for the same host, port and username; connection changes require re-entry. Changing connection/sender settings clears test status. OSS administrators must keep their server encryption secret stable and back up their database.

Set up Shop email

Custom settings are used immediately after Save. OrbitPage does not silently switch back to managed email when your SMTP fails. In SaaS, select Use OrbitPage email and Save to return to managed sending. Email failure does not undo a confirmed purchase; customers can use the verified receipt.

1. For SaaS managed sending, select Use OrbitPage email and Save.
2. For your own sender, choose Use custom SMTP in SaaS; OSS uses SMTP only. Enter connection and sender fields, then Save.
3. Select Send test email. SaaS sends to your signed-in account; OSS sends to the configured sender address.
4. Check inbox, spam and provider delivery logs before selling. OSS requires completed Compliance, verified Stripe/webhook and a successful SMTP test before publishing or accepting payments. Products and storefront design can be prepared first.

Set up Newsletter email

Newsletter uses its own SMTP settings in both editions.

1. Enter your own SMTP, sender identity, postal/legal details and public Privacy and Terms URLs.
2. Save settings, then Verify and send test. The test goes to the Newsletter sender email.
3. Confirm receipt before sending or scheduling campaigns. A successful test is required; Shop email settings do not configure Newsletter.

Resolve sending failures

A successful test confirms provider acceptance, not guaranteed inbox delivery. Never post SMTP credentials, signed customer links or private buyer details in a public support request.