Patrik Kernstock

The error is generally completely different. Please don't let us mix those two different issues in one thread - could you please open a new issue?

> But `mariadb-upgrade` can fix some issues as well like Yes, correct. That's why I suggested in https://github.com/mailcow/mailcow-dockerized/issues/6349#issuecomment-2694930315 running `mysql-upgrade` with at least the check-parameter to see if any upgrade...

Please run the command from https://github.com/mailcow/mailcow-dockerized/issues/6349#issuecomment-2694930315 so that we can see if upgrade went fine.

I'm not aware about any need. Your comment has been the first post since Sep 2023, that it is apparently a open relay because of this. Also, the `daemon.json` is...

Just re-opening for now. We're still not understanding how an open-relay is supposed to occur - except for some misconfiguration or allowing certain IPs to send without proper authentication. Default...

Excellent summary - thank you very, very much! Very helpful. > From Postfix’s perspective, the request originated from 172.22.1.1. Using the `postconf` command inside the running Postfix container, the current...

> But that's a different error message than "relay access denied", isn't it? What if you try an existing mail address as sender? Valid point. I'll try to check today...

> Idea of additional port not sounds bad, even if we go or not go with host network [@bobobo1618](https://github.com/bobobo1618) and that's really nice [@patschi](https://github.com/patschi) I agree. Also like this idea....

> Thank you for the PR. I think there is no need to make it customizable. We should always return 404. @patschi What do you think? I like this change...

`str_starts_with` sounds good indeed - great idea. I'd say rebase & force-push - to keep the discussion in this PR too. Should do the trick.