# Email Integration > Integrates with any IMAP/SMTP mail server (Gmail, Outlook, Naver, Kakao, custom servers, etc.). Use when the user wants to read, send, search, reply to, or manage emails. On first use, runs interactive account setup in the terminal to store credentials in a local config file with restricted permissions. Subsequent requests use the stored config without re-asking for credentials. Triggers on requests like: "메일 보여줘", "이메일 확인", "send email", "받은 편지함", "메일 보내줘", "메일 검색". - Skill: `fritzprix/email-integration` (Agent Skill, multi-file: 7 files) - Install (CLI): `npx skillmds@latest add fritzprix/email-integration` - Raw SKILL.md: https://api.skillmd.com/api/skills/fritzprix/email-integration/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - Author: fritzprix (https://skillmd.com/u/fritzprix) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/fritzprix/email-integration --- # Email Integration Skill Enables the agent to interact with any IMAP/SMTP mail server on behalf of the user. ## ⚠️ Security Rules (Mandatory) - **NEVER** ask for passwords or credentials in chat - **NEVER** display or repeat the contents of `~/.libragent/email_config` - **ALWAYS** use `setup_account.py` for credential collection — it uses `getpass()` so input is hidden in terminal - If the user accidentally pastes credentials in chat, acknowledge receipt, do NOT echo them back, and immediately run setup to store them properly --- ## Overview Email integration involves these steps: 1. **Detect config** — run `validate_config.py` to check if account is configured 2. **Setup (first time only)** — run `setup_account.py` interactively in terminal 3. **Dispatch action** — classify the user's request and call `email_client.py` with the right action 4. **Present results** — format and summarize the output for the user --- ## Step 1: Detect Config Always start by checking if the account is configured: ```bash python scripts/validate_config.py ``` - Exit code `0` → configured, proceed to Step 3 - Exit code `1` → not configured, go to Step 2 - Exit code `2` → config exists but invalid (e.g. wrong password), go to Step 2 with `--reset` flag --- ## Step 2: Account Setup (First Time or Reset) Tell the user setup is needed, then run in terminal: ```bash python scripts/setup_account.py ``` For reset after auth failure: ```bash python scripts/setup_account.py --reset ``` The script will: 1. Prompt for email address (visible) 2. Auto-detect server settings from domain (see `references/server-profiles.md`) 3. Prompt for password using `getpass()` — **input is hidden** 4. Test the connection live 5. Save to `~/.libragent/email_config` with restricted permissions After successful setup, proceed to Step 3 with the original user request. --- ## Step 3: Dispatch Action Classify the user's request into one of five actions and call `email_client.py`: ### Action: `read_inbox` — Browse received emails ```bash python scripts/email_client.py --action read_inbox [--limit N] [--filter unread|today|all] ``` Use when: "메일 보여줘", "받은 편지함", "최근 메일", "안 읽은 메일" Default: `--limit 10 --filter unread` --- ### Action: `read_email` — Read full email content ```bash python scripts/email_client.py --action read_email --uid ``` Use when: user refers to a specific email by number/index from a previous list, or "이 메일 내용 보여줘" The UID comes from a prior `read_inbox` call. Always mark as read after displaying. --- ### Action: `send_email` — Compose and send ```bash python scripts/email_client.py --action send_email \ --to "recipient@example.com" \ --subject "제목" \ --body "본문" \ [--cc "cc@example.com"] \ [--reply-to-uid ] ``` Use when: "메일 보내줘", "답장 써줘", "이메일 작성" For replies, always include `--reply-to-uid` so `In-Reply-To` and `References` headers are set correctly. **Compose guidance**: If the user gives a vague request ("김 팀장한테 회의 일정 잡는 메일"), draft the full body yourself and confirm with the user before sending. --- ### Action: `search_email` — Search by keyword/sender/date ```bash python scripts/email_client.py --action search_email --query "" ``` Query construction examples: - "김철수한테 온 거" → `--query "FROM 김철수"` - "지난주 메일" → `--query "SINCE 26-May-2026"` - "프로젝트 관련" → `--query "SUBJECT 프로젝트"` - "첨부파일 있는 거" → `--query "BODY attachment"` (best effort) Refer to `references/request-patterns.md` for more examples. --- ### Action: `manage_email` — Mark/move/delete ```bash python scripts/email_client.py --action manage_email \ --uid \ --op \ [--folder ] ``` Use when: "읽음 처리", "삭제해줘", "스팸함으로 이동", "보관함으로" For bulk operations (e.g. "스팸함 비워"), confirm count with user before proceeding. --- ## Step 4: Present Results - **Inbox list**: Show as a numbered table — `# From Subject Date (Unread?)` - **Email body**: Show full content, list attachments separately - **Search results**: Same as inbox list, with match count - **Send/manage**: Confirm action completed with brief summary - **Errors**: See Error Handling below --- ## Error Handling | Error | Cause | Action | | ---------------------- | ------------------------------------- | --------------------------------------------------------------- | | Auth failed (IMAP 535) | Wrong password or App Password needed | Run `setup_account.py --reset`, guide user to App Password docs | | Connection refused | Wrong host/port | Check `references/server-profiles.md`, offer to re-run setup | | Config not found | First run or deleted | Run `setup_account.py` | | SSL error | Port mismatch | Suggest switching 993↔143 or 587↔465 | | Send failed (SMTP 550) | Recipient rejected | Confirm address with user | Always provide the next concrete step, never just report the error. --- ## Output Format Guidelines For inbox listings, use this format: ``` 📬 받은 편지함 (읽지 않은 메일: 3 / 총 47개) # 보낸 사람 제목 날짜 1 ● 김철수 [긴급] 서버 점검 안내 오늘 09:14 2 ● 박영희 6월 회의 일정 공유 오늘 08:30 3 noreply@github.com PR #142 merged 어제 23:11 ● = 읽지 않음 | 더 보려면: "다음 10개 보여줘" ``` For send confirmation: ``` ✅ 메일 발송 완료 받는 사람: recipient@example.com 제목: 회의 일정 확인 요청 발송 시각: 2026-06-01 14:23 ```