Aliases enable sending via api

[svenopdehipt]

Summary

I recently noticed that the aliases in mailcow now offer an option to disable/enable sending. I have an app which uses the mailcow api and newly created aliases are now disabled for sending with no option to enable sending via the api. I would like to have an option to enable sending via the api.

Motivation

This would allow users to enable sending emails via aliases created via the api.

Additional context

No response

[admins-little-helper]

I think the API already supports this. It's just not part of the docuementation.
The endpoints "add/alias" and "edit/alias" accept the property "sender_allowed" in the body.

Here's an example, when creating an alias:

curl -X POST "https://your-mailcow/api/v1/add/alias" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
		"sender_allowed": "1",
		"goto": "mailbox@domain.tld",
		"sogo_visible": "1",
		"address": "alias@domain.tld"
	  }'

And here's an example, when editing an alias:

curl -X PATCH "https://your-mailcow/api/v1/edit/alias" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
		"attr":
		{
			"sender_allowed": "1"
		},
		"items": [
			"6"
		]
	  }'

[svenopdehipt]

That did work. Thanks