Cairn

Email login username separate from sender address

NousResearch/hermes-agent · cluster 12232 · gateway

Data as of

6 open items. Fix attempted, not merged.

The short answer

4open issues
2open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
4 issues and 2 PRs.

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.

Open issues4

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

Open PRs2

  • PR#25918feat(email): add EMAIL_ACCOUNT env var for separate IMAP/SMTP login (#25849)
  • PR#41341fix(email): allow separate IMAP/SMTP login username via EMAIL_LOGIN_USER

2 PRs closed without merging

From the close comments: other 2

  • #41451 fix(email): add EMAIL_LOGIN_USER for custom domain IMAP/SMTP auth (#41331) · other
  • #77384 fix(email): support separate IMAP/SMTP login user via EMAIL_LOGIN_USER · other → 4f074b3, #41331, #46676
How this cluster was grouped
  • Link evidence (partly structural links): 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 item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/12232.json
cluster/12232.md