IMAP email source
Overview
A client can send scanned photos by email and Tower protects each attachment the same way it polls an FTP directory.
How it works
One IMAP connector (imapflow + mailparser). The mailbox is polled on the hourly discover and on demand from the source page. Each matching attachment becomes a task. The last IMAP UID is the cursor, stored like the FTP last-trigger timestamp.
Key files
src/protocol/source/email/- IMAP poll, filters, task queuesrc/protocol/source/source.service.ts- discover and per-source watchsrc/protocol/source/ftp/ftp.service.ts- watch count and disconnected skipsrc/core/data/data.service.ts- shared disconnected checksrc/app.controller.ts-POST config/source/watchsrc/config.dto.ts- email fields and watch bodysrc/core/configuration/config.schema.ts- email config validationui/src/pages/workflows/- wizard, summary, Check nowdocs/user/configuration/sources.md- email source (EN and FR)docs/user/configuration/examples.md- email YAML example (EN and FR)
Known issues
- None recorded in the 3.2.0 fragment.
Next steps
- None from this release.