Microsoft Exchange Server Versions

Exchange Server Versions

These are the Exchange Server Versions and their build numbers. Also links  to downloading each one of them!!!

You can check your version on 2007-2016 with the command – Get-ExchangeServer | Select Name, AdminDisplayVersion

To check your version on 2000 or 2003 –

  1. Start the Microsoft Exchange Administrator program.
  2. In the navigation pane, expand the objects until you locate the server object.
  3. Right-click the server object, and then click Properties.

Exchange Server Release dates

Product name Build number Date
Microsoft Exchange Server 2003 6.5.6944233 03
Microsoft Exchange Server 2003 SP1 6.5.7226 5/25/2004
Microsoft Exchange Server 2003 SP2 6.5.7638 10/19/2005
Microsoft Exchange Server 2007 8.0.685.24 12/9/2006
Microsoft Exchange Server 2007 8.0.685.25 12/9/2006
Microsoft Exchange Server 2007 SP1 8.1.240.6 11/29/2007
Microsoft Exchange Server 2007 SP2 8.2.176.2 8/24/2009
Microsoft Exchange Server 2007 SP3 8.3.083.6 6/20/2010
Microsoft Exchange Server 2010 14.0.639.21 11/9/2009
Microsoft Exchange Server 2010 SP1 14.1.218.15 8/24/2010
Microsoft Exchange Server 2010 SP2 14.2.247.5 12/4/2011
Microsoft Exchange Server 2010 SP3 14.3.123.4 2/12/2013
Microsoft Exchange Server 2013 15.0.516.32 10/11/2012
Microsoft Exchange Server 2016 15.1.225.42 10/01/2015

Exchange Server 2007 Service Pack 1

Product name Build number Date KB
Microsoft Exchange Server Exchange 2007 SP1 8.1.240.6 11/29/2007
Update Rollup 1 for Exchange Server 2007 Service Pack 1 8.1.263.1 2/28/2008 KB945684
Update Rollup 2 for Exchange Server 2007 Service Pack 1 8.1.278.2 5/8/2008 KB948016
Update Rollup 3 for Exchange Server 2007 Service Pack 1 8.1.291.2 7/8/2008 KB949870
Update Rollup 4 for Exchange Server 2007 Service Pack 1 8.1.311.3 10/7/2008 KB952580
Update Rollup 5 for Exchange Server 2007 Service Pack 1 8.1.336.1 11/20/2008 KB953467
Update Rollup 6 for Exchange Server 2007 Service Pack 1 8.1.340.1 2/10/2009 KB959241
Update Rollup 7 for Exchange Server 2007 Service Pack 1 8.1.359.2 3/18/2009 KB960384
Update Rollup 8 for Exchange Server 2007 Service Pack 1 8.1.375.2 5/19/2009 KB968012
Update Rollup 9 for Exchange Server 2007 Service Pack 1 8.1.393.1 7/17/2009 KB970162
Update Rollup 10 for Exchange Server 2007 Service Pack 1 8.1.436.0 4/9/2010 KB981407

 


Exchange Server 2007 Service Pack 2

Product name Build number Date KB
Microsoft Exchange Server 2007 SP2 8.2.176.2 8/24/2009
Update Rollup 1 for Exchange Server 2007 Service Pack 2 8.2.217.3 11/19/2009 KB971534
Update Rollup 2 for Exchange Server 2007 Service Pack 2 8.2.234.1 1/22/2010  KB972076
Update Rollup 3 for Exchange Server 2007 Service Pack 2 8.2.247.2 3/17/2010 KB979784
Update Rollup 4 for Exchange Server 2007 Service Pack 2 8.2.254.0 4/9/2010 KB981383
Update Rollup 5 for Exchange Server 2007 Service Pack 2 8.2.305.3 12/7/2010  KB2407132

 


Exchange Server 2007 Service Pack 3

