We also need this separation in our company!

If the SOGo-Server is comprised the attacker could upload a virus or modified integrator package which is then pushed to all clients which is inadmissible.

We serve a different secured server for any automatic contributed updates.

The solution should be easy:
Two different variables, one for SOGo-Server and one for Update-Server, should do the job.

Is there a lot of problem with unique sogo-server and update-server like nameserver.mydomain.com:

• if i need to change name or domain of sogo-server i should reinstall all the client with new xpi, and i can't do this remotly.
• every integrator need to be create with different domain, if i have a lot of server i need to create a lot of integrator xpi, one for every domain. It's difficult to do this work automatic.
• if i use only the name of server (like an alias 'sogo') for be domain indipendent (es. http://sogo/), this configuration doesn't work out of LAN, for mobile/laptop users i should change sogo-server address

For all this reason i need to separate sogo-server and update-server and, other feature very important, to change manually by user the sogo server.

A useful feature!

Here a user already prepared a patch for this five years ago:
https://lists.inverse.ca/sogo/arc/users/2014-12/msg00227.html

How about integrating into SOGo?