Exchange 2000 / 2003 – Exporting Mail to .pst files with ExMerge

KB ID 0000091

Problem

ExMerge has been around for a long time, its used (as the name implies) to merge pst files into existing mailbox’s. However its also a great tool to export/backup users mail box’s if you’re doing a migration, or if you have got your “Disaster Recovery” hat on.

The following is a run through of how to export from a mail store to pst files – Note on a live system this can take some time, the example below was done in VMware on a test Exchange box that had 1000 users (as it was a test server the mailbox’s were tiny) If you need to do this on a production server plan in a LOT of time if your moving a large amount of data.

Solution

 

Note: I’ve mentioned it in the video, but just to reiterate, your mailbox’s need to be smaller than 2GB, if that can not be achieved, you can either;

1. Use ExMerge and export particular “date ranges” and produce multiple .pst files for the same mailbox (hopefully less than 2GB).

2. Use Outlook 2007 (or greater) to export the mailbox to .pst files individually.

Related Articles, References, Credits, or External Links

Download ExMerge 

Exchange 2010 Bulk Import .pst Files

Exchange 2007 – Export Mailbox’s to PST files

Can I ‘Shrink’ My Exchange Database?

KB ID 0001706

Problem

Saw this asked in a forum today, and my response was;

It never gets smaller, if you delete things out of it, it just creates more ‘whitespace’ within the database, unless you;

a) Take it offline, and defragment it using eseutil.
b) Move the mailboxes out of it, to another database and delete it.

Which is true, but even Microsoft say you should not need to defragment a database! Before you do anything make sure you have a good backup of Exchange and the mailbox databases!

Defragment an Exchange Database

Stop! Why are you doing this, if it’s because you are running out of room, then migrating mailboxes out of a database into another database, on another piece of storage with more room is what you should be doing, and does not involve long periods of downtime!

If you have just deleted hundreds of GB from a mailbox database, and you simply want to compress the DB, and you have a BIG window for downtime, (allow 1 hour for every 9GB of database size). Then you are in about the only use case scenario I can think of to want to do this!

Before You start: This process creates a temporary mailbox database, (you need to tell it where), if you are pressed for room, I suggest you add another volume/drive and put it there. (Though in my example I have room in the same folder). Allow for the entire database’s existing size plus ten percent to be on the safe side.

Let’s have a look, and see how  much room we might be able to reclaim (whitespace);

[box]

Get-MailboxDatabase -Status | Select Name, DatabaseSize, AvailableNewMailboxSpace

[/box]

The database has to be dismounted before you can run Eseutil on it (downtime starts here).

[box]

Dismount –Database Database Name

Eseutil /d C:\Folder\DatabaseName.edb> /t T:\Folder\TempDB.edb>"

[/box]

When complete, mount the datastore again, (downtime ends here).

[box]

Mount-Database Database Name

[/box]

Hopefully you should see the whitespace has decreased.

Don’t forget to set off a full backup of the store as soon at it’s back online.

Move Mailboxes To Another Exchange Database (To Reclaim Space)

This is the much more elegant solution, create a shiny new database move everything  from the old database into the new one, and delete the old database.

Will This Impact My Users? Any user using their mailbox while it is getting moved wont be affected, until the move is complete then they will see a popup that looks like;

The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook.

Cool eh! So lets start by creating a New Mailbox Database.

[box]

New-MailboxDatabase -Name New Database Name -EdbFilePath C:\Folder\DB-Name.edb -LogFolderPath C:\Folder\Folder\

[/box]

Make sure you follow the advice and restart the information store, (yes you can mount the new DB and proceed, but Exchange does not allocate the resources correctly if you do this).

[box]

Restart-Service MSExchangeIS

[/box]

Let’s move our ‘Normal’ mailboxes to the new DB.

[box]

Get-Mailbox -Resultsize Unlimited | New-MoveRequest -TargetDatabase Target Database Name

[/box]

Depending on how many (and how large) mailboxes there are this can take a while, (days for large databases!) When they’ve all completed you need to remove the  move requests, (if you have any failures, or speed issues use the search box above, I’ve had to cope with thousands of these things not working correctly in my time!)

Let’s assume we are all moved, so we want to remove the move requests.

[box]

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

[/box]

Now let’s see if we have any Arbitration Mailboxes, we do so let’s shift them;

[box]

Get-Mailbox -Database Source Database Name -Arbitration

Get-Mailbox -Database Source Database Name -Arbitration | New-MoveRequest -TargetDatabase Target Database Name

[/box]

Again, when complete, remove the move requests.

[box]

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

[/box]

Now let’s see if we have any Auditlog Mailboxes, we do so let’s shift them;

[box]

Get-Mailbox -Database Source Database Name -Auditlog

Get-Mailbox -Database Source Database Name -Auditlog | New-MoveRequest -TargetDatabase Target Database Name