Product name Build number Date KB
Microsoft Exchange Server 2007 SP3 8.3.083.6 6/20/2010
Update Rollup 1 for Exchange Server 2007 Service Pack 3 8.3.106.2 9/9/2010 KB2279665
Update Rollup 2 for Exchange Server 2007 Service Pack 3 8.3.137.3 12/10/2010 KB2407025
Update Rollup 3 for Exchange Server 2007 Service Pack 3 8.3.159.0 3/2/2011 KB2492691
Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3 8.3.159.2 3/30/2011 KB2530488
Update Rollup 4 for Exchange Server 2007 Service Pack 3 8.3.192.1 7/7/2011 KB2509911
Update Rollup 5 for Exchange Server 2007 Service Pack 3 8.3.213.1 9/21/2011 KB2602324
Update Rollup 6 for Exchange Server 2007 Service Pack 3 8.3.245.2 1/25/2012 KB2608656
Update Rollup 7 for Exchange Server 2007 Service Pack 3 8.3.264.0 4/16/2012 KB2655203
Update Rollup 8 for Exchange Server 2007 Service Pack 3 8.3.279.3 8/13/2012 KB2734232
Update Rollup 8-v2 for Exchange Server 2007 Service Pack 3 8.3.279.5 10/9/2012 KB2756497
Update Rollup 8-v3 for Exchange Server 2007 Service Pack 3 8.3.279.6 11/13/2012 KB2778154
Update Rollup 9 for Exchange Server 2007 Service Pack 3 8.3.297.2 12/10/2012 KB2746157
Update Rollup 10 for Exchange Server 2007 Service Pack 3 8.3.298.3 2/11/2013  KB2788321
Update Rollup 11 for Exchange Server 2007 Service Pack 3 8.3.327.1  8/13/2013 KB28737461
Update Rollup 12 for Exchange Server 2007 Service Pack 3 8.3.342.4 12/10/2013 KB2903911
Update Rollup 13 for Exchange Server 2007 Service Pack 3 8.3.348.1 2/25/2014 KB2917522
Update Rollup 14 for Exchange Server 2007 Service Pack 3 8.3.379.2 8/26/2014 KB2936861
Update Rollup 15 for Exchange Server 2007 Service Pack 3 8.3.389.2 12/9/2014 KB2996150
Update Rollup 16 for Exchange Server 2007 Service Pack 3 8.3.406.0 3/17/2015 KB3030086
Update Rollup 17 for Exchange Server 2007 Service Pack 3 8.3.417.1 6/16/2015 KB3056710
Update Rollup 18 for Exchange Server 2007 Service Pack 3
8.3.445.0 12/10/2015 KB3078672

 


Exchange Server 2010

Product name Build number Date KB
Microsoft Exchange Server 2010 RTM 14.0.639.21 11/9/2009
Update Rollup 1 for Exchange Server 2010 14.0.682.1 12/9/2009 KB976573
Update Rollup 2 for Exchange Server 2010 14.0.689.0 3/4/2010 KB979611
Update Rollup 3 for Exchange Server 2010 14.0.694.0 4/9/2010 KB981401
Update Rollup 4 for Exchange Server 2010 14.0.702.1  6/17/2010 KB982639
Update Rollup 5 for Exchange Server 2010 14.0.726.0 12/13/2010 KB2407113

Exchange Server 2010 Service Pack 1

Product name Build number Date KB
Microsoft Exchange Server 2010 SP1 14.1.218.15 8/24/2010
Update Rollup 1 for Exchange Server 2010 SP1 14.1.255.2 10/4/2010 KB2407028
Update Rollup 2 for Exchange Server 2010 SP1 14.1.270.1 12/9/2010 KB2425179
 Update Rollup 3 for Exchange Server 2010 SP1 14.1.289.3 3/7/2011 KB2492690
