potiuk opened a new issue, #303:
URL: https://github.com/apache/airflow-steward/issues/303

   The IMAP mail-source adapter is currently a documentation stub — the 
contract is defined but no executable lands the actual operations. Land the 
concrete CLI per 
[`tools/mail-source/imap/README.md`](../tree/main/tools/mail-source/imap/README.md).
   
   **Operations to implement** (per the [mail-source 
contract](../tree/main/tools/mail-source/contract.md)):
   
   - `list_recent_threads(list, since)` — `IMAP SEARCH SINCE <date>` against 
the configured folder
   - `read_thread(thread_id)` — fetch by Message-ID + walk `References:` / 
`In-Reply-To:` chain
   - `list_drafts(thread_id)` — list Drafts folder filtered to thread
   - `list_sent_since(thread_id, since)` — search Sent folder
   - `create_draft(thread_id, body)` — `APPEND` to Drafts with the threading 
headers from 
[`tools/gmail/threading.md`](../tree/main/tools/gmail/threading.md) (the 
threading rule is shared across backends)
   - `thread_url(thread_id)` — build archive deep-link (Hyperkitty / PonyMail / 
Pipermail) per the adopter's public archive, or fall back to `imap://`
   
   **Why:** Many projects run on corporate IMAP (Office 365, Fastmail, 
self-hosted Dovecot, Cyrus) — Gmail-only forecloses those adopters. An IMAP 
backend is also the natural choice for shared role mailboxes (e.g. 
`[email protected]`) that aren't on Gmail.
   
   **Reference:**
   
   - Contract: 
[`tools/mail-source/contract.md`](../tree/main/tools/mail-source/contract.md)
   - Stub spec (capability claim already declared): 
[`tools/mail-source/imap/README.md`](../tree/main/tools/mail-source/imap/README.md)
   - Existing Gmail backend for reference shape: 
[`tools/gmail/tool.md`](../tree/main/tools/gmail/tool.md)
   - Python `imaplib` (stdlib) is sufficient; `aioimaplib` for async if 
preferred
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to