bondy.error.relay_not_permitted
When the calling realm may not use the named relay.
Description
The relay exists, but the calling realm is not in its mail.relay.$name.realms list.
That list is operator-owned and default-deny: a relay with no realms configured is available to the master realm only. It lives in bondy.conf rather than in realm state precisely so that a realm administrator cannot grant their own realm access to a relay — that would be privilege escalation across the operator/tenant boundary.
A prototype URI in the list admits every realm that inherits from it, so the fix for a family of tenant realms is usually one line. See Configuring Mail Relays.
| Handle | Nature | HTTP status |
|---|---|---|
M003 | permanent | 403 |
Positional Results
0The error message.
Keyword Results
The standard error payload. Each key of details also appears at the top level.
coderelay_not_permitted
detailsHolds relay. The configured name of the relay. Never its hostname, username or credential.
See also
- Mail — the model these errors come from.
- Mail WAMP API — the procedures that raise them.
- Mail Configuration Reference — the keys that decide them.