Documentation / Email

Ocalt Email

Mail infrastructure for your domain, not another inbox. Unlimited addresses, IMAP/SMTP, and sending that lives in the same namespace as your files.

Open Ocalt Email

Overview

Ocalt Email provisions addresses on a domain you own, or on an ocalt.site subdomain with no DNS to configure. Every Ocalt account also comes with an address of its own from the moment it is made.

The mail lives in your namespace alongside your files, so it counts against the same storage rather than sitting in a pool somewhere. Any mail client reaches it over IMAP, POP3 and SMTP, because it is ordinary mail on an ordinary server.

What it is

Complete email infrastructure for the ecosystem, not a bolt-on inbox. You provision addresses from a namespace — hello@, support@, billing@, anything@ — on a domain you already own, or on an instant <subdomain>.ocalt.site identity.

A built-in webmail workspace sits next to IMAP/POP3, so you can use Ocalt Email as the client or as the server behind the client you already have. A programmatic sending engine handles automated and transactional mail: no-reply notices, app alerts, receipts.

What it does

  • Create as many addresses as you need and set a password on each.
  • Read and send in the built-in workspace, or in Thunderbird, Apple Mail, Outlook, or any client that speaks IMAP/SMTP.
  • Connect a domain you own (DNS) or skip DNS entirely with an ocalt.site subdomain.
  • Manage native addresses alongside existing third-party mailboxes in one interface.
  • Send from scripts with MAIL TO — attachments included.
  • DKIM signing on your own domain, so the mail looks like it came from you, because it did.

How it works

Addresses are real mailboxes on real mail infrastructure. Nothing about them is specific to Ocalt except where the storage happens to be. That is why a normal mail client works, and why a script can NEW EMAIL IMAP against the same box a human is reading.

Because mail is in the namespace, a pipeline that files invoices, extracts totals and notifies accounts does not need a second vendor's API and a second credential. The inbox is a folder the language can search.

Getting started

  1. Open email.ocalt.com. Your default username@ocalt.site identity is already there.
  2. To use a domain you own, add it and publish the DNS records as shown:
    DNS Records
     
     •  MX: Type: MX, Name: @, Value: mail.ocalt.com, Priority: 10.   
     •  SPF: Type: TXT, Name: @, Value: v=spf1 include:mail.ocalt.com ~all.   
     •  DMARC: Type: TXT, Name: _dmarc, Value: v=DMARC1; p=none; rua=mailto:you@tld.com.   
     •  DKIM: Type: TXT, Name: ocalt._domainkey, Value: A long, domain-unique v=DKIM1 string that must be retrieved by running the DOMAIN STATUS command.
    To get the full setup specifics, see this OcaltQL Page or to skip DNS, SUBDOMAIN ADD and provision from you.ocalt.site.
  3. Create hello@your-domain and set a password. Add the account to a mail client over IMAP/SMTP, or stay in the workspace.
  4. Send a test from the client, then send one from a script.
Send a message with an attachment
DOC CREATE FROM STRING ["Reminder: invoice overdue"] AS "pdf" SET ?pdf
AFTER MAIL TO "customer@example.com" SUBJECT "Invoice reminder" BODY "Attached." ATTACH ?pdf
AFTER NOTIFICATION "reminder sent"

IMAP, POP3 and SMTP

Use the hostnames and ports shown in the Email panel for the account you are connecting. Each address has its own password, independent of your Ocalt login and independent of your API key. Rotating a mailbox password does not rotate the API key, and the other way around.

Reading mail from a script

OcaltQL can connect over IMAP, search, and act. That is how an inbox becomes an operations surface rather than a place things go to die.

Watch an inbox, restart a machine
NEW EMAIL IMAP ?acc("imap_host") WITH ?pw AS ?acc("address") SET ?conn
AFTER EMAIL ?conn SEARCH "urgent" SET ?hits
AFTER FOREACH ?hits SET ?msg
OPEN
  IF ?msg("subject") CONTAINS "site down"
  OPEN
    DIRECTIVE "edge-01" EXEC "systemctl restart nginx" SET ?out
    AFTER NOTIFICATION "restarted edge-01: " & ?out("exit_code")
  CLOSE
CLOSE

Limits and plans

Mail storage counts against the same namespace storage as files. Programmatic sending is a query. Daily query allowances and storage sizes are on Pricing.

Sending reputation depends on DNS being correct. If you skip DKIM/SPF on a custom domain, expect providers to treat the mail with suspicion. ocalt.site identities are already aligned.

QueryAdminProvision addresses from the control panel.ClockWorkInvoices and customer mail in the same business namespace.OcaltQLMAIL, IMAP, and notifications as verbs.OMNIState an intent; let mail be one of the steps.

FAQ

Can I keep Gmail and add Ocalt addresses?

Yes. The workspace can sit next to third-party mailboxes. Native Ocalt addresses remain in your namespace; the third-party ones remain theirs.

Is there a sending limit besides queries?

Abuse and reputation limits apply on top of query spend. Transactional mail for your own users is the intended use. If you are building a bulk campaign product, talk to support before you find the ceiling the hard way.