53 lines
2.3 KiB
Markdown
53 lines
2.3 KiB
Markdown
# Email Agent — Original Notes (archived)
|
|
|
|
> Historical pre-planning notes. **Superseded by `AGENTS.md`.** Do not build from this.
|
|
|
|
|
|
> Kept for provenance. The sections above replace these. Do not build from this.
|
|
|
|
```
|
|
# Intro
|
|
To create an email agent that will be developed over time to handle the
|
|
samuelrolfe@gmail.com emails. This account will have emails come in from other
|
|
accounts linked into this using MX records including hello@where-woof.com,
|
|
hello@kontra.day, sam@audasmedia.com.au and samuelrolfe@gmail.com.
|
|
|
|
# Objective
|
|
- I am unsure how email agents work - need advise in planning stage.
|
|
- Create an admin interface.
|
|
* Ignore unsubscribe
|
|
* Recommend to Delete -> Delete
|
|
* Summarized Emails -> Delete
|
|
* Summary
|
|
* Email Rules for ai
|
|
* Auto replied emails -> Delete
|
|
* Other requirements as advised by ai planning bot
|
|
* Some emails will be responded to
|
|
- Collate emails into subjects and or, who they are for - which email did they come through on?
|
|
- Delete spam email or repetitive emails that can not be unsubscribed.
|
|
- Advise to unsubscribe to email spam, check if they are on ignore unsubscribe spam list
|
|
- unsubscribe
|
|
- create report. Delete report. Delete associated emails.
|
|
- A.i. interface - Respond to emails, delete spam, unsubscribe, add new rule etc.
|
|
- LLM skills style text editor, just input text, for LLM responses to categorized emails.
|
|
- Move for deletion to a delete folder or trash.
|
|
- Move replied to to replied to folder per email address
|
|
- Summary of emails daily. Possible concertina or left nav for replies. Deletions. Etc. Select all -> delete.
|
|
- Option to save specific emails or move to folder.
|
|
- Jev to analyze emails based on rules.
|
|
|
|
# Plan / Overview (historical)
|
|
- Build using Paperclip. N8N as trigger. Web interface on .13, /var/www.
|
|
- Obsidian on .27.
|
|
- Use JEV to assess emails (skill installed, key present). Build a JEV pipeline.
|
|
- Assess whether the interface can create rules JEV uses.
|
|
- Golang + HTMX interface for speed.
|
|
- Response templates / LLM skills per category.
|
|
- Document on Obsidian / Outline / Vikunja / Gitea via project-docs.
|
|
```
|
|
|
|
### Email and DNS reference
|
|
|
|
Full setup: `.27:/home/sam/obsidian/300 areas/360 Dev-Ops Network Computers/Email & DNS Setup — Domains, Mailboxes & Records.md`.
|
|
Summary: Cloudflare DNS → PurelyMail mailboxes → forward to Gmail. Outbound via Amazon SES.
|