Delete mail address of a web hosting package
Delete one mail address of a web hosting package - a mailbox with all its mail.
manitu_webhosting_mail_address_delete on https://mcp.manitu.de/mcpAnnotations as tools/list sends them
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_idinteger | stringrequiredThe site_id from manitu_webhosting_list - never guess one.
mail_addressstringrequiredThe 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.
Result structuredContent, checked against the schema
mail_addressstringrequiredThe address deleted.
typestring | nullrequiredWhat it was - as in the list.
Authentication
One of X-API-Key, Authorization: Bearer … - never more than one in a request. More
Request body JSON; unknown fields are refused
site_idinteger | stringrequiredThe site_id from manitu_webhosting_list - never guess one.
mail_addressstringrequiredThe 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.
Response in data; the rest of the body as on every call
mail_addressstringrequiredThe address deleted.
typestring | nullrequiredWhat it was - as in the list.
Statuses
200Success.400The request does not match the declared input schema.401No credential was presented, or it was not recognised.403The credential is not permitted to use this operation.500The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.503The channel this operation forwards through is unavailable.