FAQ¶

Pelton supports standard IMAP and SMTP, which covers the vast majority of providers out of the box, see Setting up a mailbox. Gmail, iCloud, Outlook, Yahoo, Fastmail, and Purelymail all get a dedicated setup flow on top of that. Because Pelton is FOSS, the community can add support for more providers too.

Yes. You can configure Pelton to cache your newest emails locally (you choose the timeframe), and you can explicitly mark specific emails to be kept offline permanently.

Yes. See Encryption keys.

Your data stays entirely in your control. It's stored in a local SQLite database on your machine, and on your original email provider's server. Pelton doesn't host or route your data through any third-party servers.

Speed and memory efficiency. Go and Wails use significantly less RAM than heavy Electron wrappers, while still giving a snappy, cross-platform UI.

This is entirely configurable. By default, remote images and tracking pixels are blocked (similar to Thunderbird). A banner appears letting you know images were blocked, and you can choose to load them for that email if you want to.

Pointing Pelton's SQLite database at a custom path (like a network share) isn't recommended or fully tested yet, but it's planned.

No. Pelton has zero telemetry. If you hit a crash or a bug, please help out by opening an issue yourself, Pelton won't report it for you.