Update Rollup 3-v3 for Exchange Server 2010 SP1 14.1.289.7 4/1/2011 KB2529939
Update Rollup 4 for Exchange Server 2010 SP1 14.1.323.1 6/22/2011 KB2509910
Update Rollup 4-v2 for Exchange Server 2010 SP1 14.1.323.6 7/27/2011  KB2579150
Update Rollup 5 for Exchange Server 2010 SP1 14.1.339.1 8/23/2011 KB2582113
Update Rollup 6 for Exchange Server 2010 SP1 14.1.355.2 10/27/2011  KB2608646
Update Rollup 7 for Exchange Server 2010 SP1 14.1.421.0 8/13/2012 KB2743248
Update Rollup 7-v2 for Exchange Server 2010 SP1 14.1.421.2 10/9/2012 KB2756496
Update Rollup 7-v3 for Exchange Server 2010 SP1 14.1.421.3 11/12/2012 KB2778158
Update Rollup 8 for Exchange Server 2010 SP1 14.1.438.0 12/10/2012 KB2787763

 


Exchange Server 2010 Service Pack 2

Product name Build number Date KB
Microsoft Exchange Server 2010 SP2 14.2.247.5 12/4/2011
Update Rollup 1 for Exchange Server 2010 SP2 14.2.283.3 2/13/2012 KB2645995
Update Rollup 2 for Exchange Server 2010 SP2 14.2.298.4 4/16/2012 KB2661854
Update Rollup 3 for Exchange Server 2010 SP2 14.2.309.2 5/29/2012  KB2685289
Update Rollup 4 for Exchange Server 2010 SP2 14.2.318.2 8/13/2012 KB2706690
Update Rollup 4-v2 for Exchange Server 2010 SP2 14.2.318.4 10/9/2012 KB2756485
Update Rollup 5 for Exchange Server 2010 SP2 14.2.328.5 11/13/2012 KB2719800
 Update Rollup 5-v2 for Exchange Server 2010 SP2  14.2.328.10  12/10/2012  KB2785908
 Update Rollup 6 for Exchange Server 2010 SP2 14.2.342.3 2/11/2013 KB2746164
Update Rollup 7 for Exchange Server 2010 SP2 14.2.375.0 8/13/2013 KB2874216
Update Rollup 8 for Exchange Server 2010 SP2 14.2.390.3 12/10/2013 KB2903903

 


Exchange Server 2010 Service Pack 3

Product name Build number Date KB
Microsoft Exchange Server 2010 SP3 14.3.123.4 2/12/2013 KB2808208
Update Rollup 1 for Exchange Server 2010 SP3 14.3.146.0 5/29/2013 KB2803727
Update Rollup 2 for Exchange Server 2010 SP3 14.3.158.1 8/13/2013 KB2866475
Update Rollup 3 for Exchange Server 2010 SP3 14.3.169.1 11/25/2013 KB2891587
Update Rollup 4 for Exchange Server 2010 SP3 14.3.174.1 12/10/2013 KB2905616
Update Rollup 5 for Exchange Server 2010 SP3 14.3.181.6 2/25/2014 KB2917508
Update Rollup 6 for Exchange Server 2010 SP3 14.3.195.1 5/23/2014 KB2936871
Update Rollup 7 for Exchange Server 2010 SP3 14.3.210.2 8/26/2014 KB2961522
Update Rollup 8-v2 for Exchange Server 2010 SP3 14.3.224.2 12/12/2014 KB2986475
Update Rollup 9 for Exchange Server 2010 SP3 14.3.235.1 3/17/2015 KB3030085
Update Rollup 10 for Exchange Server 2010 SP3 14.3.248.2 6/16/2015 KB3049853
Update Rollup 11 for Exchange Server 2010 SP3 14.3.266.1 9/11/2015 KB3078674
Update Rollup 12 for Exchange Server 2010 SP3 14.3.279.2 12/10/2015 KB3096066

Exchange Server 2013

