Create your organization.
Register as a business or MSP. MSPs can add client organizations and assign access.
Incoming mail passes through SpamScan before continuing to your mail service. Your team gets control over the messages that need attention.
Follow the setupMail for a verified domain reaches SpamScan. Recipient checks keep the gateway focused on valid addresses.
Sender, content, links, attachments, and AI review contribute to the message decision.
Your organization’s policy determines whether mail moves on, receives a tag, or needs further review.
Approved mail continues to your destination. Held mail stays reviewable; temporary delivery failures need retries.
No mailbox connector is required for the gateway approach. Mail must be routed through SpamScan for it to be inspected.
Register as a business or MSP. MSPs can add client organizations and assign access.
Add the provided DNS TXT record. Ownership verification comes before domain activation.
Add the delivery destination and valid recipients. Connection, routing, and secure delivery checks come before cutover.
Review default protection, quarantine behavior, and role permissions. Select premium review when available and appropriate.
Point incoming mail to the supplied gateway records. Follow migration and rollback instructions; keep the original destination available.
Check message traces, quarantine, delivery health, and false positives before broad rollout.
SpamScan is being built as an incoming mail checkpoint. It does not replace your mailbox provider.
Internal mail that never reaches the gateway is outside this inspection flow. Delivered messages cannot be recalled through gateway routing alone.
These steps describe the planned onboarding experience. Public registration and customer mail processing are not open yet.