micw

The behaviour should have been similar prior to that backport, except that `HOST_*` and `*_ADDRESS` was used equally in some services. The change is that if `HOST_*` is set, it's...

I think so, yes. But the current behaviour was introduced for reason (dns lookup failures I think) and that was before my time. So I'm waiting for feedback of the...

@jawabuu I don't think that we have the resources to test it ourself. The limitations of `HOST_*` and the advantage of `*_ADDRESS` are well documented.

@muhlemmer @kaiyou Do you think we should switch the docker-compose setup from `HOST_*` to `*_ADDRESS`?

@jawabuu Sorry, got the "test out the scenarios above" wrong. What you describe is indeed expected behaviour. Mailu by default resolve all `HOST_*` to static addresses. This gives strong resistance...

Yes, it's env only. I have no suitable docker-compose test env. When it works smoothly, I'd switch to `*_ADDRESS`. If not I'd dig into the issue.

I think we would need to host a service somewhere that can be used to perform such a check. Mailu admin calls that external service, telling it "please check me"....

Just an idea. Nginx mail proxy asks the admin backend for auth, see https://docs.nginx.com/nginx/admin-guide/mail-proxy/mail-proxy/#mail_auth So the backend react on special credentials and return the IP it sees as error message....

If anyone is willing to test it and do the necessary changes in travis config in the near future, I'd add the 1.8 label

I'd like to pick up this issue because there are some pending feature requests for roundcube plug-ins: - carddav (https://github.com/Mailu/Mailu/issues/1230, https://github.com/Mailu/Mailu/issues/1116) - pgp (https://github.com/Mailu/Mailu/issues/506) Personally I'd like to see https://plugins.roundcube.net/packages/melanie2/infinitescroll...