# NousResearch/hermes-agent · Email login username separate from sender address

## Open now

- 4 issues, 2 PRs open on GitHub.
- #12232: \[Feature\]: IMAP username
- #25849: \[Bug\]: EMAIL_ADDRESS env var does not always match the actual email account/user being used (enable EMAIL_ACCOUNT)
- #41331: \[Bug\] email: IMAP/SMTP login user hardcoded to EMAIL_ADDRESS — breaks Custom Email Domain setups
- #46676: Email gateway: allow separate IMAP/SMTP login from the From address
- PR #25918: feat(email): add EMAIL_ACCOUNT env var for separate IMAP/SMTP login (#25849)
- PR #41341: fix(email): allow separate IMAP/SMTP login username via EMAIL_LOGIN_USER

These issues and PRs address the inability to configure a different username for IMAP/SMTP authentication when it differs from the EMAIL_ADDRESS value, particularly affecting custom domain setups. Multiple approaches are proposed, including new environment variables such as EMAIL_LOGIN_USER and EMAIL_ACCOUNT.

## TL;DR

- 8 member(s): 4 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.22`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Open related issues

- #12232: \[Feature\]: IMAP username
- #25849: \[Bug\]: EMAIL_ADDRESS env var does not always match the actual email account/user being used (enable EMAIL_ACCOUNT)
- #41331: \[Bug\] email: IMAP/SMTP login user hardcoded to EMAIL_ADDRESS — breaks Custom Email Domain setups
- #46676: Email gateway: allow separate IMAP/SMTP login from the From address

## Prior & competing PRs

- **#41451: fix(email): add EMAIL_LOGIN_USER for custom domain IMAP/SMTP auth (#41331)**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#25918: feat(email): add EMAIL_ACCOUNT env var for separate IMAP/SMTP login (#25849)**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#25849`
  - files: `gateway/platforms/email.py`, `tests/gateway/test_email.py`, `tools/send_message_tool.py`
- **#41341: fix(email): allow separate IMAP/SMTP login username via EMAIL_LOGIN_USER**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#77384`
  - files: `gateway/platforms/email.py`, `tests/gateway/test_email.py`
- **#77384: fix(email): support separate IMAP/SMTP login user via EMAIL_LOGIN_USER**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `4f074b38e6d697475cad66f6dfd612dcc6f908d9`, `#41331`, `#46676`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`