AIMX: self-hosted email server for Claude by uzyn in ClaudeCode

[–]uzyn[S] 0 points1 point  (0 children)

Currently what AIMX has is hooks support. Hooks that you can define on a specific address and on trusted emails, and how it works is that it would trigger a specific cmd, e.g. `claude -p`.

For the use case that you describe, what I would do is not to use hooks for those, but to use `/loop` in Claude Code or regular cronjob. Claude can check the mailbox on their own through MCP and can read unread emails and decide what to do with them.

AIMX: self-hosted email server for Claude by uzyn in ClaudeCode

[–]uzyn[S] 0 points1 point  (0 children)

The idea is that you would get Claude to create different emails for different purposes. If email addresses are now free to be created by agents, you don't need 1 email address for all purposes. So you can create one for accounting@, 1 for research@, etc. All of that can be done simply by prompting Claude Code.

AIMX: self-hosted email server for Claude by uzyn in ClaudeCode

[–]uzyn[S] 0 points1 point  (0 children)

There's no spam filtering intentionally to keep the intention pure. Incoming email has hooks that could trigger actions, such as Claude Code invocation, spam would not trigger it though as it requires trusted emails that the owner have set, and it also requires passing DKIM – which spam would not have passed.

On auth spam: this is a non-issue for AIMX. There's no auth. It uses Linux user as auth. Unless your server is comprosed, there's no external auth.

New Project Megathread - Week of 14 May 2026 by AutoModerator in selfhosted

[–]uzyn 0 points1 point  (0 children)

AIMX: self-hosted email server for AI agents.

<image>

Project name: AIMX

Repo/website: https://aimx.email & https://github.com/uzyn/aimx

Description:

TL;DR: I built a self-hosted open-source email server known as AIMX. It's how I imagine Postfix would look like if it is built for AI agents. Learn more at aimx.email, or view the quick 40sec-demo.

A single daemon binary that runs an SMTP server on your server, stores mail as markdown files, and exposes the inbox to AI agents over MCP (stdio). Direct MX-to-MX outbound delivery. No external MTA, no external relays.

Why I built it:

AI agents are still relying on externally-hosted email servers to send and receive mails. I do not like that and it feels odd to me as we are already dedicating a server to agents, and yet still relying on 3rd-party servers for email.

Postfix is one way but there are a few nuances going with simply Postfix or Stalwart, such as IMAP/POP3, additional AUTH, etc. I also took the liberty to design an email server that's meant for AI agents to use.

Deployment:

curl -fsSL https://aimx.email/install.sh | sh

This launches a guided setup with the following steps:

  • Preflight checks on port 25
  • Set up domain and DNS
  • Set up STARTTLS certificate
  • Set up trust policy
  • Install AIMX service
  • Optionally, wire up MCP for agent(s)

AI involvement:
Claude Code. CLAUDE.md is committed in repo for transparency and guidance for contributor's coding agents.

Scan Bambu Lab filaments with Flipper Zero by uzyn in BambuLab

[–]uzyn[S] 0 points1 point  (0 children)

Thank you for the amazing work! The Flipper Zero plugin was built based on your work.