In this step by step example I am upgrading SpamAssassin version 3.0.3-4.fc4 to 3.2.5 on my Fedora 4 server.

After you download the lastest version, build the rpm using this file, the command to do that is below.

sudo rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz

This will create two files, perl-Mail-SpamAssassin-3.2.5-1.i386.rpm and spamassassin-3.2.5-1.i386.rpm in the folder /usr/src/redhat/RPMS/i386.

Install this file first with the following command,

rpm -i perl-Mail-SpamAssassin-3.2.5-1.i386.rpm

Uninstall Evolution first because it dependencies that relies on Spamassassin 3.0.3-4.fc4, otherwise you will receive an error when uninstalling SpamAssassin version 3.0.3. Evolution is an email client for Linux, similar to Outlook for Windows.

Uninstall in the following order:
rpm -e evolution-connector-2.2.2-5.i386
rpm -e evolution-devel-2.2.2-5.i386
rpm -e evolution-2.2.2-5.i386

Check to see whcih version of Spam Assassin is installed.

rpm -q spamassassin
spamassassin-3.0.3-4.fc4

To uninstall run this command.

rpm -e spamassassin-3.0.3-4.fc4

You will see this warning message.
warning: /etc/mail/spamassassin/spamassassin-default.rc saved as /etc/mail/spamassassin/spamassassin-default.rc.rpmsave

Confirm that SpamAssassin has been uninstalled.
rpm -q spamassassin
package spamassassin is not installed

Now install the new version of SpamAssassin.

rpm -i spamassassin-3.2.5-1.i386.rpm

Check to see if the installation was successful.
rpm -q spamassassin
spamassassin-3.2.5-1

Now copy this file that was renamed during the uninstallation of the previous version.
cp -i spamassassin-default.rc.rpmsave spamassassin-default.rc

If you are interested here is the contents of the file spamassassin-default.rc.
# send mail through spamassassin
:0fw
| /usr/bin/spamassassin
# Drop all spam emails to /dev/null
:0:
* ^X-Spam-Status: Yes
/dev/null
# send mail through spamassassin
:0fw
| /usr/bin/spamassassin
# Drop all spam emails to /dev/null
:0:
* ^X-Spam-Status: Yes
/dev/null

The final step is to start the SpamAssassin service.

service spamassassin start
Starting spamd: [ OK ]

If you wish you can now download and install the latest version of Evolution from projects.gnome.org/evolution. I may do that sometime, as I do not use it.

Well after I completed the above steps, it seems that SpamAssassin was not working. I then decided to read the documentation avaiable on the website. I guess I should have doen that first.

Anyhow, these are the steps I missed. Edit the file /etc/mail/spamassassin/local.cf.

Remove the comment (#) from these lines as shown below

# Add *****SPAM***** to the Subject header of spam e-mails
#
rewrite_header Subject *****SPAM*****

# Bayesian classifier auto-learning (default: 1)
#
bayes_auto_learn 1

Then edit the file /etc/mail/spamassassin/spamassassin-default.rc, and add these lines if it’s not there.

# send mail through spamassassin
DROPPRIVS=yes

:0fw
| /usr/bin/spamassassin

Restart spamd.
service spamassassin restart

When configuring a new Exchange server it is recommended that a new Recipient Policy be created, instead of using the Default Policy. Here is how you can configure or change the recipent policy.

The below is an excerpt from Microsoft Tech Net.

To modify any recipient policy:
Start Exchange System Manager.
Click Organization, click Recipients, and then click Recipient Policies.
Double-click the policy that you want to change. If you are going to generate your SMTP address by using the replacement strings listed below, do not modify your Default Policy. You may encounter problems if the Default Policy is based upon attributes such as Given Name or Surname.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
271339 (support.microsoft.com/kb/271339/EN-US/ ) XADM: Cannot Mount Database and Event ID 9546 Occurs
Click the E-Mail Addresses tab, and then edit the appropriate SMTP Generation rule by using the following switches.

The default format is:
user_name@domain_name.com
The following replacement strings are available:
%s = surname (last name)
%g = given name (first name)
%i = middle initial
%d = display name
%m = Exchange 2003 or Exchange 2000 Alias
%rxy = Replace all subsequent characters x with character y in username. If x = y, then the character will be deleted.
You can place a number in front of any of the preceding switches to define how many characters of the switch should be used, for example:
%1s = Uses the first letter of the surname
%5g = Uses the first five letters of the given name
NOTE: Invalid characters (in accordance with Request for Comments [RFC] 821/822) are removed from the user’s name.
More Information on the %r Replacement String
If a %r is used for the purpose of substituting a valid character for an invalid character, the entire %r string is ignored. Additionally, %r should be used immediately before replacement string where you want to replace characters.

Therefore, in cases in which you want to replace character “x” with character “y” in the last name (represented with %s) an SMTP e-mail address is generated as follows:
%g.%s
The proper use of %r replacement string is:
%g.%rxy%s
Putting %rxy in front of the whole e-mail will not work properly in the above case and will not replace character “x” with “y” in the last name.

NOTE: When using the %rxy string, x can equal blank space. This string can be used to merge spaces in the name with a valid character.

NOTE: You cannot use the %rxy string as %r to remove manually typed periods from the Initials field in Active Directory Users and Computers. We recommend that the manually typed period be removed from the Initials field in Active Directory as this also affects other attributes.
Back to the top
Examples for User Logon Name = “AndrewLin”
Display name = “Andrew Lin”
Surname = “Lin”
Given name = “Andrew”
Format string SMTP address generated for sample user
————- ————————————–
%d@microsoft.com HollyEBarrett@microsoft.com
%r._%d@microsoft.com HollyE_Barrett@microsoft.com
%r..%d@microsoft.com HollyE.Barrett@microsoft.com
%g.%s@microsoft.com Holly.Barrett@microsoft.com
@microsoft.com HollyB@microsoft.com
%1g%s@microsoft.com HBarrett@microsoft.com
%1g%4s@microsoft.com HBarr@microsoft.com

282314 (support.microsoft.com/kb/282314/ ) Site addressing generates incorrect SMTP address for “%g.%s.%m”

Open Exchange System Manager

Go to Administrative Groups – First Administrative Group – Servers – Server_Name – First Storage Group – Mailbox Store – Mailboxes.

This will display all the mailboxes, you can determine the current size of each mailboxes. This screen also provides a quick way to determine basic security auditing information such as, last logon by, logon time and logoff time.

This is due to the delay in the Recipient Update Services. Depending on the size and complexity of your Microsoft Windows server network and the number of domain controllers, it may take a few minutes to many hours to initiate and complete the Recipient Update Services process. If you are not in a rush, then simply wait until the next day to configure the Outlook client.

If you do not have the patience to wait or you simply must get Outlool email working for a new user, then there is a solution. The Recipient Update Serives can manually be initiated to speed up the process.

Below is the instructions on how to manually force the Recipient Update Services to initiate.

Open Exchange System Manager

Click on Recipients – Recipient Update Services. In the right windows, right click Recipient Update Service and select Update Now.