gortium/infra
1
1
Fork 0
Code Issues 13 Pull Requests 21 Actions Packages Projects 1 Releases Wiki Activity

feat: Email management with himalaya - inbox cleanup and monitoring #16

New Issue
Open
opened 2026-04-29 23:41:14 +00:00 by Hermes · 0 comments
Hermes commented 2026-04-29 23:41:14 +00:00
Collaborator
Copy Link

Summary

Set up automated email management for personal and work accounts using himalaya CLI.

Requirements

Accounts

Features

  1. Inbox Cleanup Cron Job

    • Process emails in batches of 500 to avoid overload
    • Run until inbox is empty
    • Auto-deactivate when complete
    • Define "clean" action (archive/delete/move)

  2. Important Email Monitoring

    • Watch for important incoming emails
    • Send Matrix notification when detected
    • Define "important" criteria (sender, subject, flags)
    • Note: Matrix bridge currently not working - needs fix

  3. Response Templates

    • Pre-prepared email responses
    • Manual approval before sending (or auto-send for certain categories)
    • Store templates in repo

Implementation Plan

  1. Install himalaya in agent container
  2. Configure IMAP/SMTP for both accounts
  3. Create cleanup script with batch processing
  4. Set up cron job with self-deactivation logic
  5. Implement email watcher for important messages
  6. Fix Matrix bridge for notifications
  7. Create response template system

Status

On hold - User will provide more details later (credentials, cleanup rules, importance criteria)

Related

  • Matrix bridge issue: (to be linked)
  • himalaya skill: email/himalaya
## Summary Set up automated email management for personal and work accounts using himalaya CLI. ## Requirements ### Accounts - **Personal**: Gmail (tpouplier@gmail.com or similar) - **Work**: Hostinger (tpouplier@tdnde.com) ### Features 1. **Inbox Cleanup Cron Job** - Process emails in batches of 500 to avoid overload - Run until inbox is empty - Auto-deactivate when complete - Define "clean" action (archive/delete/move) 2. **Important Email Monitoring** - Watch for important incoming emails - Send Matrix notification when detected - Define "important" criteria (sender, subject, flags) - Note: Matrix bridge currently not working - needs fix 3. **Response Templates** - Pre-prepared email responses - Manual approval before sending (or auto-send for certain categories) - Store templates in repo ## Implementation Plan 1. Install himalaya in agent container 2. Configure IMAP/SMTP for both accounts 3. Create cleanup script with batch processing 4. Set up cron job with self-deactivation logic 5. Implement email watcher for important messages 6. Fix Matrix bridge for notifications 7. Create response template system ## Status **On hold** - User will provide more details later (credentials, cleanup rules, importance criteria) ## Related - Matrix bridge issue: (to be linked) - himalaya skill: `email/himalaya`
gortium self-assigned this 2026-04-29 23:43:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hermes gortium
No Assignees gortium
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gortium/infra#16
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?