Lars Hubrich

Please include the following text in this pr to fulfill the [contribution guidelines](https://github.com/hetzneronline/community-content/blob/master/contributing.md#how-to). ``` I have read and understood the Contributor's Certificate of Origin available at the end of https://raw.githubusercontent.com/hetzneronline/community-content/master/tutorial-template.md...

Periodically fetching the main Hetzner website is probably not the best [example](https://github.com/hetzneronline/community-content/blob/a5c763d25ee6ecb24de5b8373d566dd4abc8ce71/tutorials/deploy-uptime-kuma-with-docker/images/9.png).

I'm just a nerdy Hetzner customer and my approval is just for my recommended changes. @leojakeson is the person who decides which tutorial gets approved.

Yes, I executed `docker-compose up -d` with the following response: ``` mailcow_redis-mailcow_1 is up-to-date mailcow_solr-mailcow_1 is up-to-date mailcow_clamd-mailcow_1 is up-to-date mailcow_olefy-mailcow_1 is up-to-date mailcow_dockerapi-mailcow_1 is up-to-date mailcow_unbound-mailcow_1 is up-to-date mailcow_memcached-mailcow_1...

The error which I posted above is gone but the subdomains of my alias domain still does not show up anywhere in my logs. Do you know if this feature...

Ok, that answers the question then. Even if it is not actually intended, it is possible to send e-mails from alias domains. I just tested this earlier. Would it be...