Product Name Build Number Date [mm/dd/yyyy] KB
 Microsoft Exchange Server 2013 RTM  15.0.516.32  12/03/2012
 Exchange Server 2013 Cumulative Update 1 (CU1)  15.0.620.29  04/02/2013  KB2816900
 Exchange Server 2013 Cumulative Update 2 (CU2)  15.0.712.24  07/09/2013  KB2859928
 Exchange Server 2013 Cumulative Update 3 (CU3)  15.0.775.38  11/25/2013  KB2892464
 Exchange Server 2013 Service Pack 1 (SP1 aka CU4)  15.0.847.32  02/25/2014  KB2926248
 Exchange Server 2013 Cumulative Update 5 (CU5)  15.0.913.22  05/27/2014  KB2936880
 Exchange Server 2013 Cumulative Update 6 (CU6)  15.0.995.29  08/26/2014  KB2961810
 Exchange Server 2013 Cumulative Update 7 (CU7)  15.0.1044.25  12/09/2014  KB2986485
 Exchange Server 2013 Cumulative Update 8 (CU8)  15.0.1076.9  03/17/2015  KB3030080
 Exchange Server 2013 Cumulative Update 9 (CU9)  15.0.1104.5  06/16/2015  KB3049849
 Exchange Server 2013 Cumulative Update 10 (CU10)  15.0.1130.7  09/14/2015  KB3078678
 Exchange Server 2013 Cumulative Update 11 (CU11)  15.00.1156.006  12/10/2015  KB3099522

Exchange Server 2016

Product Name Build Number Date [mm/dd/yyyy] KB
 Exchange Server 2016 Preview  15.1.225.16  6/22/2015
 Exchange Server 2016 RTM  15.1.225.42  10/01/2015
 Exchange Server 2016 Cumulative Update 1  15.1.396.30  3/14/2016  KB3134844
Exchange Server 2016 Cumulative Update 2
15.1.4XX.XX X/XX/2016 KBXXXXXX

 

Install Exchange 2016 on Windows Server 2016

Install Exchange 2016 on Windows Server 2016

Install Exchange 2016 – Hi everyone. I am back and I am installing Exchange 2016 on Windows Server 2016 (currently TP3) from scratch on a virtual machine.

So before the install:

VMWare Workstation 10

256GB SSD (let’s see how fast the install will be)

2016 TP3 iso downloaded from Microsoft. Click Windows Server 2016 Download.

40GB of free space

Exchange 2016 Enterprise. Click Exchange 2016 Download.

Step by step what happens in the video below:

  1. I create a Virtual Machine using VMWare Workstation. Preferably with the most resources like CPU and RAM that you can spare. Attach the downloaded Windows Server iso file to the DVD/CD.
  2. Start the VM and boot from CD which has the Windows Server 2016 iso attached.
  3. We choose Windows Server 2016 Technical Preview (Server with Desktop Experience)
  4. We configure a static IP and change the name of the server and reboot
  5. Once the server is back from reboot we install Active Directory Domain Services from Server Manager. Add Roles and Features
  6. Follow along the auto-selected Features as well
  7. After the installation has finished go to Server Manager and click on the flag and choose to Promote this server to domain controller
  8. On the wizard step 1, choose 3rd option. Add a new forest
  9. Type the domain name below. Root domain name:_______
  10. Select Forest and Domain Functional level – Windows Server 2016/Technical Preview
  11. Check the Domain Name System (DNS) Server
  12. Type in a Directory Services Restore Mode password
  13. Ignore the Warning for DNS delegation and go Next
  14. Type in a NetBIOS name. Example. If contoso.com, you can choose just contoso. Use the default one at best
  15. Recommended that you don’t change the AD paths in the next section
  16. If no errors and just warnings proceed with Install
  17. After the reboot log back in and copy over the Exchange installation files to your server
  18. Start the setup
  19. Go through the initial setup screen with Next, then choose Recommended settings (not that important choice, whatever you like) and go to Next.
  20. Choose Mailbox role and check “Automatically install Windows Server roles and features…” and click Next
  21. Recommended that you leave the default path of “C:\Program Files\Microsoft\Exchange Server\V15”
  22. Type in an Exchange Organization Name. Can be whatever you like. Do not check “Apply Active Directory split permissions”
  23. If you want malware protection leave at “No” and click Next.
  24. The prerequisites check starts. Once it finishes you should only have one Error for missing the Microsoft Unified Communications Managed API 4.0 64-bit. The rest should be warnings. Download the API from here.
  25. If you have problems downloading due to error in Internet Explorer “Your current security settings do not allow this file to be downloaded” go to your Internet Options in your Internet Explorer. Go to tab Security. Click on Custom Level and browse to Downloads and change from Disable to Enable.
  26. Download and Install the API. Retry the Readiness Check.
  27. It should be only warnings and the Retry button to be replaced by Install button. Click and sit back for an hour.
  28. Your Exchange should be installed now. Here are some tips
  29. Your Outlook Web App or Outlook on the Web, as it’s called in 2016 is on the same URL as before – https://localhost/owa and your Exchange Administration Center is on – https://localhost/ecp.
  30. For your email flow to be full you need to create a Send Connector. In your Admin Center, go to Mail Flow and then Send Connectors. Click + to create a new one.
  31. Put a name for it. For type – Choose Internet
  32. Leave it on MX record associated
  33. Address space – click + and only add * to the “Full Qualified Domain Name” field. This means that through this send connector your will be able to send to all the domains in the world 😉 Leave the cost at 1.
  34. On the next menu click + and add your own server
  35. There we go you should be having a start-up working Exchange Server 2016 from scratch !!!