Get-MoveRequest | Get-MoveRequestStatistics

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

[/box]

Now let’s see if we have any Archive Mailboxes, we do NOT so I will skip them, let’s check for Monitoring Mailboxes, we have those so let’s move them;

[box]

Get-Mailbox -Database Source Database Name -Archive

Get-Mailbox -Database Source Database Name -Monitoring

Get-Mailbox -Database Source Database Name -Monitoring | New-MoveRequest -TargetDatabase Target Database Name

[/box]

And clean those up as before.

[box]

Get-MoveRequest | Get-MoveRequestStatistics

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

[/box]

Finally let’s see if we have any Public Folder Mailboxes, we have one of those so let’s move that;

[box]

Get-Mailbox -Database Source Database Name -PublicFolder

Get-Mailbox -Database Source Database Name -PublicFolder | New-MoveRequest -TargetDatabase Target Database Name
[/box]

We now need to remove the ‘Source‘ Database but first we need to dismount it.

[box]

Dismount-Database OLD Database Name

Remove-MailboxDatabase -Identity OLD Database Name

[/box]

I get an error message saying I cant delete the database.

 

Related Articles, References, Credits, or External Links

NA

Exchange: Can’t Delete a Database

KB ID 0001414

Problem

Every iteration of Exchange comes up with some new system/hidden mailbox type that stops me deleting mailbox databases!

[box]

This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or arbitration mailboxes, Audit mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all public folder mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -PublicFolder. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To get a list of all Audit mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -AuditLog. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -PublicFolder. To disable a Audit mailbox so that you can delete the mailbox database, run the command Get-Mailbox -AuditLog | Disable-Mailbox. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>.

[/box]

 

Solution

OK, I’m assuming you don’t actually have any mailboxes in the database? The following will tell you;

[box]Get-Mailbox -Database “Database-Name“[/box]

If you are running Exchange 2016 you might have an AudiLog account;

[box]Get-Mailbox -Auditlog -Database “Database-Name“[/box]

Or a Monitoring Mailbox

[box]Get-Mailbox -Monitoring -Server “Server-Name“[/box]

For 2013 (and older) the likely culprits are Arbitration, Archive, or Discovery Search mailboxes, (the latter you need an extra command to see).

[box]Get-Mailbox -Auditlog -Database “Database-Name” -Arbitration

Get-Mailbox -Auditlog -Database “Database-Name” -Archive

Set-AdServerSettings -ViewEntireForest $true

Get-Mailbox -Database “Database-Name“[/box]

To move a Discovery Search Malbox

[box]Get-Mailbox DiscoverySearchMailbox* | New-MoveRequest -TargetDatabase “Target-Database“[/box]

Also Exchange 2013 or Newer may have one or more Public folder mailboxes;

[box]Get-Mailbox -PublicFolder | New-MoveRequest -TargetDatabase “Target-Database“[/box]

I Can’t Find Anything and it still Wont Let Me Delete the Datastore?

Well, there’s two things you can do;

1. On a Domain Controller, 0pen ADSIEdit.msc and Connect to ‘Configuration’. Navigate to Configuration > Services > Microsoft Exchange > {Organisation name} > Administrative Groups > {Administrative-Group-Name} > Databases  >Delete the database from here (BE CAREFUL CHECK TWICE, DELETE ONCE!). Then have a coffee refresh you datastore view and the offender will disappear.

2. With the database dismounted, move its .edb file to another folder, then mount the store, it will complain and ask if you want to mount and empty store > select ‘yes’ > You can then delete it.

 

Related Articles, References, Credits, or External Links

NA

Exchange – Failed to mount database(hr=0x80040115, ec=-2147221227)

KB ID 0000664 

Problem

The Exchange server on my test network stopped working, the mailbox database was not mounted. When I attempted to mount it:

