api

Package analytics collects page views without cookies or stored addresses and keeps them in a Store.

Package lists holds the third-party lists analytics matches against, as fetched by update.go: crawler user agents, referrer spam domains, and search engines, social networks and AI assistants by host.

Package apppush sends notifications to iOS apps through APNs (token-based authentication) and to Android apps through Firebase Cloud Messaging (HTTP v1 with a service account).

Package awsses calls the few Amazon SES v2 and STS operations Yuva needs to manage SES tenants, signed with minio-go's Signature Version 4 signer.

Package cfsaas manages Cloudflare for SaaS custom hostnames of one zone through the Cloudflare API (https://developers.cloudflare.com/api/resources/custom_hostnames/).

Package cfsaastest is a fake of the Cloudflare custom hostnames API for tests, answering in the documented shapes (https://developers.cloudflare.com/api/resources/custom_hostnames/).

Package csvimport reads subscriber files as spreadsheets export them: it finds the text encoding and the column separator and splits the rows per RFC 4180.

Package reply finds the new text of an e-mail reply: it drops the quoted history that mail clients append or prepend and the signature below the delimiter or a "sent from" line.

Package gallery serves the starter e-mail designs of templates/email (MIT), copied into data by go generate.

Command copy mirrors templates/email into the gallery's embedded data: go:embed cannot reach outside the api module.

Package issues talks to GitHub (REST, with a fine-grained personal access token) and Linear (GraphQL, with a personal API key): it checks a token, reads, finds and creates issues, maps an issue's state to a feedback progress and checks the signatures of their webhooks.

Package design reads, checks and renders e-mail design documents (EmailDesignDocument in the contract) to table HTML with inline styles and a plain-text part.

Package images turns an uploaded picture into what e-mail designs serve: a PNG, JPEG or GIF without metadata, at most 1,200 pixels wide.

Package style holds what the server's own mails (mail's layout.html) and e-mail designs (mail/design) draw alike: colour contrast, font stacks, the button and the Outlook wrappers.

Package migrate holds what moving a mailbox into Yuva needs before any mail is read: the provider presets, detection from an address, the address checks for the connection, and the connection test.

Package fileread reads the export files a team uploads to move its mail to Yuva: a Google Takeout mbox, any mbox, and zips of .eml files, of a Maildir or of mbox files.

Package helpdesk reads the help desks of its registry (Desks) over their APIs, only ever with GET: every data request goes through a transport that refuses any other method, and the one POST Yuva sends, the OAuth token exchange, goes through a client that reaches the token endpoint and nothing else.

Package helpdesktest serves recorded Zendesk, Help Scout, Chatwoot and Front answers from a local TLS server for tests: every request is recorded, the API refuses a missing or stale token, and the rate-limit headers are the ones the providers document.

Package imapread reads a source mailbox over IMAP and can do nothing else.

Package microsoft signs a mailbox in with the Microsoft identity platform only to obtain a token for IMAP: the authorization-code flow with PKCE asks for IMAP.AccessAsUser.All and offline_access and nothing else, and the one client that sends anything to Microsoft may only POST to the tenant's token endpoint.

Package microsofttest imitates the Microsoft identity platform for tests: the authorize and token endpoints of login.microsoftonline.com over TLS (codes bound to PKCE, refresh tokens, the errors Microsoft answers), and a token introspection endpoint over plain HTTP that an IMAP server such as Dovecot asks whether a token is valid and whose it is.

Package oas provides primitives to interact with the openapi HTTP API.

Package push sends Web Push messages (RFC 8030) encrypted per RFC 8291 and signed with VAPID (RFC 8292).

Package slack talks to Slack's Web API at slack.com and checks the signatures of its event requests.

Package telemetry exports OpenTelemetry traces over OTLP.

Package webhook signs and sends webhooks per the Standard Webhooks specification (https://www.standardwebhooks.com) and refuses to send them into private networks.