>> So, before investigating more, let me ask: did anyone managed to remove the >> /SOGo path under Nginx?
> I'll likely not work correctly right now as "SOGo" is hardcoded in a few > places. There's an open bug for this: http://www.sogo.nu/bugs/view.php?id=331 I tried changing the proxy settings in apache. It indeed failed to work properly. My only conclusion is just that, the path defined within the SOGo application itself. The only reason for me to change the path is to obfuscate access to SOGo. It seems to dramatically cut down on obnoxious potential malicious network traffic if paths of applications are non-default and therefore out of reach of bots trying to hack passwords, etc. Adi-- [email protected] https://inverse.ca/sogo/lists
