Email ingestion
Connect a mailbox and Lucius can search it for receipts, statements, and transaction confirmations, on request or via an Automation. This connection is strictly read-only — nothing about it can change your mailbox.
What it does
Set your IMAP host, username, password, and folder (default: inbox) in the connector settings. Lucius can then:
- Search headers — subject, sender, date — without pulling any message body yet.
- Fetch specific messages once headers narrow down which matter, so a broad search doesn’t mean downloading your whole mailbox.
Only the plain-text (or HTML-stripped) body is read — attachments are never opened. A body is capped before reaching the AI model, so one huge email can’t blow a turn’s budget.
What it never does
Read-only at the protocol level, not just by convention — nothing here can mark a message read, move it, flag it, or delete it. No background poller either: a search runs only when you ask, or an Automation you configured runs one on its own schedule.
Sending mail is a separate feature, with its own confirmation and SMTP credentials — reading your inbox and sending mail as you are two different connections; having one never enables the other.
Where your password is stored
Stored on this machine, never sent to Lucius or included in an export. The field is write-only at a glance, but you (the logged-in operator) can reveal it to confirm what’s saved — logged, and the only way it’s ever shown to anyone. Excluded from a sanitised backup like every other connector credential; see Backup and restore.
Related pages
connectors/telegram— the other place Lucius can be reachedoperations/security-and-privacy— where every credential lives