[Martin Hepworth]

The autowhitelist is depreciated for a long time now

Just disable that plugin in the spamassasin config files

On Friday, 22 March 2013, Robert Lopez wrote:

> Here is the definitive answer for anyone who later finds this thread.
> It is from the file /usr/share/doc/mailscanner/examples/conf.d/README
>
>
> # In this directory, you can put files that will be automatically included
> # as if they were inserted at the end of the main MailScanner.conf file
> # in the directory above this one.
> #
> # They should be read in alphabetical order.
> #
> # NOTE: If you change the value of a %variable% then you must redefine all
> # the settings that use that %variable% here, as the %variable%
> # substitutions are done when the files are initially read, not later when
> # settings are looked up when MailScanner is processing messages.
> # So if, for example, you change the value of %rules-dir% in an included
> # file here, you must reset the values of the settings
> #        Maximum Message Size
> #        Is Definitely Not Spam
> #        Enable Spam Bounce
> # in order for them all to use the new value of %rules-dir%.
> # My apologies for this, but it is only possible to know the values of
> # each %variable% when the configuration files are read, and not when
> # the settings are evaluated as they could be set at any point within the
> # files, giving an unknown value of the %variable% at that point.
> #
> # --
> # Jules
> # MailScanner at ecs.soton.ac.uk <javascript:_e({}, 'cvml',
> 'MailScanner at ecs.soton.ac.uk');>
>
> So before modifying any %something% line in a conf.d/ file grep for
> that %something% string in the .../MailScanner/MailScanner.conf file
> and modify all of them.
>
>
>
> On Fri, Mar 22, 2013 at 4:19 PM, Robert Lopez <rlopezcnm at gmail.com> wrote:
>
> I am terribly wrong.
> I have been able to prove to myself the configuration file
> /etc/MailScanner/conf.d/CNM-MailScanner.conf is read and affects many
> configuration parameters.
>
> However this line:
> %org-name% = CNM
> does not take precedence over this line in
> /etc/MailScanner/MailScanner.conf:
>  %org-name% = unconfigured-debian-site
> So all the places it should modify other configuration parameters they are
> not modified.
> When I look in the internet headers of email passed through I see lines
> like these:
> X-unconfigured-debian-site-MailScanner-From: xxxxxxxxxx at yyyyyyyy.zzzz
> X-unconfigured-debian-site-MailScanner: Found to be clean
> X-unconfigured-debian-site-MailScanner-ID: 7E9D75F8D.AA75F
>
>
>
> On Fri, Mar 22, 2013 at 10:20 AM, Robert Lopez <rlopezcnm at gmail.com>wrote:
>
> Martin,
>
> I had done that. There are some "errors"; part related to the fact the
> local conf file is not loaded.
>
> The first error is
> ERROR: The "envelope_sender_header" in your spam.assassin.prefs.conf
> ERROR: is not correct, it should match
> X-unconfigured-debian-site-MailScanner-From
> and it is because the /etc/MailScanner/conf.d/CNM-MailScanner.conf file
> sets
> envelope_sender_header X-CNM-MailScanner-From
>
> The second error/warning is
> config: failed to parse line, skipping, in
> "/etc/MailScanner/spam.assassin.prefs.conf": use_auto_whitelist 0
> SpamAssassin reported an error.
> which I have never been able to understand, but is there because I want
> the whitelist off. Also
> I assume the "SpamAssassin reported an error" refers to the line above it.
>
> The result of the run is below.
>
>
>
> # MailScanner -debug --lint
> Trying to setlogsock(unix)
>
>
> Reading configuration file /etc/MailScanner/MailScanner.conf
> Reading configuration file /etc/MailScanner/conf.d/CNM-MailScanner.conf
> Read 869 hostnames from the phishing whitelist
> Read 5414 hostnames from the phishing blacklists
>
> Checking version numbers...
> Version number in MailScanner.conf (4.84.5) is correct.
>
> ERROR: The "envelope_sender_header" in your spam.assassin.prefs.conf
> ERROR: is not correct, it should match
> X-unconfigured-debian-site-MailScanner-From
>
> MailScanner setting GID to  (117)
> MailScanner setting UID to  (108)
>
> Checking for SpamAssassin errors (if you use it)...
> Using SpamAssassin results cache
> Connected to SpamAssassin cache database
> config: failed to parse line, skipping, in
> "/etc/MailScanner/spam.assassin.prefs.conf": use_auto_whitelist 0
> SpamAssassin reported an error.
> I have found clamd scanners installed, and will use them all by default.
> Connected to Processing Attempts Database
> Created Processing Attempts Database successfully
> There are 0 messages in the Processing Attempts Database
> Using locktype = posix
> MailScanner.conf says "Virus Scanners = auto"
> Found these virus scanners installed: clamd
> ===========================================================================
> Filename Checks: Windows/DOS Executable (1 eicar.com)
> Other Checks: Found 1 problems
> Virus and Content Scanning: Starting
> Clamd::INFECTED::Eicar-Test-Signature :: ./1/
> Clamd::INFECTED:: Eicar-Test-Signature :: ./1/eicar.com
> Virus Scanning: Clamd found 2 infections
> Infected message 1 came from 10.1.1.1
> Virus Scanning: Found 2 viruses
> ===========================================================================
> Virus Scanner test reports:
> Clamd said "eicar.com was infected: Eicar-Test-Signature"
>
> If any of your virus scanners (clamd)
> are not listed there, you should check that they are installed correctly
> and that MailScanner is finding them correctly via its virus.scanners.conf.
>
>
>
>
>
> On Fri, Mar 22, 2013 at 5:43 AM, Martin Hepworth
>
>

-- 
-- 
Martin Hepworth, CISSP
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20130323/bbd4d356/attachment.html