Using outbound authenticated SMTP from Exchange
Using Exchange System Manager navigate to the 'Servers' container.
Now drop down the 'Protocols' container. Next find the 'SMTP'
protocol and select 'Default SMTP Virtual Server'. Right click on
the default smtp virtual server and choose 'Properties'.
Click on the 'Outbound Security...' button. This is where you
will enter the User ID (email address) and password of you were given. Choose 'Basic authentication'.
Exchange 2003 uses the term Basic Authentication, whereas it really is SMTP AUTH
to the rest of the internet community. The user name is case
sensitive and the password is case sensitive.
This step is optional - and should be used if your ISP blocks outbound traffic on port 25.
Click on 'Outbound connections...' on the delivery tab. Change the port number to '587'. This port is an alternative message port, which will bypass any Transparent Proxies implemented by the ISP.
Click on 'Advanced' on the main delivery options tab. Your fully qualified domain name should be the domain that is appended to all of your outgoing mail. In order to get mail to relay through our servers you will need to setup the 'Smart host' . This is what tells Exchange to delivery all mail destined for the internet though our servers. Use 'outmail.profilter.co.uk' for your smart host. All mail being delivered to the internet will be handed off to this smart host server. Click OK when completed.
After you've completed the above steps you will need to restart your SMTP service for all changes to take effect. Any mail that is currently in the queue might not take these new settings so you might need to send a new piece of mail to test it. After sending a test email you will want to check the outbound queue on Exchange to make sure that the mail did not get stuck in your outbound queue because of authentication errors. Navigate to the Server queue and click on any line that has pending messages and you will see error status at the bottom. You can see that this mail failed because of SMTP AUTH on the remote server. This means that the username and password that you've entered for relaying is not valid. Double check the user ID (email address) and password that you've configured and try again.