*****************
* CONFIGURATION *
*****************

This version of the sa-exim package defaults to placing a configuration
sniplet in /etc/exim4/conf.d/. Depending on what you have answered to the
DebConf questions while configuring Exim4, the module will be loaded
automatically, or human intervention is required.

To find out what configurationfile Exim4 is using, issue:

  $ exim4 -bV | tail -1
  Configuration file is /path/to/configfile

If /path/to/configfile shows:

  - /etc/exim4/exim4.conf
    You are using the 'monolithic' configuration file.
	See the 'MONOLITHIC' section below.
	
  - /var/lib/exim4/config.autogenerated 
    You are using the 'split' configuration file.
	See the 'SPLIT' section below.


MONOLITHIC
----------

Use 'grep "local_scan_path" /etc/exim4/exim4.conf" to see if the sa-exim
line is included in the configuration. If grep returns something, check
if it matches the following line. If grep returns nothing, you have to
manually add the following line to the exim4.conf file and restart exim4.

    local_scan_path = /usr/lib/exim4/local_scan/sa-exim.so

Change or add the line above and manually restart exim4 by issuing
'invoke-rc.d exim4 restart' or '/etc/init.d/exim4 restart' as root.


SPLIT
-----

Use 'grep "local_scan_path" /var/lib/exim4/config.autogenerated' to see
if the sa-exim line is included in the configuration. If grep returns
something, you're set and already using the sa-exim module. If grep
returns nothing, we need to figure out a few things:

Issue:
	$ grep "use_split_config" /etc/exim4/update-exim4.conf.conf 
      dc_use_split_config='true'

If your result shows 'false' where mine shows 'true', but the check
earlier showed that you *are* in fact using the split configuration,
then you have to edit /etc/exim4/update-exim4.conf.conf by hand and
change the 'false' to 'true' and issue 'update-exim4.conf' as root.
Next, check again if the sa-exim module-line is included. It should.
If it still isn't: mail me. If it is, restart exim4 by issuing
'invoke-rc.d exim4 restart' or '/etc/init.d/exim4 restart' as root.

Next, read all about greylisting and sa-exim:

***************
* GREYLISTING *
***************
Notes on greylisting with sa-exim.

If you use SpamAssassin 3.0 or better, you do not need to patch it, you
can just use the Greylisting module shipped with sa-exim. 
The only thing you need to do to enable it, is to copy the 4 lines below
loadplugin in the greylisting README, and adjust the score if you wish (see
README.Greylisting for details)


If you use a version of SA older than 3.0, you will need to patch
spamassassin's sources to support greylisting.

There are two versions of the patches: 
 - /usr/share/doc/sa-exim/patches/SA-greylisting-2.4x.diff 
   This patch can be applied to versions 2.4x of SpamAssassin. Note
   that this patch is not fully functional anymore, it is just left as
   a template should you want to backport the current 2.6x patch. 
   That said, you really ought to upgrade SA to 2.6x or 3.x

 - /usr/share/doc/sa-exim/patches/SA-greylisting-2.6.diff 
   This patch can be applied to versions 2.6x of SpamAssassin.

Please read README.Greylisting for more information on how to enable
this feature, and what further changes are needed.
Note that this configuration won't be supported in the future, and you
are encouraged to upgrade to SA 3.0 or better.

*************
* BE WARNED *
*************

By applying these patches, you change the sourcecode of SpamAssassin
(again, this is if you use a version of SpamAssassin earlier than 3.0)
This also means that when the SpamAssassin package gets upgraded, the
changes made by the patch are LOST. 
This *MIGHT* cause your mail setup to break. It might be best to put
SpamAssassin on hold:

  $ echo "spamassassin hold" | dpkg --set-selections

You can later set it to install again with:

  $ echo "spamassassin install" | dpkg --set-selections