Reference
Limits, DNS & architecture
A quick reference for the technical details — connection settings, DNS records, plan limits — plus a short internal overview for the SyncGaze team.
Mail client settings
| Protocol | Server | Port | Security |
|---|---|---|---|
| IMAP (incoming) | imap.syncgaze.in | 993 | SSL / TLS |
| SMTP (outgoing) | smtp.syncgaze.in | 587 | STARTTLS |
| POP (incoming) | pop.syncgaze.in | 995 | SSL / TLS |
Username = your full email address; password = your mailbox password. IMAP/SMTP is available on business plans (webmail only on free). Full walkthrough: Connect Outlook / Thunderbird.
DNS records
| Record | Host | Value | Notes |
|---|---|---|---|
| MX | @ | mail.syncgaze.in (priority 10) | The only MX on the domain. |
| SPF (TXT) | @ | v=spf1 include:syncgaze.in ~all | One SPF record only. |
| DKIM (TXT) | dkim._domainkey | Provided per domain | Configured automatically on our side. |
| DMARC (TXT) | _dmarc | v=DMARC1; p=none; | Optional; tighten later. |
Changes take 5–30 minutes to propagate. Verification requires the SyncGaze MX and no conflicting MX at equal/higher priority — see the multiple-MX fix.
Plan limits (guide)
| Plan | Storage / mailbox | External clients |
|---|---|---|
| Free (personal) | Generous, single mailbox | Webmail only |
| Starter | 5 GB | Webmail |
| Business | 30 GB | IMAP / SMTP |
| Enterprise | 100 GB | IMAP / SMTP + retention, delegation |
Exact limits, sending rates and features are shown on the live plan picker and in Billing. Your account may differ on a custom/partner plan.
For the SyncGaze team
A short orientation for internal support and engineering. (Customer-facing readers can stop here.)
- One identity, every app.
auth.syncgaze.inissues a JWT in a.syncgaze.incookie; every subdomain validates it locally with the shared secret — no re-login between apps. This Help Center decodes the same cookie read-only for its header. - Mail delivery. Inbound: Postfix → a pipe transport →
mail-ingest.pystores messages in MongoDB (spam-scored, filtered, quarantined). Recipient/alias resolution and SMTP auth are custom services reading the same MongoDB. Webmail reads MongoDB directly. - Domain verification. A domain is “verified” only when its MX points to SyncGaze and no other MX sits at equal/higher priority; that flag is what makes Postfix accept its mail.
- Where things live. Core (auth, tenants, domains, mailboxes, billing) at
dashboard/account/auth/admin; Mail atmail; the workspace apps each on their own subdomain and database.
What's next?