System requirements
This page separates configured build settings from validated environments. It does not publish disk, RAM, or per-message size estimates, and it does not invent a tested OS matrix.
Configured build targets
Section titled “Configured build targets”From primail-tauri/src-tauri/tauri.conf.json:
- macOS minimum: 11.0. The app bundle also lists desktop packaging targets used for local/internal builds.
- iOS minimum: 15.0 on the iOS bundle record. iOS is future work, not a shipping product.
- Linux / Windows: deb, rpm, AppImage, MSI, and NSIS targets exist in that same bundle list. They are source targets.
A configured minimum is not proof that every supported OS version or CPU has been tested.
Validated environments
Section titled “Validated environments”Internal verification to date is a signed macOS desktop build used for development and testing. That receipt does not establish:
- a public App Store listing
- universal binaries or a published size requirement
- Linux or Windows native credential/integration acceptance
- iOS, iPad, or Android device acceptance
Linux and Windows native credential persistence is still open. Playwright’s mocked Chromium suite is available in the repository and is not native WebKit or platform evidence.
Mail and network
Section titled “Mail and network”New network mail needs outbound connectivity to your mail provider, not to a Primail cloud account:
- IMAP uses port 993 with implicit TLS. Plaintext is not supported.
- SMTP uses port 465 with implicit TLS. STARTTLS is not supported.
Cached and local work — reading already-fetched mail, local search, drafts on disk — does not require a Primail cloud account or a deployed sync service. Optional iCloud configuration sync is accepted direction only and is not implemented public functionality.
Restrictive networks that block those mail ports can prevent new fetch or send. If a network operator asks for the ports, see Advanced IMAP / SMTP settings.
Related pages
Section titled “Related pages”- Availability — no public download or store listing.
- Automation interfaces — CLI and MCP instead of a local mail REST listener.
- Mail and configuration sync — provider IMAP versus unavailable Primail Cloud identity.