And this is the video !

Install Exchange 2016 on Windows Server 2016

Failed Security Audits 4625 HMWorker Exchange 2013

Failed Security Audits 4625 HMWorker Exchange 2013

One of the first problems I encountered after Installing Exchange 2013 on Windows Server 2012 ( and R2 ) was that my security log grew to 200k events in just a few days. Event ID 4625 Unknown user name or bad password coming from your Healthmailox usually under the name of HealthMailbox4d14f344f…@domainname. The process producing it was “C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe”. The problem itself is a bit masked. On the client side you can barely notice any problems but your Event Viewer is a different story. The problem indicates problems with your Health mailboxes even without upgrading or migrating. It happens with new installs too. So searching the web I found the solutions which at this point are very limited for such new technologies as Windows Server 2012 R2 and Exchange 2013.

I found the solution of re-creating your Health monitoring mailboxes to be working well for me. Here is how :

Open Exchange Management Shell as Administrator and type :

Get-Mailbox -monitoring | Get-MailboxStatistics

get-mailbox-monitoring

As you can see the ItemCount is large. We will be removing these mailboxes but we don’t have the full names displayed here. So we will run the same command put “| fl” it.

Get-Mailbox -monitoring | Get-MailboxStatistics | fl

get-mailbox-monitoring-fl

Remove-Mailbox -Identity HealthMailbox4d14f344f6294c1fb8d3f45bf436452a and confirm Y.

remove-mailbox

Do this for the rest of the health monitoring mailboxes. Take their Identities from the “Get-Mailbox -monitoring | Get-MailboxStatistics | fl” command.

After your are done deleting them you will have to re-run the PrepareAD cmd from the Exchange setup.

Navigate your Exchange Shell to the bin directory of Exchange installation:

cd “Program Files\Microsoft\Exchange Server\V15\bin”

Once there type

setup.exe /preparead /iacceptexchangeserverlicenseterms

Wait for the setup to finish and restart the Exchange Health Manager service.

net stop msexchangehm

net start msexchangehm

setup-prepare-ad

This should re-create your health mailboxes. Run the Get-Mailbox -monitoring | Get-MailboxStatistics to double check.

 

 

 

Setup mail relay in Exchange 2003/2007/2010

Setup mail relay in Exchange 2003/2007/2010

At some point in your IT lives you will find yourself in the position to configure mail relay, for a device or a server in your local network. Here’s how it’s done :

Exchange 2003 :

