On 14/03/06, Greg Ward <[EMAIL PROTECTED]> wrote: > The one ray of hope is that we already have guaranteed HTTPS > connectivity from customer sites to a support server on our premises. > (We can't monitor the remote deployments without it, so opening outgoing > port 443 to this one special host is pretty much a prerequisite for > being one of our customers.)
Then you have your answer - add functionality to the interface which already 'calls home' over HTTPS to trigger emails from your central server. This way you're squeaky-clean about the firewall privileges you've got them to implement for you - never a good idea to hoodwink your customer by stealth into allowing something which their security policy doesn't want you to have. And it will work for all customers without a second thought. Peter -- Peter Bowyer Email: [EMAIL PROTECTED] Tel: +44 1296 768003 VoIP: sip:[EMAIL PROTECTED] VoIP: [EMAIL PROTECTED] FWD: **275*5048707000 VoipTalk: **473*5048707000 -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
