Frequently asked questions

Plain text and common attachment types. The per-message attachment count and total size limits are configured at runtime (admin-adjustable); exceeding them shows a friendly prompt at compose time — nothing is silently dropped.

Go to Website sending / Domains, add your domain, and you’ll get SPF, DKIM, DMARC and a verify TXT record. Add them at your DNS provider, verify in one click, and the domain is ready.

Yes — Inbox / Sent / Drafts / Trash, with compose (cc / bcc / attachments), search and bulk actions, matching Gmail-style interaction.

Generate a key under Website sending; it starts with te_live_. The plaintext is shown only once at creation — afterwards only the prefix is visible (stored encrypted). Save it then; if lost, revoke and recreate.

Yes — recipients per message, sending rate, and attachment count/size all have caps, admin-configurable at runtime. Exceeding the rate returns 429 with retry_after; just retry later as indicated.

No. There’s automatic fallback: failed sends are retried, and expired/orphan resources are swept by a periodic self-heal — aiming to lose no mail and leave no half-done tasks.

No. Your Sent copy keeps the full recipient list (visible to you), but each recipient’s delivered copy has BCC blanked out — recipients can’t see the bcc’d addresses.

No. Soft-deleted or banned accounts are invalidated immediately (checked every request): no re-login or renewal, and new mail is no longer delivered to that address.

Binding your own domain and configuring SPF / DKIM / DMARC, then passing the one-click verification, is the most effective way. See Deliverability for details.