Exchange Console -> Administrative Groups -> first administrative group -> Servers -> Servername -> Protocols -> SMTP -> Right click Properties on the Default SMTP Virtual Server -> Access tab – Relay. Click Add and insert the IP address of the device you that want to relay through your Exchange.

relay 2003

Exchange 2007/2010:

Not easy to guess if you don’t know – It is done through the use of a Receive Connector.

Go to Exchange Management Console – > Hub Transport -> Receive Connectors. Right Click and choose New Receive Connector.

Choose an appropriate name for it. For intended use choose Custom.

For Local Network Settings, leave it as it is. on Specify the FQDN type in your Fully Qualified Domain Name of your server. Example . Exchangeserver.contoso.local

On the Remote Network Settings, delete the entry 0.0.0.0-255.255.255.255 and add on your own. Input the IP address of the device that you want to relay through the Exchange server.

Click New. This will create the Connector but our job is not yet done. Right click the Connector and go to Properties. On the Authentication tab choose Externally Secured. On the permissions tab leave blank.

Open Exchange Shell. Type the following command:

The only change in the command you need to make is to put the real Connector’s name in the brackets.

Get-ReceiveConnector -Identity “Connector’s Name” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient”

Depending on specifics around the relay you may need to specify Exchange Users as Permissions group.

Can’t remove additional mailboxes in Outlook

Can’t remove additional mailboxes in Outlook

Have you ever wondered why you can’t close down your additional mailboxes in Outlook, returning you this error :

Can't remove additional mailbox from Outlook

Only to find out that your Account Settings tab is empty?

Can't remove additional mailbox from Outlook

Well there is still hope. There are two options. You can just re-create the Outlook profile and hope that this fixes it or you can choose to explore more options. One of these options is called Auto Mapping and is introduced in Exchange 2010 and 2013.

It basically automatically adds any mailboxes you have Full Access to directly into your Outlook client. This is designed to reduce the administrative time to give such access especially for helpdesk teams where a single click can provide you with Full Access but you need still to do a remote session to the customer’s computer and add the mailbox into their Outlook.This is for the customers that don’t know how to do it themselves and believe me 90% of them don’t.

However touching the automapping cannot be done through the GUI and would need Shell. Here is the command :

Add-MailboxPermission -Identity User1 -user “User2” -AccessRights FullAccess -InheritanceType All -AutoMapping:$false

where User 1 is the mailbox owner and User 2 is the user receiving the FullAccess rights to User1’s mailbox. -AutoMapping:$false or true turns off and on the automapping.

Can't remove additional mailbox from Outlook

Don’t worry if you run the command for users that already have Full Access to their mailboxes, it will still run the command properly.

For those of you who want to go even further here are the registry keys responsible for the Outlook profiles. Always backup your registry before editing !

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Default

Going through Exchange 2013 Admin Center

Going through Exchange 2013 Admin Center

Exchange 2013 Admin Center – Whether you like it or not, Exchange 2013 has ditched the all beautiful Management Console and has gone to a web based ( in a browser ) management called Exchange Admin Center. Still buggy for me in IE 10. Here is a video of going through the different menus without going deep in to the details.

exchange 2013 admin center

Official MS Library article: http://technet.microsoft.com/en-us/library/jj150562.aspx

Here is the video. Enjoy:

Installing Exchange 2013 on Windows Server 2012

Installing Exchange 2013 on Windows Server 2012

Installing Exchange 2013 on Windows Server 2012 is new and interesting theme among the IT world nowadays and that’s why I tried installing it without reading what’s new and if anything else is required. I wanted to make a video of it and upload it unedited so it can show how a pure installation goes on without preparations and with any problems coming on the way. Installation is done on a virtual test machine with 8 GB of RAM. With a minimum requirements of 8 GB of RAM it was clearly not very optimal for running 2012 + Exchange 2013. Maybe a few more GB will make it run smooth. This time there are packages that need installing.

2010 Filter packhttp://www.microsoft.com/en-us/download/details.aspx?id=17062

