Hermes Agent answers emails, recommending using an independent email address from the beginning, rather than directly using your personal primary email address for experiments. The focus of the official email documentation is on two-way configuration: receive IMAP, send credit SMTP, and then configure the allowed sender list.
What information to prepare
- An email account dedicated to Hermes.
- SMTP host, port, username, password, or App Password.
- IMAP host, port, username, password, or App Password.
EMAIL_ALLOWED_USERS, limit who can give orders to Hermes.
Recommended configuration order
- First, enable IMAP/SMTP in the email service provider's backend.
- If your service provider supports two-step verification, use App Password first.
- Write the parameters into
~/.hermes/.env. - Start
hermes gatewayby sending a simple test email to Hermes.
What should I do if I receive it but don't reply?
These are usually not model issues, but rather send/receive link or allowlist issues. First, check if the EMAIL_ALLOWED_USERS contains the sender's email address; Check whether IMAP is successfully pulled and whether SMTP is intercepted by the service provider. The official documentation also mentions that if you want Hermes to return an email with an attachment, you can use the form MEDIA:/path/to/file in the results.
In a word: Email configuration is most afraid of hard-connecting to production scenarios with personal emails, so the safe approach is to upload an independent account + IMAP/SMTP + allowlist together.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
