# Delete mail address of a web hosting package

> Delete one mail address of a web hosting package - a mailbox with all its mail.

- Effect: Destructive - Removes something for good. Agents ask first.
- Idempotent: no
- Stability: beta
- MCP tool: `manitu_webhosting_mail_address_delete` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/webhosting/mail/address/delete`
- Needs: `service_webhosting`
- Page: /reference/webhosting/mail/address/delete/

**Removes something for good. Agents name what will be lost and wait for an explicit yes; a program should ask the same.**

## MCP tool

`manitu_webhosting_mail_address_delete`

### Description for the model

Deletes a mail address of a web hosting package of the manitu customer account this connection works in, by site_id and mail_address from manitu_webhosting_mail_address_list, of any type. Its aliases go with it; a MAILBOX GOES WITH ALL ITS MAIL, for good; the address is taken out of other addresses' targets. Mail to it is then handled by the catch-all of its domain, if there is one, else refused. To switch a mailbox off for a while, use manitu_webhosting_mail_address_set with mailbox.suspended instead; to remove an alias, set the alias_list of its address. Refused with a conflict when the package cannot be changed now (not_configurable). Ask the customer for an explicit yes first, naming the address, its type and - for a mailbox - that its mail is lost.

### Arguments

- `site_id` (integer | string, required) - The site_id from manitu_webhosting_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `mail_address` (string, required) - The mail address from manitu_webhosting_mail_address_list, e.g. info@example.de - a catch-all is written "@" and its domain, e.g. @example.de. Never guess one. (minLength `2`; maxLength `254`)

### Example

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manitu_webhosting_mail_address_delete",
    "arguments": {
      "site_id": 12345,
      "mail_address": "info@example.com"
    }
  }
}
```

## REST

`POST https://api.manitu.de/v1/webhosting/mail/address/delete`

### Authentication

One of `X-API-Key`, `Authorization: Bearer …` - never more than one in a request.

### Request body

JSON; unknown fields are refused.

- `site_id` (integer | string, required) - The site_id from manitu_webhosting_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `mail_address` (string, required) - The mail address from manitu_webhosting_mail_address_list, e.g. info@example.de - a catch-all is written "@" and its domain, e.g. @example.de. Never guess one. (minLength `2`; maxLength `254`)

### Response

In `data`; the rest of the body as on every call.

- `mail_address` (string, required) - The address deleted.
- `type` (string | null, required) - What it was - as in the list.

### Statuses

- `200` Success.
- `400` The request does not match the declared input schema.
- `401` No credential was presented, or it was not recognised.
- `403` The credential is not permitted to use this operation.
- `500` The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.
- `503` The channel this operation forwards through is unavailable.

### Example

```sh
curl -X POST 'https://api.manitu.de/v1/webhosting/mail/address/delete' \
  -H 'X-API-Key: $API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"site_id":12345,"mail_address":"info@example.com"}'
```

## Example result

```json
{
  "mail_address": "info@example.com",
  "type": "string"
}
```