installing exchange 2013 on windows server 2012

Service Pack 1 for Microsoft Office Filter Pack 2010 (KB2460041) 64-bit Edition –

http://www.microsoft.com/en-us/download/details.aspx?id=26604

Unified Communications Managed API 4.0 Runtime –

http://www.microsoft.com/en-us/download/details.aspx?id=34992

 

And here is the video. I repeat, it’s unedited so feel free to jump on long reboots or installations.

 

Email Blacklists ( RBLs )

 Introduction

 

Blacklists or otherwise called RBLs ( Realtime Blackhole Lists ) are Internet lists that intercept email message routes, scan and review email messages and if they find spam/malware in a message they block the IP address of the sending server. Being into a list, means that whenever you cross path with this blacklist, your email messages will be denied and a NDR will be returned to you. That also means that the higher the number of blacklists your IP appears on,  more likely the chance of your email message to be denied somewhere on the route to its destination. Remember, blacklist problems only affect sending emails and it has nothing to do with receiving email problems. There are many websites that can check if an IP is blocked by the most common internet RBLs. One such website is http://mxtoolbox.com/blacklists.aspx. If IP address is blacklisted, it means that the server is sending out bad emails such as spam and malware or infected emails. You need to scan the server and clean it if infected. If server is clean you can go for the workstations. It might be only one of the users sending out bad email while the other users are good but this will still get the IP banned.  If the IP is heavily blacklisted and despite being clean now some blacklists won’t let go, you can think of a smart host solution. More on smart hosts here.

If blacklisted you could do :

1) Mxtoolbox provides links on the blacklists that your IP appears to be blocked. Links are leading to the reason why the IP was blocked and ways to unlist it. So first check the reasons

2) If the server is having a lot of messages intercepted by the blacklists and it interrupts their workflow, you can search for a smart host solution until the IP is delisted from the Blacklists.

3) Scan the server and the workstations and make sure Exchange configurations are tight. You can refer to other documents here to achieve that.

3) Once you are sure the server and the workstations are clean and the exchange configuration is tight, you can go for the delisting process

4) Run a MX Toolbox Diagnostics tool and check if the address matches the smtp banner. This is what your servers says in it’s Helo response to smtp connections. If they don’t match you can read how to fix that here.

 

When checking blacklists on MxToolbox after the first search result you will notice that it is checking you against 45 known blacklists, if you click the Check All Blacklists will check against 105. 

 

 

 

However Mxtoolbox doesn’t check against all of the blacklists possible. Here are some websites that check against much more blacklists and are in ways more reliable:

1. http://MultiRBL.Valli.org
2.
http://JustSpam.org
3.
http://UnifiedeMail.net
4.
http://BlacklistAlert.org/

Exchange 2007/2010 Anti-Spam Tools

Exchange 2007/2010

 

Exchange 2007 – Most of the features the same as the ones in 2003 and some are new and some are just with a different name.

 

Exchange Management Console – > Organization Configuration -> Hub Transport -> Anti-Spam

 

Content FilteringThe same as 2003

 

IP Allow List – Specify IP addresses that are always allowed to connect and transmit email messages to the server. It can be a single IP or a Range. You can only Enable/Disable the feature from here. To actually add/remove addresses is done from Server Configuration – > Hub Transport -> Anti-Spam.

 

IP Block List – Disallow IP addresses or ranges from connecting to the server. Same as IP Allow List.

 

IP Allow List Providers – Here you can specify an external whitelist with approved senders. One such is The Spamhaus Whitelist.

 

IP Block List Providers – This is the same as Connection Filtering in 2003. Here you can provide and external blacklist like Zen Spamhaus which is free. For more info check Connection Filtering.

 

Recipient Filtering – Purpose is the same as in 2003. However you need to execute the following command to turn on the Blocked Recipients list – Set-RecipientFilterConfig -BlockListEnabled $true

