Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
exchange working as relay after service pack 4 install
- Thread starter jaydo1
- Start date
Very simple, take a look at this article from Microsoft.
Mike
=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
Mike
=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
better yet look at this:
and/or read this below:
The following are basic steps to ensure that your registered domains and IP addresses do not get added to MAPS or any other mail abuse databases. This procedure should be the first step in protecting your server from being brought to it's knees by SPAMMERS looking for a free server to distribute unsolicited messages to bulk recipients. Unfortunately, by default, Exchange 5.5 configures it's IMS as an SMTP open relay. This basically means that anyone inside, or outside, can use your IMS to deliver messages virtually, anywhere they'd like to.
Procedure to correct this situation:
Connect the Exchange Administrator program to an Exchange server which is running the Internet Mail Service (IMS).
Navigate to the connections container, which is a sub-container, under site configuration.
Open the properties page of your IMS object.
Click on the routing tab, of the properties page.
Click on the 'routing restrictions' button.
Check the box titled "Hosts and Clients connecting to these IP addresses". If you need to have any internal machines use this box to relay mail, add the ip addresses as either individual entries, or a single entry which covers a range of addresses. For a single address, be sure to specify a subnet mask of 255.255.255.255. To cover a subnet such as 10.x.x.x, use a single entry of 10.0.0.0 with a mask of 255.0.0.0.
Restart you IMS service for the change to take effect.
Test using an SMTP client such as Outlook Express, or telnet on port 25.
and/or read this below:
The following are basic steps to ensure that your registered domains and IP addresses do not get added to MAPS or any other mail abuse databases. This procedure should be the first step in protecting your server from being brought to it's knees by SPAMMERS looking for a free server to distribute unsolicited messages to bulk recipients. Unfortunately, by default, Exchange 5.5 configures it's IMS as an SMTP open relay. This basically means that anyone inside, or outside, can use your IMS to deliver messages virtually, anywhere they'd like to.
Procedure to correct this situation:
Connect the Exchange Administrator program to an Exchange server which is running the Internet Mail Service (IMS).
Navigate to the connections container, which is a sub-container, under site configuration.
Open the properties page of your IMS object.
Click on the routing tab, of the properties page.
Click on the 'routing restrictions' button.
Check the box titled "Hosts and Clients connecting to these IP addresses". If you need to have any internal machines use this box to relay mail, add the ip addresses as either individual entries, or a single entry which covers a range of addresses. For a single address, be sure to specify a subnet mask of 255.255.255.255. To cover a subnet such as 10.x.x.x, use a single entry of 10.0.0.0 with a mask of 255.0.0.0.
Restart you IMS service for the change to take effect.
Test using an SMTP client such as Outlook Express, or telnet on port 25.
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question
