DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a real mail server that receives mail for your domain with Sentio

Install Sentio without Docker and run it as a systemd service on port 25.

Authorization notice. Sentio is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. The README asks you to copy and run install commands with sudo, so review each command before running it on a production host.

Who it is forA systems engineer who wants agents to receive mail on a domain they control and needs direct MX delivery.

The problemRelying on a hosted email API adds a dependency and limits control over the mail path.

The outcomeSentio runs as a systemd service accepting SMTP on ports 25, 465 and 587 and the REST API on port 8080.

What you need first

  • Docker Engine 24+ with the Compose plugin, about 4 GB RAM and 8 GB disk, or a Linux host with PostgreSQL 18+, Redis or Valkey, NATS with JetStream, and S3-compatible storage
  • A terminal and curl
  • Rotation of the bootstrap admin API key before the host is reachable by anyone else

Steps

  1. Install build dependencies, then run cargo build --release in the cloned repo.
  2. Create the database with sudo -u postgres createdb --owner=sentio sentio.
  3. Run ./target/release/sentio-smtp --config config/default.toml migrate.
  4. Copy the config with sudo cp config/default.toml /etc/sentio/sentio.toml and set server.hostname, database.url and storage.
  5. Install the unit with sudo systemctl enable --now sentio-smtp and check logs with journalctl -u sentio-smtp -f.

Prompt for your agent

In the truespar/sentio repo, build with cargo build --release, run the migrate command against config/default.toml, and enable the sentio-smtp systemd service. Report the output of curl localhost:8080/health/ready. Verify that port 25 accepts a connection from an external test host for <your-domain>.

Caveat. Receiving mail on port 25 also needs DNS, PTR and MX records that the README covers only under 'Running a real mail server'.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page