Separate component for tracking URLs & data segmentation

[arthurzenika]

Serving the tracking URLs using the same web server as the admin interface can be a security issue in some cases. Would it be possible to have a separate component for the tracking web component with some further garanties as to not serving the admin web ui on that component and URLs associated with it ?

A further segmentation with a different MySQL user could also be a good security measure to ensure that a security bug limits the access to the data from a web server that is meant to be exposed to public access (as opposed to the admin web interface which can be put behind private URLs, VPNs and other security measures).

[willpower232]

As you have to configure each tracking URL in your proxy program of choice (nginx/caddy/etc) anyway, there is nothing stopping you from having a different version of Postal running with a slightly different configuration.

The tracking response is enabled by a header applied from the proxy so I don't think there is a way around that from the clients perspective so they shouldn't be able to get to the UI that way.