Installing and Uninstalling Anti-Spam in Exchange 2007

Exchange 2003 was built differently from Exchange 2007, and the Anti-Spam section of the system could be put to work or disabled just by marking the component as displayed in the SMTP Virtual Server. This though is not possible in Exchange 2007, and there is a specific element of the program that deals with junk, spam and viruses. This though does mean that the Anti-Spam section is not installed as a default during the program installation.

Installing the Anti-Spam System

Installing though is fairly straightforward and just requires the use of a PowerShell script as found in the installation of Exchange 2007’s Hub Transport.

Close the Exchange Management Console and then use PowerShell to follow the file path, Program FilesMicrosoftExchange ServerScripts. The Install-AntispamAgents.ps1 script should be followed. The changes are confirmed by restarting the Microsoft Exchange Transport.

The changes can be seen by looking at the Hub Transport in the Exchange Management Console, there will be an Anti-Spam tab displayed.

Uninstalling the Anti-Spam System

It is possible to uninstall the Anti-Spam system from Exchange 2007’s Hub Transport role. This is done once the Exchange Management Console has been shut down.

The PowerShell is then opened and the file path, Program FilesMicrosoftExchange ServerScripts is followed. The Uninstall-AntispamAgents.ps1 script should be followed, which will require separate elements of the system to uninstalled and confirmed, including sender filtering, content filtering and connection filtering. The changes are confirmed by restarting the Microsoft Exchange Transport.

The changes can be seen by looking at the Hub Transport in the Exchange Management Console, there will no longer be an Anti-Spam tab displayed.

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Installing and Uninstalling Anti-Spam in Exchange 2007

Exchange 2007 makes the process though more difficult that Exchange 2000 and 2003 did. In previous releases it used to be possible to make a new email address the default just by altering the “set as primary” marker. This though cannot be done in 2007 as the option of “set as reply” is not available. Therefore it is necessary to uncheck the marker that allows for “automatically update email addresses based on recipient policy.” Once this marker has been removed then the option for “set as reply” is available and can be applied to the new email address. One last step is to manually alter the primary email address within the AD.

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

change primary address in exchange 2007

Attempting to install Exchange Server 2003 onto a Domain Controller computer does create problems, including performance issues.

• The server cannot be a cluster. Exchange Server 2003 clusters which co-exist alongside Active Directory Servers will not be supported by Microsoft
• The server cannot just be Domain Controller, and will also need to be a Global Catalog server
• DSAccess/DSProxy/Cat will not fail-over or load balance to another Domain Controller or Global Catalog server.
• Use of the /3GB switch may cause the Exchange cache to use up the majority of system memory. It is also important that the number of user connections is kept to the minimum, this will also help in avoiding the need for the /3GB switch
• There is a security risk that could see services that are being run under LocalSystem being susceptible to security bugs. If a bug attacks Active Directory then it will also attack Exchange Server, and if one attacks Exchange Server then it will also be able to attack the Active Directory
• Administrators may be able to increase their permission levels within Active Directory as they are able to access the Domain Controller
• There will be an issue in the speed of server closedown as well. Times in excess of ten minutes are not unknown as the AD service (LSASS.EXE) will have to shut down prior to the shutdown of Exchange services. You will also find that DSAccess will timeout on several occasions before it will eventually shutdown. The only way to make this process faster is to have the Exchange services manually stopped before a computer shutdown is commenced

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Do not install Exchange Server 2003 on a Domain Controller

The simplest method of creating an admin email address to which misdirected mails can be forwarded is in the properties of the virtual server. Here there should be a “Messages” tab that allows for an entry to be added to the “Send a copy of NDR’s to”, here another user account or email address can be added.

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Creating an admin email address for misdirected mails

Formatting Exchange Server Emails to add a disclaimer or legal notice footer to every sent mail

Adding footers is possible, although the method used is dependant on the version of Exchange that is being utilised. In general terms though, the simplest method is to make use of an application form another company to do it for you. A lot of information can be found at mycomputeraid.com

Recommended companies include –

http://www.gfi.com/mes

http://www.policypatrol.com

http://www.mimesweeper.com

http://www.exclaimer.co.uk

http://www.disclaimit.com

For Exchange 5.5 Microsoft also provide imsext.dll -

http://support.microsoft.com/?kbid=258206

For Exchange 2000 you will need to write an SMTP transport event sink. Information on this is found at – http://support.microsoft.com/?kbid=317680

There is also a lot of information to be found for both Exchange 5.5 -

http://www.swinc.com/resource/exch_faq.htm

and Exchange 2000 –
http://www.swinc.com/resource/e2kfaq.htm

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Add a footer to every email in exchange