[box]
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database '{Database Name}'.
{Database Name}
Failed
Error:
Couldn't mount the database that you specified. Specified database: {Database Name}; 
Error code: An Active Manager operation failed with a transient error. Please retry 
the operation. Error: Database action failed with transient error. Error: A 
transient error occurred during a database operation. Error: MapiExceptionNetworkError: 
Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation Time: 2012-08-28 13:55:49:266
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string:
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115 [Database: {Database Name}, Server: 
PNL-EX.petenetlive.net].
An Active Manager operation failed with a transient error. Please retry the operation. 
Error: Database action failed with transient error. Error: A transient error occurred 
during a database operation. Error: MapiExceptionNetworkError: Unable to make admin 
interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation Time: 2012-08-28 13:55:49:266
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string:
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115 [Database: {Database Name}, 
Server: PNL-EX.petenetlive.net]
An Active Manager operation failed with a transient error. Please retry the operation. 
Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. 
(hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation Time: 2012-08-28 13:55:49:266
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string:
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115 [Server: PNL-EX.petenetlive.net]
MapiExceptionNetworkError: Unable to make admin interface connection to server. 
(hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation Time: 2012-08-28 13:55:49:266
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string:
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
[/box]


Solution

1. On closer inspection, I noticed the Exchange System Attendant was not running, and when I tried to launch it is started then stopped?

2. And the Exchange Information Store service was also not running, (that explains why the database won’t mount).

3. And when I tried to start that:

Error Windows could not start the Microsoft Exchange Information Store on Local Computer. For more information review the System Event Log. If this is a non Microsoft service, contact the service vendor, and refer to server-specific error code -2147221213

4. Fair enough, the Event Viewer yielded this:

Event ID 5003

Error
Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client 
and on the server machine are skewed. This may be caused by a time change either in the client or the 
server machine, and may require a reboot of that machine. Other than that, verify that your domain is 
properly configured and is currently online.

Well the clock on the Exchange server was correct, as were the clocks on the domain controllers they were both sync’d and in the same time zone.

5. The Exchange server is a VMware virtual machine, and even though it is not set to take it’s time from the host, the time on the host was incorrect.

6. Firstly set the time correctly on the ESX host, (below I’ve used an external NTP server, though you can just manually set the time).

7. Then restart the Exchange Active Directory Topology Service, make sure all the services come up correctly, and check the database has mounted.

Related Articles, References, Credits, or External Links

NA

Users Cannot Access Public Folders Post Migration (Exchange 2016)

KB ID 0001295 

Problem

This post comes form my colleague Andrew Dorrian, he usually follows my migrating public folders article. Recently after a couple of Exchange 2016 migrations he has seen a problem where the public folders are visible in the Exchange Admin Console, but the users can’t access them.

Solution

Open ADSIedit.msc and connect to the ‘Configuration’ context.

Navigate to;

CN=Services > CN=Microsoft Exchange > CN=(your organization name) > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Databases.

Locate you mailbox database(s) > Right Click > Properties > Locate: msExchHomePublicMDB  > Edit > Clear > OK > Apply > OK.

Open an Exchange administrative shell and run the following command;

[box]Set-OrganizationConfig -PublicFoldersEnabled Local[/box]

Note: Depending on the size of your organisation, you might want to wait a while for the changes to get replicated.

Related Articles, References, Credits, or External Links

NA

The name of the security certificate is invalid or does not match the name of the site

KB ID 0000036

Problem

Seen in Outlook when connecting to a mailbox on an Exchange Server, its caused by using a self signed certificate OR a purchased certificate, where the internal and external names are different.

The name of the security certificate is invalid or does not match the name of the site.

Solution

Before proceeding if you have an A or CNAME record in your DNS for autodiscover  then DELETE it and setup an SRV record!

Exchange AutoDiscover Errors – Creating an AutoDiscover SRV Record

1. On the Exchange Server > Start > All Programs > Microsoft Exchange Server {version} > Exchange Management Console. Issue the following four commands;

Exchange 2019 and 2016 (change the values in red)

Note: This uses the new Set-ClientAccessService commandlet, for older versions of Exchange use Set-ClientAccessServer.

[box]

Get-WebServicesVirtualDirectory -Server EXCHANGE-MAIL | Set-WebServicesVirtualDirectory -InternalUrl https://mail.publicdomain.co.uk/ews/exchange.asmx -ExternalURL https://mail.publicdomain.co.uk/ews/exchange.asmx

Set-OWAVirtualDirectory -identity "EXCHANGE-MAIL\owa (Default Web Site)" -InternalURL https://mail.publicdomain.co.uk/owa -ExternalURL https://mail.publicdomain.co.uk/owa

Get-OABVirtualDirectory -Server EXCHANGE-MAIL | Set-OABVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/OAB -ExternalURL https://mail.publicdomain.co.uk/OAB

Get-ECPVirtualDirectory -Server EXCHANGE-MAIL | Set-ECPVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/ECP -ExternalURL https://mail.publicdomain.co.uk/ECP

Get-MAPIVirtualDirectory -Server EXCHANGE-MAIL | Set-MAPIVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/MAPI -ExternalURL https://mail.publicdomain.co.uk/MAPI -IISAuthenticationMethods NTLM,Negotiate

Get-ActiveSyncVirtualDirectory -Server EXCHANGE-MAIL | Set-ActiveSyncVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/Microsoft-Server-ActiveSync -ExternalURL https://mail.publicdomain.co.uk/Microsoft-Server-ActiveSync

Set-OutlookAnywhere -identity "EXCHANGE-MAIL\RPC (Default Web Site)" -ExternalHostname mail.publicdomain.co.uk -InternalHostname mail.publicdomain.co.uk -InternalClientsRequireSSL $true -ExternalClientsRequireSsl $true -ExternalClientAuthenticationMethod:NTLM

Set-ClientAccessService -Identity EXCHANGE-MAIL -AutoDiscoverServiceInternalUri https://mail.publicdomain.co.uk/Autodiscover/Autodiscover.xml

[/box]

Exchange 2013 (change the values in red)

[box]

Set-ClientAccessServer -Identity EXCHANGE-MAIL -AutodiscoverServiceInternalUri https://mail.publicdomain.co.uk/autodiscover/autodiscover.xml
 
Get-WebServicesVirtualDirectory -Server EXCHANGE-MAIL | Set-WebServicesVirtualDirectory -InternalUrl https://mail.publicdomain.co.uk/ews/exchange.asmx -ExternalURL https://mail.publicdomain.co.uk/ews/exchange.asmx
 
Set-OWAVirtualDirectory -identity "EXCHANGE-MAIL\owa (Default Web Site)" -InternalURL https://mail.publicdomain.co.uk/owa -ExternalURL https://mail.publicdomain.co.uk/owa
 
Get-OABVirtualDirectory -Server EXCHANGE-MAIL | Set-OABVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/OAB -ExternalURL https://mail.publicdomain.co.uk/OAB
 
Get-ECPVirtualDirectory -Server EXCHANGE-MAIL | Set-ECPVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/ECP -ExternalURL https://mail.publicdomain.co.uk/ECP
 
Get-MAPIVirtualDirectory -Server EXCHANGE-MAIL | Set-MAPIVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/MAPI -ExternalURL https://mail.publicdomain.co.uk/MAPI -IISAuthenticationMethods NTLM,Negotiate
 
Get-ActiveSyncVirtualDirectory -Server EXCHANGE-MAIL | Set-ActiveSyncVirtualDirectory -InternalURL https://mail.publicdomain.co.uk/Microsoft-Server-ActiveSync -ExternalURL https://mail.publicdomain.co.uk/Microsoft-Server-ActiveSync
 
Set-OutlookAnywhere -identity "EXCHANGE-MAIL\RPC (Default Web Site)" -ExternalHostname mail.publicdomain.co.uk -InternalHostname mail.publicdomain.co.uk -InternalClientsRequireSSL $true -ExternalClientsRequireSsl $true -ExternalClientAuthenticationMethod:NTLM

[/box]

 

Exchange 2010 and SBS 2011 (change the values in red)

[box]

Set-ClientAccessServer -Identity EXCHANGE-MAIL -AutodiscoverServiceInternalUri https://mail.publicdomain.co.uk/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "EXCHANGE-MAIL/EWS (Default Web Site)" –InternalUrl https://mail.publicdomain.co.uk/EWS/Exchange.asmx

Set-OABVirtualDirectory -Identity “EXCHANGE-MAIL/OAB (Default Web Site)” -InternalURL https://mail.publicdomain.co.uk/OAB

Set-ActiveSyncVirtualDirectory -Identity “EXCHANGE-MAIL/Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL https://mail.publicdomain.co.uk/Microsoft-Server-Activesync

[/box]

Note:If you get repeated certificate prompts for ‘autodiscover.domain.com’ that should be from ‘mail.domain.com’, create an SRV record (_autodiscover) to redirect to mail.domain.con

Outlook Anywhere Note

If you intend to use Outlook Anywhere, you may also want to execute the following command. Particularly if you use SBS, which has a habit of setting remote.publicdomain.com as the default outside name.

[box] Set-WebServicesVirtualDirectory –Identity ‘EXCHANGE-MAIL/EWS (Default Web Site)’ –ExternalUrl https://mail.publicdomain.co.uk/ews/exchange.asmx[/box]

Exchange 2007 (change the values in red)

[box]

Set-ClientAccessServer -Identity EXCHANGE-MAIL -AutodiscoverServiceInternalUri https://mail.publicdomain.co.uk/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "EXCHANGE-MAIL/EWS (Default Web Site)" -InternalUrl https://mail.publicdomain.co.uk/ews/exchange.asmx

Set-OABVirtualDirectory -Identity "EXCHANGE-MAIL/oab (Default Web Site)" -InternalUrl https://mail.publicdomain.co.uk/oab

Set-UMVirtualDirectory -Identity "EXCHANGE-MAIL/unifiedmessaging (Default Web Site)" -InternalUrl https://mail.publicdomain.co.uk/unifiedmessaging/service.asmx

[/box]

For Small Business Server 2008

For SBS 2008 the commands are Different! (the following commands are for Exchange 2007 on SBS 2008 ONLY;

[box]

Set-ClientAccessServer -Identity EXCHANGE-MAIL -AutodiscoverServiceInternalUri https://mail.publicdomain.co.uk/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "EXCHANGE-MAIL/EWS (SBS Web Applications)" -InternalUrl https://mail.publicdomain.co.uk/ews/exchange.asmx

Set-OABVirtualDirectory -Identity "EXCHANGE-MAIL/oab (SBS Web Applications)" -InternalUrl https://mail.publicdomain.co.uk/oab

et-UMVirtualDirectory -Identity "EXCHANGE-MAIL/unifiedmessaging (SBS Web Applications)" -InternalUrl https://mail.publicdomain.co.uk/unifiedmessaging/service.asmx

[/box]

Note: where EXCHANGE-MAIL is internal and mail.publicdomain.co.uk is external name

2. Then open the IIS Manager Expand Application Pools > MSExchangeAutodiscoverAppPool > Right Click > Recycle.

Note: You may have to enter the FQDN of the server rather than its Netbios name!!

Related Articles, References, Credits, or External Links

Original article written 04/11/11 – Updated 07/03/13

Microsoft Exchange Server Build Numbers

KB ID 0000344

Problem

To find out what service pack and rollups have been applied to Microsoft Exchange you need to locate its “Build Number”.

2000/2003

2007

2010

Warning: After SP3 the build number does not update.

To find your build number in Exchange 2010 (after SP3,) use the following command;

exsetup | %{$_Fileversioninfo}

2019, 2016, and 2013

Find Exchange 2019 / 2016 and 2013 Build numbers from EMC (PowerShell)

Run the following PowerShell command;

[box]

Get-ExchangeServer | select Name,AdminDisplayVersion

[/box]

Exchange 2019 Build Numbers

Produce Name Build number Date KB
Exchange Server 2019 CU5 15.02.0595.003 17/03/2020  
Exchange Server 2019 CU4 15.02.0529.005 17/12/2019  
Exchange Server 2019 CU3 15.02.0464.005 17/09/2019  
Exchange Server 2019 CU2 15.02.0397.003 18/06/2019  
Exchange Server 2019 CU1 15.02.0330.005 12/02/2019  
Exchange Server 2019 RTM 15.02.0221.012 22/10/2018  
Exchange Server 2019 Preview 15.02.0196.000 24/07/2018  

Exchange 2016 Build Numbers

Produce Name Build number Date KB
Exchange Server 2016 Preview 15.1.225.16 22/06/2015  
Exchange Server 2016 RTM 15.1.225.42 28/09/2015  
Exchange Server 2016 Cumulative Update 1 15.1.396.30 14/03/2016 KB3134844
Exchange Server 2016 Cumulative Update 2 15.01.0466.034 21/06/16 KB3135742
Exchange Server 2016 Cumulative Update 3 15.01.0544.027 20/09/2016 KB3152589
Exchange Server 2016 Cumulative Update 4 15.01.0669.032 13/12/2016  
Exchange Server 2016 Cumulative Update 5 15.01.0845.034 13/12/2017  
Exchange Server 2016 Cumulative Update 6 15.01.1034.026 27/06/2017  
Exchange Server 2016 Cumulative Update 7 15.01.1261.035 19/09/2017 KB4018115
Exchange Server 2016 Cumulative Update 8 15.01.1415.002 19/12/2017 KB4035145
Exchange Server 2016 Cumulative Update 9 15.01.1466.003 20/05/2018 KB4055222
Exchange Server 2016 Cumulative Update 10 15.01.1531.003 19/06/2019 KB4471392
Exchange Server 2016 Cumulative Update 11 15.01.1591.010 16/10/2018

KB4134118

Exchange Server 2016 Cumulative Update 12 15.01.1713.005 12/02/2019  
Exchange Server 2016 Cumulative Update 13 15.01.1779.003 18/06/2019  
Exchange Server 2016 Cumulative Update 14 15.01.1847.003 17/09/2019  
Exchange Server 2016 Cumulative Update 15 15.01.1913.005 17/12/2019  
Exchange Server 2016 Cumulative Update 16 15.01.1979.003 17/03/2020  

Exchange 2013 Build Numbers

Product name Build number Date KB
Microsoft Exchange Server 2013 Preview 15.0.466.13 7/16/2012  
Microsoft Exchange Server 2013 RTM 15.0.516.32 10/11/2012  
Exchange Server 2013 Cumulative Update 1 (CU1) 15.0.620.29 04/27/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.0.1156.6 12/10/2015 KB3099522
Exchange Server 2013 Cumulative Update 12 (CU12) 15.0.1178.4 3/14/2016 KB3108023
Exchange Server 2013 Cumulative Update 13 (CU13) 15.00.1210.003 21/06/2-16 KB3135743
Exchange Server 2013 Cumulative Update 14 (CU14) 15.00.1236.003 20/09/2016 KB3177670
Exchange Server 2013 Cumulative Update 15 (CU15) 15.00.1263.005 13/12/2017  
Exchange Server 2013 Cumulative Update 16 (CU16) 15.00.1293.002 21/03/2017  
Exchange Server 2013 Cumulative Update 17 (CU17) 15.00.1320.004 27/06/2017  
Exchange Server 2013 Cumulative Update 18 (CU18) 15.00.1347.002 19/09/2017 KB4022631
Exchange Server 2013 Cumulative Update 19 (CU19) 15.00.1365.001 19/12/2017 KB4037224
Exchange Server 2013 Cumulative Update 20 (CU20) 15.00.1367.003 20/05/2018 KB4055221
Exchange Server 2013 Cumulative Update 21 (CU21) 15.00.1395.004 19/06/2019  
Exchange Server 2013 Cumulative Update 22 (CU22) 15.00.1473.003 12/02/2019 KB4345836
Exchange Server 2013 Cumulative Update 23 (CU23) 15.00.1497.002 18/06/2019 KB4489622

Exchange 2010 (SP3) Build Numbers

Product name Build number Date KB
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
Update Rollup 13 for Exchange Server 2010 SP3 14.3.294.0 3/14/2016 KB3141339
Update Rollup 14 for Exchange Server 2010 SP3 14.3.0301.000 14/06/2016 KB3151097
Update Rollup 15 for Exchange Server 2010 SP3 14.03.0319.002 20/09/2016 KB3184728
Update Rollup 16 for Exchange Server 2010 SP3 14.03.0336.000 13/12/2017  
Update Rollup 17 for Exchange Server 2010 SP3 14.03.0352.000 21/03/2017  
Update Rollup 18 for Exchange Server 2010 SP3 14.03.0361.001 11/07/2017  
Update Rollup 19 for Exchange Server 2010 SP3 14.03.0382.00 19/12/2017 KB4035162
Update Rollup 20 for Exchange Server 2010 SP3 14.03.0389.001 05/05/2018 KB4073537
Update Rollup 21 for Exchange Server 2010 SP3 14.03.0399.002 07/05/2018  
Update Rollup 22 for Exchange Server 2010 SP3 14.03.0411.000 19/06/2018 KB4295699
Update Rollup 23 for Exchange Server 2010 SP3 14.03.0417.001 13/08/2018 KB4340733
Update Rollup 24 for Exchange Server 2010 SP3 14.03.0419.000 05/09/2019 KB4458321
Update Rollup 25 for Exchange Server 2010 SP3 14.03.0435.000 08/01/2019 KB4468742
Update Rollup 26 for Exchange Server 2010 SP3 14.03.0442.000 12/02/2019 KB4487052
Update Rollup 27 for Exchange Server 2010 SP3 14.03.0452.000 09/04/2019 KB4491413
Update Rollup 28 for Exchange Server 2010 SP3 14.03.0461.001 07/06/2019 KB4503028
Update Rollup 29 for Exchange Server 2010 SP3 14.03.0468.000 09/07/2019 KB4509410
Update Rollup 29 for Exchange Server 2010 SP3 14.03.0496.000 11/02/2020 KB4536989

Exchange 2010 (SP2) Build Numbers

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-2 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 2010 (SP1) Build Numbers

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 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 2010 Build Numbers

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 KB982639

Exchange 2007 (SP3) Build Numbers

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
KB2530488
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
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 8 for Exchange Server 2007 SP3 08.03.0279.003
13/08/2012
 
Update Rollup 8-v2 for Exchange Server 2007 SP3 08.03.0279.005 09/10/2012  
Update Rollup 8-v3 for Exchange Server 2007 SP3 08.03.0279.006 13/11/2012  
Update Rollup 9 for Exchange Server 2007 SP3 08.03.0297.002 10/12/2012  
Update Rollup 10 for Exchange Server 2007 SP3 08.03.0298.003 11/02/2013  
Update Rollup 11 for Exchange Server 2007 SP3 08.03.0327.001 13/08/2013  
Update Rollup 12 for Exchange Server 2007 SP3 08.03.0342.004 09/12/2013  
Update Rollup 13 for Exchange Server 2007 SP3 08.03.0348.002 24/02/2014  
Update Rollup 14 for Exchange Server 2007 SP3 08.03.0379.002 26/08/2014  
Update Rollup 15 for Exchange Server 2007 SP3 08.03.0389.002 09/12/2014  
Update Rollup 16 for Exchange Server 2007 SP3 08.03.0406.000 17/03/2015  
Update Rollup 17 for Exchange Server 2007 SP3 08.03.0417.001 17/06/2015  
Update Rollup 18 for Exchange Server 2007 SP3 08.03.0445.000 01/12/2015  
Update Rollup 19 for Exchange Server 2007 SP3 08.03.0459.000 15/03/2016  
Update Rollup 20 for Exchange Server 2007 SP3 08.03.0468.000 21/06/2016 KB3151086
Update Rollup 21 for Exchange Server 2007 SP3 08.03.0485.001 20/09/2016 KB3184711
Update Rollup 22 for Exchange Server 2007 SP3 08.03.0502.000 13/12/2016  
Update Rollup 23 for Exchange Server 2007 SP3 08.03.0517.000 21/03/2017  

Exchange 2007 (SP2) Build Numbers

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

Exchange 2007 (SP1) Build Numbers

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  
Update Rollup 2 for Exchange Server 2007 Service Pack 1 8.1.278.2 5/8/2008  
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 2007  Build Numbers

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  

Exchange 2003 Build Numbers

Exchange Server 2003
Product name Build number Date  
Microsoft Exchange Server 2003 6.5.6944 6/30/2003  
Microsoft Exchange Server 2003 SP1 6.5.7226 5/25/2004  
Microsoft Exchange Server 2003 SP2 6.5.7638 10/19/2005  

 

Related Articles, References, Credits, or External Links

NA

SEM – SPAMfighter Exchange Module – Installation and Configuration with Exchange 2013

KB ID 0000824 

Problem

“I seem to get a lot of spam”, and “I get a lot more spam than I used to” are right up there with “My computer is running slow”. It’s a problem that, eats up users time and fills your mail stores with junk, and time/disk space costs money.

SEM is tiny! In a world where a graphics driver is now over 100MB the entire install suite is less than 11MB. This is going into my test network so testing its ability to limit spam is NOT the point of this exercise, I’m looking at the ease of installation, configuration, and administration.

SEM Pre-Requisites

1. Exchange 2000, 2003, 2007, 2010, or 2013.

2. Windows Server 2000, 2003, 2003 R2, 2008, 2008 R2, or 2012.

3. .Net framework version 2.0 (SP1).

4. MDAC (Microsoft Data Access Components) version 2.7.

5. Internet Information Services.

Solution

Before You Start

1. If you have already installed the Microsoft Anti Spam agents you might want to remove them, (not that you have to). If you don’t know you can run the following command;

[box]
Get-TransportAgent[/box]

If you just have the four below then you DO NOT have the extra agents installed.

2. If yours looks like the one below, then YOU DO have them installed.

3. As stated you don’t have to remove them but if you want to simply execute the following two commands;

[box]

cd "Program FilesMicrosoftExchange ServerV15Scripts"
./Uninstall-AmtispamAgents.ps1

[/box]

4. Answer each question, then run;

[box]
services.msc[/box]

5. Restart the Microsoft Exchange Transport service.

Install SPAMfighter

6. Download the installer, and run it.

7. The installer is pretty straight forward > Next > Accept the EULA > Next > Enter your details > Next > Accept or change the install location > Next.

8. The product will install.

9. At this point it’s downloading definitions form the internet, and it will take a while.

10. When complete it needs to setup a user that the services will run under. Just supply a password > Next.

Note: This user (by default) is added to the local administrators group, and the Exchange Organization Management group.

11. Finish.

12. The management console installs on TCP port 5000, so if you need to access it through a firewall you will need to open that port.

13. Toolbars Tab: From here, I’ll jump straight to the configuration section, this drops you straight onto the Plugins tab. From here you can change the logo that will be displayed with the toolbar (this is NOT visible with Outlook 2013). You can also change the URL it points to and adding rights to users.

14. Toolbar Tab > Outlook Toolbar: On a client running Outlook > Download Outlook Toolbar > Run the installer.

Note: The installer is a .exe file, I would have preferred a .msi file, so I could deploy this out (on mass), to domain clients via GPO.

15. Next > Accept the EULA > Next > Next.

16. Finish.

17. Now when you launch Outlook you can see the plugin loading.

18. You will now have an extra toolbar with the following options.

BE AWARE: You install the OWA toolbar ONCE on the Exchange CAS server.

19. Toolbars > Outlook Web Application: Install OWA toolbar.

20. Yes.

21. Now when your clients access OWA, you have the toolbar.

22. Latest news: Essentially this is just an RSS feed from the manufacturer to keep you abreast of software updates etc. If you have some RSS aggregation software you can add this same feed.

23. Mailbox Tab > Mailboxes: Here it will list all the mailboxes, by default the ‘Default policy’ will be applied and virus filtering will NOT be enabled (this is an add on license). you can also access statistics for this particular mailbox, and view quarantined emails. The User filter settings are for applying an exception for this one mailbox (I’ll cover this later). If you can’t locate a particular user there is also a search function.

24. Mailbox Tab > Usergroups: Usergroups are used to apply policies, any new group requires you to maintain membership manually. But if your Active Directory is well designed, you can select your SPAMfighter groups based on your OU structure.

SEM – SPAMfighter – Configuring and Working with Policies

This is pretty intuitive, and the default policy comes preconfigured and already applied, though with all filtering systems it will probably take you a little while to get it streamlined to your requirements. The policies section has four main tabs;

Filter Settings: What tools you are going to use to look for spam.
Accept Actions: What it will do if it finds nothing.
Block Actions: What it will do if it finds something.
User Filter settings: Exceptions to the filters for one or more users.
Mailboxes: Puts you straight back to the mailbox section you saw earlier.

25. Out of the box there are five filters enabled.

26. But there are four further filters that you can add to the policies.

SPAMfighter – Filters

27. VIRUSfighter Antivirus Filter for SPAMfighter Exchange Module: Remember this is an ‘Add on’ so it would only apply to mailboxes that have this enabled. It’s on its most conservative setting, and will replace the infected email with safe content.

28. SPAMfighter Sender Filter > Whitelist:Simply add either a particular email address you want to allow or add in an entire domain.

29. If your lists get a little unwieldy you can import or export them, and chose weather to overwrite them or append the imported list to your existing list.

30. And where there is a Whitelist there is a Blacklist, it’s configured exactly the same.

31. Automatic Whitelist: This is a brilliant feature! It dynamically adds the addresses our users send to to the Whitelist, and maintains the cache for 10 days (which you can alter). I’m surprised this is disabled by default.

Note: This will be enabled by default in the next release.

32. SPAMfighter Content Filter > Whitelist phrases: Gives you the power to automatically Whitelist emails based on a phrase they contain i.e. Your corporate email disclaimer or default signature.

33. SPAMfighter Content Filter > Blacklist phrases: As the warning says be careful with this section, this is the sort of thing that is handy for blocking “We attempted to deliver your parcel but were unable to” emails that urge you to click an attached zip file full of infected spyware nastiness.

34. SPAMfighter Content Filter > Whitelist Attachments: Here you can upload an attachments (like your company logo from your email signatures) and the system will whitelist and allow through emails containing them.

35. SPAMfighter Content Filter > Blacklist Attachments: Thankfully this is disabled by default, the list of file extensions is quite long, and contains some commonly used file extensions, You will need to do some planning and testing with this one if you want to enable it.

36. SPAMfighter Community Filter: This will filter mail based on mails that have already been blocked by other SPAMfighter users, it uses a scoring/weighting system. You simply set a threshold the higher you set it the more mail will be stopped, this will require some fine tuning.

37. SPAMfighter Language Filter:This is enabled by default, but no languages are selected (which is sensible). If you are never expecting any emails in Chinese you can block them here.

SPAMfighter Filters that you can Manually Add to the Policy.

38. SPAMfighter IP-address Filter: Pretty much does what it says on the tin! Though blocking spammers by IP address is a little hard to manage, and it’s pretty easy to spoof an IP address anyway, which is probably when this is not on the default policy.

39. SPAMfighter Sender Policy Framework Filter: Personally I think you would be crazy to turn this on! If you don’t know what an SPF record is then read the following article.

Setting up the Correct DNS Records for your Web or Mail Server

40. SPAMfighter DNSBL Filter: A DNSBL is a dynamic DNS list of known spammers, if you are familiar with RBL block lists this is similar.

41. SPAMfighter Combined Spam Score Filter: All the other filters check the mail and give it a score, if the score is higher than a certain threshold this this filter will aggregate all those scores and block the mail.

SPAMfighter – Policies > Accept Actions

42. If the mail makes it through all the filters, then this section decides what happens with it.

43. And that is adding information to the mail header that says the mail was scanned and accepted.

SPAMfighter – Policies > Block Actions

44. If the mail gets blocked by any of the filters, this section decides how that is handled.

Note: You can add other actions from the drop-down list below if this does not do what you require.

45. Just as for the accept policy action, this modifies the email header, though this one says the mail was blocked.

46. SPAMfighter Move To Folder Policy Action > Mailboxes : The second default policy action takes that filtered email and places it within a folder called SPAMfighter within the users mailbox.

Note: You can redirect that mail to another mailbox if that is your preference.

47. The system for Public Folders (if you use them) is identical.

48. Contacts: As is says contacts do not have a mailbox, but you can redirect filters contact mail to a specific mailbox should you wish.

49. User Filter Settings: This section can create an exception for one particular user, it simply creates another policy that you can apply to that user.

50. You can create new policies and apply then to particular users or usergroups, and make the system as granular as you like.

51. Statistics: On my test network I didn’t have any throughput on which to pull some meaningful statistics.

52. Statistics > Notifications: You can have daily/weekly/monthly reports emailed to you.

53. If you decide to purchase, the licenses are priced per mailbox. Prices start at £14.50 each (or £29.00 with the Antivirus) And go down to £2.45 (or £4.90 with Antivirus) depending on the amount you buy. They are available for 1, 2, and 3 year periods. For an up to date price list go here.

Related Articles, References, Credits, or External Links

NA