Version 4.00.0a4

Julian Field mailscanner at ecs.soton.ac.uk
Mon Sep 23 14:56:51 IST 2002


At 14:43 23/09/2002, you wrote:
>Thanks
>
>If I start with "Load SpamAssasin = yes" I get
>
>Can't locate Mail/SpamAssassin.pm in @INC (@INC contains:
>/opt/MailScanner/bin /usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
>/usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
>/usr/lib/perl5/site_perl .) at MailScanner/SA.pm line 69

Have you installed SpamAssassin? If not, then I would fully expect "Load
SpamAssassin=yes" to fail.

>Also just noticed I got
>
>We haven't got any child processes, which isn't right!, No child processes
>at /opt/MailScanner/bin/mailscanner line 174.
>We have just tried to reap a process which wasn't one of ours!, No child
>processes at /opt/MailScanner/bin/mailscanner line 177.

This is because it is aborting while trying to load SpamAssassin. If you
haven't got it installed, then clearly(?) you need to set "Load
SpamAssassin = no".

>Seems fine if I set to "Load SpamAssasin = no"
>
>I dont have spamassasin installed.

Aha! Don't tell it to load software you haven't got. Surprisingly enough it
fails :-)
>----- Original Message -----
>From: <mailto:mailscanner at ECS.SOTON.AC.UK>Julian Field
>To: <mailto:MAILSCANNER at JISCMAIL.AC.UK>MAILSCANNER at JISCMAIL.AC.UK
>Sent: Monday, September 23, 2002 2:22 PM
>Subject: Re: Version 4.00.0a4
>
>At 12:49 23/09/2002, you wrote:
>>Just trying it out on a totally fresh server.
>>
>>Looks really good, comments are
>>
>>1. Sophos.install - does not point to the new location for sophos-wrapper
>>and sophos-autoupdate scripts.
>Fixed.
>
>>2. If "Use SpamAssassin = no" and "Load SpamAssassin = yes" in
>>mailscanner.conf, it does try to use spamassasin. I would have expected
>>the "Use SpamAssassin = no" to have precedence.
>Does it try to use it, or just try to load it?
>Working out whether "Use SpamAssassin" is yes or no is no longer easy
>because it could be a ruleset rather than a simple value. That's why I put
>in the "Load SpamAssassin" option in, as that has to be just yes or no.
>
>>Im very interested in the ability to do different signatures for
>>different domains, and will be trying that out next, I was looking at the
>>example and it seemed to apply for outgoing mail only e.g.
>>
>>    From:        <mailto:*@domain1.com>*@domain1.com
>> /opt/MailScanner/etc/reports/domain1.sig.txt
>>    From:        <mailto:*@domain2.com>*@domain2.com
>> /opt/MailScanner/etc/reports/domain2.sig.txt
>>
>>Does this work for for To: as well? e.g.
>>
>>     To:        <mailto:*@domain1.com>*@domain1.com
>> /opt/MailScanner/etc/reports/domain1.sig.txt
>>     To:        <mailto:*@domain2.com>*@domain2.com
>> /opt/MailScanner/etc/reports/domain2.sig.txt
>You can have "from", "to" or "fromto" or "tofrom" etc in the first field.
>It just looks at the first word for the word "from" and for the word "to"
>so if you want both then you can combine them how you like. So I would do
>         FromTo:         *@domain1.com
> /opt/MailScanner/etc/reports/domain1.sig.txt
>         FromTo:         *@domain2.com
> /opt/MailScanner/etc/reports/domain2.sig.txt
>
>Don't forget to set the HTML sigs as well as the txt ones.
>--
>Julian Field                Teaching Systems Manager
>jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
>Tel. 023 8059 2817          University of Southampton
>                             Southampton SO17 1BJ
>--
>This message has been scanned for viruses and
>dangerous content by <http://www.mailscanner.info/>MailScanner, and is
>believed to be clean.
>
>
>--
>This message has been scanned for viruses and
>dangerous content by <http://www.mailscanner.info/>MailScanner, and is
>believed to be clean.

--
Julian Field                Teaching Systems Manager
jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
Tel. 023 8059 2817          University of Southampton
                             Southampton SO17 1BJ



More information about the MailScanner mailing list