Connect via IMAP
Connect any email provider with IMAP. Your password is encrypted at rest in Supabase Vault.
Connect via IMAP
Admin+IMAP connects any provider that Inbox Ledger does not support through OAuth. That covers Fastmail, Zoho, iCloud, Yandex, GMX, IONOS, hosted Exchange, and most on-premise mail servers. You give Inbox Ledger your email address and password, and it handles the server settings for the common providers automatically.
Your password is stored encrypted in Supabase Vault, the server-side secret store. The plaintext password never touches the regular database tables or your browser. It is decrypted server-side only when a sync worker needs to open the connection to your mail server.
What you'll need
The admin or owner role, your email address, and the password for that mailbox. If your provider uses two-factor authentication, you need an app password instead of your normal password (see the warning below).
Connect your mailbox
Open Sources and start an IMAP source
In the dashboard sidebar, open Sources, click Add Source, and choose IMAP.
Name the source and pick your provider
Give it a name like "Company Inbox", then choose your Email Provider from the dropdown. Inbox Ledger fills in the server and port for you.
Enter your email and password
Type the email address and password for the mailbox. If your provider needs an app password, a setup card with a link appears under the dropdown.
Test the connection
Click Test Connection. Inbox Ledger opens an IMAP session and verifies your credentials before saving anything.
Add the source
Click Add Source. Your password is encrypted and stored, and auto-sync starts within 60 minutes.

If your provider is a custom or self-hosted server, tick Advanced settings to enter the IMAP server, port, username, and folders by hand.
Use an app password if you have two-factor authentication
If two-factor authentication is on, your provider's IMAP server rejects your normal account password. Generate an app password in your provider's security settings and paste that into the Password field instead. Gmail, iCloud, Yahoo, Fastmail, and Zoho all require this.
Confirm it worked
After Test Connection reports success and you click Add Source, the mailbox appears in the source list. Open Documents after the first sync runs to see captured invoices. To pull in older invoices, run Find Past Invoices on the Retroactive Scan page.
Reference
Common provider settings
Most of these are detected automatically when you pick the provider from the dropdown. Use this table only when you connect a custom server through Advanced settings.
| Provider | Host | Port | Encryption | Notes |
|---|---|---|---|---|
| Gmail | imap.gmail.com | 993 | SSL/TLS | App password required when 2FA is on. |
| iCloud | imap.mail.me.com | 993 | SSL/TLS | App password always required. |
| Fastmail | imap.fastmail.com | 993 | SSL/TLS | Generate an app password in Fastmail settings. |
| Yahoo | imap.mail.yahoo.com | 993 | SSL/TLS | App password required. |
| Zoho | imap.zoho.com | 993 | SSL/TLS | Enable IMAP in Zoho settings first. |
| Yandex | imap.yandex.com | 993 | SSL/TLS | Enable IMAP in Yandex settings. |
Domain restrictions
Inbox Ledger supports yandex.com but does not accept .ru hosts.
That rules out imap.mail.ru, imap.yandex.ru, and any other .ru mail server.
A connection to a .ru host is rejected.
Related
Forwarding addresses
An alternative when IMAP is not an option.
Email not syncing
Diagnose stuck or delayed IMAP syncs.
Ready to try this?
Inbox Ledger turns your inbox into clean accounting data. The free tier includes 10 credits, refilled every 30 days.
Start free