To see if the entries are valid – Get-RecipientFilterConfig | Format-List BlockedRecipients.

 

Sender Filtering – Same purpose as in 2003 but more developed. You can block email addresses, domains and domain hierarchies. Block blank senders should be ticked. In 2007 you can also specify how the server will react if the Blocked Senders list is met – Reject or Stamp.

 

Sender ID – The same as 2003 but with fewer options. Just Enable/Disable and Action.

 

Sender Reputation – New feature. Server determines Sendeer Reputation Level and based on a set treshold it adds the sender to the IP Block list for a specific amount of hours. Reputation is deteremined by:

HELO/EHLO analysis, Reverse DNS lookup, Analysis of SCL ratings on messages from a particular sender, Sender open proxy test. Full info on here.

 

There is another option called Aggregation of Outlook Junk E-mail Filter Lists. This feature helps reduce false positives in anti-spam filtering by propagating Outlook 2003 and Outlook 2007 Junk E-mail Filter Lists to Mailbox servers and to Edge Transport servers. For more information, see Safelist Aggregation.

 

Exchange 2010 –  Same funtionality and features but it needs to be turned on as by default it is not. Open Exchange Management Shell. Type Set-TransportServer –identity “SERVERNAME” -AntispamAgentsEnabled $true. Restart the Microsoft Exchange Transport service. Close and re-open the Exchange Management Console and the Anti-Spam tabs will be there in the same place as in 2007.

 

Other possible reasons for SPAM are infected server or workstations which will be sending spam OUT or to other internal recipients. Best way to fight with it is to scan and clean the machines.

Exchange 2003 Anti-Spam Tools

The main tools to fight spam is by having the proper configuration on the Exchange server, clean computers/server ( from malware ) and additional software that could be 3rd party.

 

Exchange 2003

 

The tools to fight spam are located in System  Manager -> Message Delivery -> Properties.

 

Sender Filtering – Filter messages with blank sender is ticked – mandatory. If you want a specific email to be blocked you can tick “Drop connection if address matches filter” and Add the desired email address.

sender filtering

Connection Filtering – Here you can add a Block List Service. Common one and free to use is Zen Spamhaus. Here is the configuration rule for using Zen – http://www.spamhaus.org/zen : The status codes hidden from the pictures are 127.0.0.7 and .8

Connection-Filtering

 

Recipient Filtering – You can block Exchange email addresses from receiving any emails. Also “Filter recipients who are not in the Directory” is important to be ticked, as this is filter mail sent to fictional users from your organization.

 

Intelligent Message Filtering – This is a filtering based on SCL ( Spam Confidence Level ). When turned on, every email coming to the Exchange Server will receive a SCL number based on examination of the Subject, Body , attachments and etc. Here you can specify how the IMF will react based on the SCL number. The lower the number the higher the restrictions. If you receive spam you could lower the number, if you have messages blocked that are good, you can increase it. You can also specify what the IMF should do if the threshold is met, like Reject, Accept, Archive or Take no Action. Below is the Store Junk E-mail Configuration where you specify the threshold for emails going to the Junk folder for users.

IMF

 

Sender ID Filtering – Sender ID is an e-mail industry initiative invented by Microsoft and a few other industry leaders. The purpose of Sender ID is to help counter Email spoofing, which is the number one deceptive practice used by spammers. Sender ID works by verifying every e-mail message indeed originates from the Internet domain from which it was sent. This is accomplished by checking the address of the server sending the mail against a registered list of servers that the domain owner has authorized to send e-mail. If Sender ID is used with its default option “Accept”, the email will be stamped and sent to the Intelligent Message Filtering and having a stamp from the Sender ID will reflect on the SCL generated by the IMF. If you want to go for it use this feature, fully read this article

Sender-ID

There is a hotfix if you have your exchange stop responding after enabling Sender ID –

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

IMPORTANT ! None of the above features will work unless turned on from the SMTP Virtual Server. Here is how:

smtp-virtual-server

smtp-virtual-server-properties