Problem w external client sending to external domain
I have an Exch 07 server handing all roles (ex Edge trans). Until now OWA was fine for our users on the outside of corporate network. I now need to allow an outside ebill company to relay through us to make it look as if mail came from us. I have in place an ISA server allowing access to OWA. For normal mail traffic I have our MX records pointing to a Barracuda SPAM FW then on to my Exchange Server. I am having a ____ of a time getting this to work and have probably been going at this all wrong - so instead of typing up what I've already done can someone lay out or point me in a direction to make this happen. It will be greatly appreciated. Thanks, Dennis
July 7th, 2010 6:29pm

Most pieces are already in place with Exchange 2007. Tell them to use port 587, and authenticate when sending. You will simply need to configure the ISA server to allow that port through. Port 587 is the SMTP over SSL port. This is what the Client Receive Connector is for in Exchange 2007. If they insist on using port 25 because they can't handle SSL connections, then you will need to use another connector. Effectively a slight variant of this posting from the MS Exchange team: http://msexchangeteam.com/archive/2006/12/28/432013.aspx From a security point of view though, the SMTP over SSL with authenticated relaying is the most secure option, as it means the username and password is not going over the Internet in the clear. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 8:20pm

I like the port 587 via ISA. How can I test this to see if I have it configured correctly? Thanks
July 7th, 2010 8:56pm

Outlook Express can use the configuration. Get a machine that is outside the network and configure it for a test account. You will need to adjust the server settings to use SSL and port 587. However ISA doesn't do port 587 by default, so you will probably have to run the publish wizard for SMTP servers and configure it first. Then there is the SSL certificate involved, but if you are using the same host name as you do for everything else, then the same certificate should work. It is just like doing 443, but not for https, but for SMTP over SSL. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 10:59pm

Thanks Simon - works great.
July 8th, 2010 9:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics