SMTP email setup
SMTP (Simple Mail Transfer Protocol) lets OrbitPage submit outgoing email to an email provider. It is a sending connection, not a hosted mailbox or inbox. Shop can use managed OrbitPage email or your SMTP provider. Newsletter requires your SMTP provider, configured separately.
Email services
| Feature | Sending service |
|---|---|
| Shop | Use OrbitPage email or Use custom SMTP |
| Newsletter | Your SMTP provider |
Shop and Newsletter settings are separate; credentials are not copied between them. SMTP delivers messages, not a mailbox for reading replies.
Choose a provider
Use a provider that permits your intended traffic and sender address. Shop messages are transactional (purchases, delivery and appointments); newsletters are bulk marketing mail. A provider may require separate streams or credentials. A mailbox provider can also work if it supports password/app-password SMTP and your sending volume; OAuth-only SMTP authentication is not implemented.
| Provider example | Host and supported port | Credentials and setup |
|---|---|---|
| SendGrid | smtp.sendgrid.net, 587 |
Username apikey; a Mail Send API key as password; verify the sender/domain. Official SMTP guide |
| Postmark Shop | smtp.postmarkapp.com, 587 or 2525 |
Use a transactional stream's SMTP token (Access Key as username, Secret Key as password). Official SMTP guide |
| Postmark Newsletter | smtp-broadcasts.postmarkapp.com, 587 or 2525 |
Use a broadcast stream's SMTP token and an authorized sender. Official SMTP guide |
| Your mailbox/relay provider | The SMTP host supplied by that provider | Its SMTP username and password/app password; confirm that marketing mail is permitted. |
Provider requirements can change: use the linked official setup instructions. Configure the domain's SPF and DKIM records as instructed by the provider; add its recommended DMARC policy. A Reply-to address does not authorize a From address.
Connection fields
| Field | Enter |
|---|---|
| Host | SMTP hostname only, without https:// or a path |
| Port | 465 for TLS from connection start; 587 or 2525 for required STARTTLS |
| Username | Provider's SMTP login; it may differ from the sender email |
| Password | SMTP password, app password or provider SMTP/API token |
| Sender name / email | Your public name and a sender permitted by the provider |
| Reply-to | Optional monitored address for replies |
Port 25 and unencrypted delivery are not supported. Certificate checks stay enabled. Use a publicly reachable SMTP provider; OrbitPage manages the sending connection.
Shop
- Open Shop settings → Email. Choose Use OrbitPage email for managed delivery or Use custom SMTP for your own provider.
- For custom SMTP, enter the connection and sender fields, then Save.
- For custom SMTP, select Send test email. The test goes to your signed-in account. Inspect inbox and spam.
- Repeat the test after changing the connection or sender settings.
- Complete the payment, compliance and publication requirements shown in Shop before selling.
Complete Compliance, Stripe connection and the required review before publication. Configure the selected email service and test it before selling. Products and storefront design can be prepared before setup. Changing connection/sender settings clears the test status; test again. The sender handles buyer confirmations, seller notifications, questionnaire updates, booking changes and reminders. Purchase access remains available through the verified receipt if an email is delayed. See Shop.
Saved custom settings are used immediately. OrbitPage does not silently fall back to managed email when your SMTP fails. Select Use OrbitPage email and save to return to managed sending. Email failure does not undo a confirmed purchase.
Newsletter
- Open Newsletter → Settings and enter a separate SMTP configuration.
- Complete sender identity, postal/legal details, Privacy and Terms URLs.
- Save, then Verify and send test; the test goes to your signed-in account.
- Confirm receipt before sending or scheduling a campaign.
Newsletter always requires your SMTP and a successful test. Shop credentials are not reused automatically. Marketing consent and unsubscribe handling remain required. See Newsletters.
Keep settings recoverable
Passwords are encrypted and never returned to the browser. A blank password does not clear an existing password. Enter the password again when changing the SMTP provider or login, then repeat the test. OrbitPage manages encryption and public URLs. Keep access to your SMTP provider so you can replace or revoke credentials when needed. Check customer, confirmation and unsubscribe links after a public-address change.
Shop and Newsletter block private/reserved SMTP destinations. Use your provider's public TLS endpoint.
Troubleshooting
| Failure | Check |
|---|---|
| Connection timeout | Provider hostname, supported port and public availability; contact support if the connection still fails |
| Authentication rejected | SMTP credentials/app password and enabled SMTP access |
| Sender rejected | Verified sender/domain, From address and provider permissions |
| Test accepted but not received | Spam, provider delivery logs, bounce/suppression list and domain DNS |
| Saved settings unavailable | Re-enter and test provider credentials; contact support if the error persists |
A successful test proves provider acceptance, not guaranteed inbox delivery. Never share SMTP credentials, signed customer links or private buyer details in a public support request.
