Mailu API

What authentication does the Mailu API use?

Mailu uses an API token passed in the Authorization header, configured in the admin interface of the self-hosted instance. Through Jentic the token is encrypted in the vault and injected at execute time, so it never enters the agent context.

Can I create a new mailbox user through the API?

Yes. POST /users with email, password, and quota creates the mailbox. GET /users/{email} returns the configured user, and PATCH or DELETE update or remove it.

How do I forward mail from one address to another on Mailu?

Create an alias with POST /aliases where the source is the public address and destination is the list of recipients. Update the alias with PATCH /aliases/{email} or remove it with DELETE.

What are the rate limits for the Mailu API?

Mailu is self-hosted, so rate limits depend on the operator's deployment rather than a managed quota. The OpenAPI spec does not declare limits - keep request rates reasonable to avoid pressure on the admin process.

How do I provision a Mailu user through Jentic?

Run pip install jentic, search 'create mailu user', load the schema for POST /users, and execute with email, password, and quota. Jentic injects the API token from the vault at request time.

Can I limit what my agent is allowed to do with the Mailu API?

Yes. Because you run Jentic One yourself, your own rules decide which Mailu operations and credentials the agent may use. Since Mailu puts the user address in the URL path, such as GET /users/{email}, you can pin the agent to reading a single user, and you choose the operations it may call so that creating a user, alias, domain, or relay is excluded unless you add it. Your Mailu API token stays with your self-hosted instance and is injected only at execution time, never entering the agent's context.