Customising quarantine email URLs
Posted: 30 Dec 2012 11:48
Is there a supported way to customise the links in the quarantine emails? I am running EFA as (effectively) a hosted appliance behind a NAT firewall. As a result, all the links in the email are to:
http://INTERNAL_IP/messages/release/MSG_GUID/
For example (less obfuscated):
http://10.0.0.3/messages/release/123456 ... 890abcdef/
I'd really prefer to have the URL use a defined name (antispam.domain.com, for example) so that I can release messages without having to VPN into the hosting network. It may be that I failed to set up the appliance correctly - but I do not remember seeing settings related to this (other than the computer name of the appliance, which does not appear to be used in the emails). Having said that I also do not see any use of the hostname defined in Baruwa setup - which is a short name, not a FQDN (a problem, perhaps?)
I checked out /usr/share/pyshared/baruwa/settings.py and the QUARANTINE_REPORT_HOSTURL contains the IP address - so changing it there looks like it would fix the emails, but I suspect that running efa-configure (e.g. as part of a version upgrade) might .. "break" it again?
Happy to provide further information - if someone can tell me what I can usefully provide.
http://INTERNAL_IP/messages/release/MSG_GUID/
For example (less obfuscated):
http://10.0.0.3/messages/release/123456 ... 890abcdef/
I'd really prefer to have the URL use a defined name (antispam.domain.com, for example) so that I can release messages without having to VPN into the hosting network. It may be that I failed to set up the appliance correctly - but I do not remember seeing settings related to this (other than the computer name of the appliance, which does not appear to be used in the emails). Having said that I also do not see any use of the hostname defined in Baruwa setup - which is a short name, not a FQDN (a problem, perhaps?)
I checked out /usr/share/pyshared/baruwa/settings.py and the QUARANTINE_REPORT_HOSTURL contains the IP address - so changing it there looks like it would fix the emails, but I suspect that running efa-configure (e.g. as part of a version upgrade) might .. "break" it again?
Happy to provide further information - if someone can tell me what I can usefully provide.