From garry at glendown.de Fri Dec 8 08:08:30 2017
From: garry at glendown.de (Garry Glendown)
Date: Fri, 8 Dec 2017 09:08:30 +0100
Subject: Postfix & vacation notice
Message-ID: <76983855-37bd-28ff-2b2f-f673a19294f2@glendown.de>
Hi,
on an installation with Postfix as MTA I have Mailscanner running, so
far without any problems. As MS is being used to add signatures to
outgoing mails, we noticed that on vacation notices no signatures were
attached - which is caused by the fact that Postfix automatically
generates the notice and sends it without going through the "regular"
queueing of the message ... is there any way of fixing this?
Thanks, -garry
--
PGP Fingerprint: A79F A33F 5B13 BEB7 A51D 274F F99C 3AE2 4BCB 7015
From Antony.Stone at mailscanner.open.source.it Fri Dec 8 09:03:34 2017
From: Antony.Stone at mailscanner.open.source.it (Antony Stone)
Date: Fri, 8 Dec 2017 10:03:34 +0100
Subject: Postfix & vacation notice
In-Reply-To: <76983855-37bd-28ff-2b2f-f673a19294f2@glendown.de>
References: <76983855-37bd-28ff-2b2f-f673a19294f2@glendown.de>
Message-ID: <201712081003.34824.Antony.Stone@mailscanner.open.source.it>
On Friday 08 December 2017 at 09:08:30, Garry Glendown wrote:
> Hi,
>
> on an installation with Postfix as MTA I have Mailscanner running, so
> far without any problems. As MS is being used to add signatures to
> outgoing mails, we noticed that on vacation notices no signatures were
> attached - which is caused by the fact that Postfix automatically
> generates the notice and sends it without going through the "regular"
> queueing of the message ... is there any way of fixing this?
Get the "other" instance of Postfix (ie: the one putting the mails into the
queue directory for MailScanner to process) to generate the messages, instead
of the one doing the delivery?
Antony.
--
I conclude that there are two ways of constructing a software design: One way
is to make it so simple that there are _obviously_ no deficiencies, and the
other way is to make it so complicated that there are no _obvious_
deficiencies.
- C A R Hoare
Please reply to the list;
please *don't* CC me.
From mark at msapiro.net Fri Dec 8 17:45:38 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 8 Dec 2017 09:45:38 -0800
Subject: Postfix & vacation notice
In-Reply-To: <201712081003.34824.Antony.Stone@mailscanner.open.source.it>
References: <76983855-37bd-28ff-2b2f-f673a19294f2@glendown.de>
<201712081003.34824.Antony.Stone@mailscanner.open.source.it>
Message-ID: <097bc61b-a3e2-63e6-0ec9-973b8a55b132@msapiro.net>
On 12/08/2017 01:03 AM, Antony Stone wrote:
>
> Get the "other" instance of Postfix (ie: the one putting the mails into the
> queue directory for MailScanner to process) to generate the messages, instead
> of the one doing the delivery?
Unlike Sendmail, there's typically only one Postfix instance with
MailScanner. Incoming mail is placed in the hold queue and MailScanner
picks it up, processes it and requeues it in the incoming queue. See
.
You would need to get Postfix to put the vacation notice in the hold
queue instead of sending it. I don't offhand know how to do that if it
is even possible.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From Eoin.Kim at rcst.com.au Tue Dec 12 05:38:44 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Tue, 12 Dec 2017 05:38:44 +0000
Subject: [Question] missing components during the installation
Message-ID: <6d521b4037a64bdab96ffb7c78d0c6b7@rcst.com.au>
Hi all,
I am testing the MailScanner (v5.0.6-5) at the moment. The installation went well successfully although I could see few warning messages. I understand it is not really important but I would still like to ask. I am using Debian Jessie by the way.
1. So, I can see the following message from the installation log:
Package unrar is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'unrar' has no installation candidate
I believe adding non-free repository will fix this but are there any alternatives I can use?
1. During the Perl module installation, I could see the following messages:
optional module missing: Geo::IP
optional module missing: Net::Patricia
optional binary missing or nonfunctional: fetch
So, I think I can install first two missing modules (libgeo-ip-perl, libnet-patricia-perl). However, I cannot find a package that has fetch binary. Can someone please help me about this? Is this another Perl module?
Other than those, I think it's all good. Hopefully, this clarifies my situation. Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 - The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
From Eoin.Kim at rcst.com.au Tue Dec 12 22:01:01 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Tue, 12 Dec 2017 22:01:01 +0000
Subject: SpamAssassin installation failure
Message-ID: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 - The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
From iversons at rushville.k12.in.us Tue Dec 12 22:14:55 2017
From: iversons at rushville.k12.in.us (Shawn Iverson)
Date: Tue, 12 Dec 2017 17:14:55 -0500
Subject: SpamAssassin installation failure
In-Reply-To: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
Message-ID:
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim wrote:
> Hi all,
>
>
>
> I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it
> looks like installing SpamAssassin is failed. Below is the end of log
> message.
>
>
>
> Test Summary Report
>
> -------------------
>
> t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
>
> Failed tests: 1-2
>
> Non-zero exit status: 2
>
> Parse errors: Bad plan. You planned 5 tests but ran 2.
>
> Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79
> cusr 5.12 csys = 73.69 CPU)
>
> Result: FAIL
>
> Failed 1/168 test programs. 2/3014 subtests failed.
>
> Makefile:1582: recipe for target 'test_dynamic' failed
>
> make: *** [test_dynamic] Error 255
>
> -> FAIL Installing Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry with
> --force to force install it.
>
>
>
> I used this command - ./install.sh --MTA=postfix --installClamav=Y
> --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
>
>
>
> What is the possible cause of this error and how can I rectify this?
> Thanks a lot.
>
>
>
> *Eoin Kim*
>
> Systems Administrator
>
>
>
> *RCS Telecommunications *
>
> Level 1 ? The Annexe
>
> 133 Mary Street
>
> Brisbane, QLD, 4000
>
> Office: 07 3228 0843
>
> Mobile: 0419 726 231
>
>
>
> [image: RCST logo drop shadow]
>
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: not available
URL:
From Eoin.Kim at rcst.com.au Tue Dec 12 22:18:03 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Tue, 12 Dec 2017 22:18:03 +0000
Subject: SpamAssassin installation failure
In-Reply-To:
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
Message-ID:
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
From Eoin.Kim at rcst.com.au Tue Dec 12 22:22:54 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Tue, 12 Dec 2017 22:22:54 +0000
Subject: SpamAssassin installation failure
In-Reply-To:
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
Message-ID: <9a79299c4d844ca3afd0101607336e80@rcst.com.au>
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image002.jpg
URL:
From Eoin.Kim at rcst.com.au Tue Dec 12 23:09:11 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Tue, 12 Dec 2017 23:09:11 +0000
Subject: SpamAssassin installation failure
In-Reply-To: <9a79299c4d844ca3afd0101607336e80@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
Message-ID: <077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
Hi Shawn,
My apologies for messy emails but I?d like to make things clear. So, here?s what I did step by step:
1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo apt-get upgrade && sudo reboot).
2. Installed few packages: ca-certificates, libgeo-ip-perl, libnet-patricia-perl
3. Downloaded the MailScanner installer.
4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
During the procedure, I watched the log and this showed up.
--> Working on Digest::SHA1
Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
Configuring Digest-SHA1-2.13 ... OK
Building and testing Digest-SHA1-2.13 ... OK
Successfully installed Digest-SHA1-2.13
1 distribution installed
Mail::SpamAssassin is missing. Installing via CPAN ...
--> Working on Mail::SpamAssassin
Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz ... OK
Configuring Mail-SpamAssassin-3.004001 ... OK
Building and testing Mail-SpamAssassin-3.004001 ... ! Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
FAIL
It kept going and installation finished. And when I looked the /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:23 AM
To: MailScanner Discussion
Subject: RE: SpamAssassin installation failure
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image002.jpg
URL:
From Eoin.Kim at rcst.com.au Wed Dec 13 01:12:03 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Wed, 13 Dec 2017 01:12:03 +0000
Subject: SpamAssassin installation failure
In-Reply-To: <077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
Message-ID:
Hi Shawn,
I checked the install.sh script and it looks like --force options is missing.
#Install SpamaAssassin, use standard cpan in normail install, or App::cpanminus in unattended install
perldoc -l ${MODSA} >/dev/null 2>&1
if [ $? != 0 ]; then
clear
echo "${MODSA} is missing. Installing via CPAN ..."; echo;
timewait 1
if [ $AUTOCPAN -eq 0 ]; then
perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
else
cpanm --no-interactive ${MODSA}
fi
fi
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 9:09 AM
To: MailScanner Discussion
Subject: RE: SpamAssassin installation failure
Hi Shawn,
My apologies for messy emails but I?d like to make things clear. So, here?s what I did step by step:
1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo apt-get upgrade && sudo reboot).
2. Installed few packages: ca-certificates, libgeo-ip-perl, libnet-patricia-perl
3. Downloaded the MailScanner installer.
4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
During the procedure, I watched the log and this showed up.
--> Working on Digest::SHA1
Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
Configuring Digest-SHA1-2.13 ... OK
Building and testing Digest-SHA1-2.13 ... OK
Successfully installed Digest-SHA1-2.13
1 distribution installed
Mail::SpamAssassin is missing. Installing via CPAN ...
--> Working on Mail::SpamAssassin
Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz ... OK
Configuring Mail-SpamAssassin-3.004001 ... OK
Building and testing Mail-SpamAssassin-3.004001 ... ! Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
FAIL
It kept going and installation finished. And when I looked the /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:23 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image002.jpg
URL:
From iversons at rushville.k12.in.us Wed Dec 13 12:05:25 2017
From: iversons at rushville.k12.in.us (Shawn Iverson)
Date: Wed, 13 Dec 2017 07:05:25 -0500
Subject: SpamAssassin installation failure
In-Reply-To:
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
Message-ID:
Eoin,
If you install without using the flags for install.sh and answer the
prompts, does spamassassin install successfully?
On Tue, Dec 12, 2017 at 8:12 PM, Eoin Kim wrote:
> Hi Shawn,
>
>
>
> I checked the install.sh script and it looks like --force options is
> missing.
>
>
>
> #Install SpamaAssassin, use standard cpan in normail install, or
> App::cpanminus in unattended install
>
> perldoc -l ${MODSA} >/dev/null 2>&1
>
> if [ $? != 0 ]; then
>
> clear
>
> echo "${MODSA} is missing. Installing via CPAN ..."; echo;
>
> timewait 1
>
> if [ $AUTOCPAN -eq 0 ]; then
>
> perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
>
> else
>
> cpanm --no-interactive ${MODSA}
>
> fi
>
> fi
>
>
>
> Eoin
>
>
>
> *From:* MailScanner [mailto:mailscanner-bounces+eoin.kim=
> rcst.com.au at lists.mailscanner.info] *On Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 9:09 AM
> *To:* MailScanner Discussion
> *Subject:* RE: SpamAssassin installation failure
>
>
>
> Hi Shawn,
>
>
>
> My apologies for messy emails but I?d like to make things clear. So,
> here?s what I did step by step:
>
> 1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo
> apt-get upgrade && sudo reboot).
> 2. Installed few packages: ca-certificates, libgeo-ip-perl,
> libnet-patricia-perl
> 3. Downloaded the MailScanner installer.
> 4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y
> --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
>
>
>
> During the procedure, I watched the log and this showed up.
>
>
>
> --> Working on Digest::SHA1
>
> Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz
> ... OK
>
> Configuring Digest-SHA1-2.13 ... OK
>
> Building and testing Digest-SHA1-2.13 ... OK
>
> Successfully installed Digest-SHA1-2.13
>
> 1 distribution installed
>
> Mail::SpamAssassin is missing. Installing via CPAN ...
>
>
>
> --> Working on Mail::SpamAssassin
>
> Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/
> Mail-SpamAssassin-3.4.1.tar.gz ... OK
>
> Configuring Mail-SpamAssassin-3.004001 ... OK
>
> Building and testing Mail-SpamAssassin-3.004001 ... ! Installing
> Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log
> for details. Retry with --force to force install it.
>
> FAIL
>
>
>
> It kept going and installation finished. And when I looked the
> /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
>
>
>
> Test Summary Report
>
> -------------------
>
> t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
>
> Failed tests: 1-2
>
> Non-zero exit status: 2
>
> Parse errors: Bad plan. You planned 5 tests but ran 2.
>
> Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79
> cusr 5.12 csys = 73.69 CPU)
>
> Result: FAIL
>
> Failed 1/168 test programs. 2/3014 subtests failed.
>
> Makefile:1582: recipe for target 'test_dynamic' failed
>
> make: *** [test_dynamic] Error 255
>
> -> FAIL Installing Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry with
> --force to force install it.
>
>
>
> Eoin
>
>
>
> *From:* MailScanner [mailto:mailscanner-bounces+
> eoin.kim=rcst.com.au at lists.mailscanner.info
> ] *On
> Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 8:23 AM
> *To:* MailScanner Discussion
> *Subject:* RE: SpamAssassin installation failure
>
>
>
> Sorry for flying emails but I used this file -
> https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
>
>
>
> I didn?t clone Github. Thanks.
>
>
>
> Eoin
>
>
>
> *From:* MailScanner [mailto:mailscanner-bounces+
> eoin.kim=rcst.com.au at lists.mailscanner.info
> ] *On
> Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 8:18 AM
> *To:* MailScanner Discussion
> *Subject:* RE: SpamAssassin installation failure
>
>
>
> Thanks Shawn,
>
>
>
> I am using the latest kernel for your information (I did sudo apt-get
> update && sudo apt-get upgrade && sudo reboot).
>
>
>
> sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
>
> Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2
> (2017-12-03) x86_64 GNU/Linux
>
>
>
> Thanks again.
>
>
>
> Eoin
>
>
>
> *From:* MailScanner [mailto:mailscanner-bounces+
> eoin.kim=rcst.com.au at lists.mailscanner.info
> ] *On
> Behalf Of *Shawn Iverson
> *Sent:* Wednesday, 13 December 2017 8:15 AM
> *To:* MailScanner Discussion
> *Subject:* Re: SpamAssassin installation failure
>
>
>
> Eoin,
>
>
>
> I am spinning up a Jessie instance to see if i can reproduce the issue.
>
>
>
> On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim wrote:
>
> Hi all,
>
>
>
> I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it
> looks like installing SpamAssassin is failed. Below is the end of log
> message.
>
>
>
> Test Summary Report
>
> -------------------
>
> t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
>
> Failed tests: 1-2
>
> Non-zero exit status: 2
>
> Parse errors: Bad plan. You planned 5 tests but ran 2.
>
> Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79
> cusr 5.12 csys = 73.69 CPU)
>
> Result: FAIL
>
> Failed 1/168 test programs. 2/3014 subtests failed.
>
> Makefile:1582: recipe for target 'test_dynamic' failed
>
> make: *** [test_dynamic] Error 255
>
> -> FAIL Installing Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry with
> --force to force install it.
>
>
>
> I used this command - ./install.sh --MTA=postfix --installClamav=Y
> --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
>
>
>
> What is the possible cause of this error and how can I rectify this?
> Thanks a lot.
>
>
>
> *Eoin Kim*
>
> Systems Administrator
>
>
>
> *RCS Telecommunications *
>
> Level 1 ? The Annexe
>
> 133 Mary Street
>
> Brisbane, QLD, 4000
>
> Office: 07 3228 0843
>
> Mobile: 0419 726 231
>
>
>
> [image: RCST logo drop shadow]
>
>
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
>
>
> --
>
> Shawn Iverson, CETL
>
> Director of Technology
>
> Rush County Schools
>
> 765-932-3901 x1171 <(765)%20932-3901>
>
> iversons at rushville.k12.in.us
>
>
>
> [image: Image removed by sender.][image: Image removed by sender.]
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: not available
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: not available
URL:
From thom at vdb.nl Wed Dec 13 20:34:54 2017
From: thom at vdb.nl (Thom van der Boon)
Date: Wed, 13 Dec 2017 21:34:54 +0100 (CET)
Subject: Max Spam Check Size
Message-ID: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
Hi
I am currently experiencing quite some spam messages which are not caught by MailScanner (about one every 5 minutes) because of the "Max Spam Check Size" parameter in MailScanner.conf
# Spammers do not have the power to send out huge messages to everyone as
# it costs them too much (more smaller messages makes more profit than less
# very large messages). So if a message is bigger than a certain size, it
# is highly unlikely to be spam. Limiting this saves a lot of time checking
# huge messages.
# Disable this option by setting it to a huge value.
# This is measured in bytes.
# This can also be the filename of a ruleset.
Max Spam Check Size = 200k
After reviewing the log files, all messages which are uncaught have a size between 200k and 225k (most arround 215k) and look to be targeted to get past a MailScanner installation
I would suggest to set the new default value for this parameter from 200k to at least 300k in a future MailScanner version.
Met vriendelijke groet, Best regards,
Thom van der Boon
E-Mail: thom at vdb.nl
=====
Thom.H. van der Boon b.v.
Transito 4
6909 DA Babberich
Tel.: +31 (0)88 4272727
Fax: +31 (0)88 4272789
Home Page: http://www.vdb.nl/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From Antony.Stone at mailscanner.open.source.it Wed Dec 13 20:43:42 2017
From: Antony.Stone at mailscanner.open.source.it (Antony Stone)
Date: Wed, 13 Dec 2017 21:43:42 +0100
Subject: Max Spam Check Size
In-Reply-To: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
References: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
Message-ID: <201712132143.42214.Antony.Stone@mailscanner.open.source.it>
On Wednesday 13 December 2017 at 21:34:54, Thom van der Boon wrote:
> Hi
>
> I am currently experiencing quite some spam messages which are not caught
> by MailScanner (about one every 5 minutes) because of the "Max Spam Check
> Size" parameter in MailScanner.conf
> After reviewing the log files, all messages which are uncaught have a size
> between 200k and 225k (most arround 215k) and look to be targeted to get
> past a MailScanner installation
Would you care to pastebin a sample of such spam (I'm asuming they all
resemble one another, and aren't completely different messages which happen to
share a common size range) so the rest of us can see whether we're seeing
similar stuff?
Thanks,
Antony.
--
"If I've told you once, I've told you a million times - stop exaggerating!"
Please reply to the list;
please *don't* CC me.
From thom at vdb.nl Wed Dec 13 21:02:32 2017
From: thom at vdb.nl (Thom van der Boon)
Date: Wed, 13 Dec 2017 22:02:32 +0100 (CET)
Subject: Max Spam Check Size
In-Reply-To: <201712132143.42214.Antony.Stone@mailscanner.open.source.it>
References: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
<201712132143.42214.Antony.Stone@mailscanner.open.source.it>
Message-ID: <2129750295.648854.1513198952856.JavaMail.zimbra@vdb.nl>
Hi,
All spam is copier/Multifunctional or invoice related
Dec 13 16:56:47 mail MailScanner[3834]: Message CF27C20D53.A51AA from 82.192.71.78 (copier at domain.nl) to basecamp.nl is too big for spam checks (214959 > 200000 bytes)
Dec 13 16:58:09 mail MailScanner[2970]: Message ED3EB20D3F.A88E7 from 176.13.233.133 (copier at domain.eu) to domain.eu is too big for spam checks (214724 > 200000 bytes)
Dec 13 16:59:41 mail MailScanner[2970]: Message 4849720D3F.A8816 from 110.172.163.179 (copier at domain.nl) to domain.nl is too big for spam checks (214691 > 200000 bytes)
Dec 13 17:04:37 mail MailScanner[2970]: Message DEF3B20D3F.A5D67 from 82.192.71.78 (copier at domain.nl) to domain.nl is too big for spam checks (214888 > 200000 bytes)
Dec 13 17:15:01 mail MailScanner[4134]: Message A9C9A20D3F.A393A from 89.25.31.28 (copier at domain.nl) to domain.nl is too big for spam checks (214698 > 200000 bytes)
Dec 13 17:21:14 mail MailScanner[4005]: Message 540FE20D3F.AEE35 from 189.210.117.137 (copier at domain.nl) to domain.nl is too big for spam checks (214864 > 200000 bytes)
Dec 13 17:39:26 mail MailScanner[3127]: Message CB8F720D53.A312A from 82.192.71.78 (copier at domain.net) to domain.net is too big for spam checks (215035 > 200000 bytes)
Dec 13 17:54:40 mail MailScanner[4617]: Message 54DAB20D53.A8091 from 37.47.229.229 (copier at domain.nl) to domain.nl is too big for spam checks (214877 > 200000 bytes)
Dec 13 17:57:59 mail MailScanner[4738]: Message CE17220D53.AF738 from 202.84.45.219 (copier at domain.net) to domain.net is too big for spam checks (214786 > 200000 bytes)
Dec 13 17:59:21 mail MailScanner[4738]: Message 2264F20D53.A7D19 from 82.192.71.78 (copier at domain.eu) to domain.eu is too big for spam checks (214860 > 200000 bytes)
Dec 13 18:16:41 mail MailScanner[4134]: Message AAB0D21667.A71F6 from 171.233.171.251 (copier at domain.nl) to domain.nl is too big for spam checks (214711 > 200000 bytes)
Dec 13 18:17:11 mail MailScanner[4005]: Message 99A1821667.A92BF from 176.63.29.102 (copier at domain.nl) to domain.nl is too big for spam checks (214880 > 200000 bytes)
Dec 13 18:56:05 mail MailScanner[4617]: Message EC95C20D53.A8CAB from 82.192.71.78 (copier at domain.nl) to domain.nl is too big for spam checks (214864 > 200000 bytes)
Dec 13 19:14:48 mail MailScanner[5409]: Message 512F220D53.AF28C from 207.248.63.90 (copier at domain.nl) to domain.nl is too big for spam checks (214792 > 200000 bytes)
Dec 13 19:20:21 mail MailScanner[5409]: Message 6920C2046F.A09D9 from 117.2.35.204 (copier at domain.nl) to domain.nl is too big for spam checks (214682 > 200000 bytes)
Dec 13 19:24:25 mail MailScanner[4617]: Message D1700202B3.A7F9E from 82.192.71.78 (copier at domain.nl) to basecamp.nl is too big for spam checks (215028 > 200000 bytes)
Dec 13 19:35:51 mail MailScanner[4617]: Message 0CBF2202B3.A86F1 from 82.192.71.78 (copier at domain.nl) to domain.nl is too big for spam checks (214886 > 200000 bytes)
Dec 13 19:44:23 mail MailScanner[5409]: Message EE48C202B3.A7824 from 84.215.234.197 (copier at domain.nl) to domain.nl is too big for spam checks (214852 > 200000 bytes)
Dec 13 19:47:05 mail MailScanner[4617]: Message DAD11202B3.ABEF9 from 42.113.161.32 (copier at domain.nl) to domain.nl is too big for spam checks (214672 > 200000 bytes)
Dec 13 19:57:20 mail MailScanner[4738]: Message ACDE1202B3.ABFD0 from 171.61.234.53 (copier at domain.nl) to domain.nl is too big for spam checks (214877 > 200000 bytes)
Dec 13 19:59:48 mail MailScanner[5409]: Message 2CB60202B3.A18C4 from 147.236.232.253 (copier at domain.de) to domain-in.de is too big for spam checks (214775 > 200000 bytes)
Dec 13 20:04:56 mail MailScanner[5409]: Message 8D3BF2029A.ABC89 from 181.168.144.20 (copier at domain.net) to domain.net is too big for spam checks (214836 > 200000 bytes)
Dec 13 20:09:50 mail MailScanner[5873]: Message 76E5E2029A.AD1D5 from 1.52.38.2 (copier at domain.nl) to domain.nl is too big for spam checks (214642 > 200000 bytes)
Dec 13 20:43:18 mail MailScanner[5409]: Message E966420D3F.AA8FD from 171.234.152.170 (copier at domain.eu) to domain.eu is too big for spam checks (214684 > 200000 bytes)
Dec 13 20:46:01 mail MailScanner[5687]: Message 81FDE2028C.A7B2D from 82.192.71.78 (copier at domain.nl) to domain.nl is too big for spam checks (214907 > 200000 bytes)
Dec 13 20:50:32 mail MailScanner[7956]: Message 06BFA20277.A2CFB from 109.99.145.86 (copier at domain.nl) to domain.nl is too big for spam checks (214680 > 200000 bytes)
Met vriendelijke groet, Best regards,
Thom van der Boon
E-Mail: thom at vdb.nl
=====
Thom.H. van der Boon b.v.
Transito 4
6909 DA Babberich
Tel.: +31 (0)88 4272727
Fax: +31 (0)88 4272789
Home Page: http://www.vdb.nl/
Van: "Antony Stone"
Aan: "MailScanner Discussion"
Verzonden: Woensdag 13 december 2017 21:43:42
Onderwerp: Re: Max Spam Check Size
On Wednesday 13 December 2017 at 21:34:54, Thom van der Boon wrote:
> Hi
>
> I am currently experiencing quite some spam messages which are not caught
> by MailScanner (about one every 5 minutes) because of the "Max Spam Check
> Size" parameter in MailScanner.conf
> After reviewing the log files, all messages which are uncaught have a size
> between 200k and 225k (most arround 215k) and look to be targeted to get
> past a MailScanner installation
Would you care to pastebin a sample of such spam (I'm asuming they all
resemble one another, and aren't completely different messages which happen to
share a common size range) so the rest of us can see whether we're seeing
similar stuff?
Thanks,
Antony.
--
"If I've told you once, I've told you a million times - stop exaggerating!"
Please reply to the list;
please *don't* CC me.
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From Eoin.Kim at rcst.com.au Wed Dec 13 21:44:41 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Wed, 13 Dec 2017 21:44:41 +0000
Subject: SpamAssassin installation failure
In-Reply-To: <518380e5c1a241b68f13b69d2e530517@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
<518380e5c1a241b68f13b69d2e530517@rcst.com.au>
Message-ID:
Oh,
It looks like the message size was too big. I extracted the SpamAssassin installation part only. It seems successful for me. Also, I?d like to ask this question. During the MailScanner .deb package installation, I can see the following message:
ERROR: /var/log/clamav/freshclam.log is locked by another process
Is this a normal behaviour?
Eoin
From: Eoin Kim
Sent: Thursday, 14 December 2017 7:32 AM
To: MailScanner Discussion
Subject: RE: SpamAssassin installation failure
Hi Shawn,
The installation without flags looks different but I am not sure if this is successful or not. I?ll attach the installation log file. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 10:05 PM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
If you install without using the flags for install.sh and answer the prompts, does spamassassin install successfully?
On Tue, Dec 12, 2017 at 8:12 PM, Eoin Kim > wrote:
Hi Shawn,
I checked the install.sh script and it looks like --force options is missing.
#Install SpamaAssassin, use standard cpan in normail install, or App::cpanminus in unattended install
perldoc -l ${MODSA} >/dev/null 2>&1
if [ $? != 0 ]; then
clear
echo "${MODSA} is missing. Installing via CPAN ..."; echo;
timewait 1
if [ $AUTOCPAN -eq 0 ]; then
perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
else
cpanm --no-interactive ${MODSA}
fi
fi
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 9:09 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Hi Shawn,
My apologies for messy emails but I?d like to make things clear. So, here?s what I did step by step:
1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo apt-get upgrade && sudo reboot).
2. Installed few packages: ca-certificates, libgeo-ip-perl, libnet-patricia-perl
3. Downloaded the MailScanner installer.
4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
During the procedure, I watched the log and this showed up.
--> Working on Digest::SHA1
Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
Configuring Digest-SHA1-2.13 ... OK
Building and testing Digest-SHA1-2.13 ... OK
Successfully installed Digest-SHA1-2.13
1 distribution installed
Mail::SpamAssassin is missing. Installing via CPAN ...
--> Working on Mail::SpamAssassin
Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz ... OK
Configuring Mail-SpamAssassin-3.004001 ... OK
Building and testing Mail-SpamAssassin-3.004001 ... ! Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
FAIL
It kept going and installation finished. And when I looked the /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:23 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image002.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mailscanner-install.log
Type: application/octet-stream
Size: 74190 bytes
Desc: mailscanner-install.log
URL:
From mailinglists at feedmebits.nl Wed Dec 13 22:33:45 2017
From: mailinglists at feedmebits.nl (Maarten)
Date: Wed, 13 Dec 2017 23:33:45 +0100
Subject: postfix and mailscanner
Message-ID: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
Don't want to start a flame war here, but just a question, why does
postfix.org advise against using mailscanner? Saw the following on the
postfix website:
mailscanner: system, works with Postfix and other MTAs. WARNING: This
software uses unsupported methods to manipulate Postfix queue files
directly. This will result in corruption or loss of mail. The
mailscanner authors have sofar refused to discuss a proper access API or
protocol.
When reading through mailinglists it seems that some mails can get lost
as in how mailscanner handles mail from the postfix mailqueue, and that
it's safer to use one of the virus/spam/content filters that that uses
the SMTP proxy interface or the Milter Interface. I wouldn't know if
this is true or how to know if any mails every got lost(is there a way
to know of having lost mails), but have there ever been talks between
postfix devs and mailscanner devs about this?
From jerry.benton at mailborder.com Wed Dec 13 22:36:54 2017
From: jerry.benton at mailborder.com (Jerry Benton)
Date: Wed, 13 Dec 2017 17:36:54 -0500
Subject: postfix and mailscanner
In-Reply-To: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
Message-ID: <01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Because MailScanner does not use a proper milter for Postfix. Instead, it
gets the email from a hold directory and drops it back in the Postfix queue.
This is how it is supposed to work:
Postfix > milter > hold > scan > injection to Postfix > delivery
This is how it actually works:
Postfix > hold > scan > drop into Postfix
Technically, this is incorrect.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
-----Original Message-----
From: MailScanner
[mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.in
fo] On Behalf Of Maarten
Sent: Wednesday, December 13, 2017 17:34
To: MailScanner Discussion
Subject: postfix and mailscanner
Don't want to start a flame war here, but just a question, why does
postfix.org advise against using mailscanner? Saw the following on the
postfix website:
mailscanner: system, works with Postfix and other MTAs. WARNING: This
software uses unsupported methods to manipulate Postfix queue files
directly. This will result in corruption or loss of mail. The mailscanner
authors have sofar refused to discuss a proper access API or protocol.
When reading through mailinglists it seems that some mails can get lost as
in how mailscanner handles mail from the postfix mailqueue, and that it's
safer to use one of the virus/spam/content filters that that uses the SMTP
proxy interface or the Milter Interface. I wouldn't know if this is true or
how to know if any mails every got lost(is there a way to know of having
lost mails), but have there ever been talks between postfix devs and
mailscanner devs about this?
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
From mark at msapiro.net Wed Dec 13 22:45:12 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Dec 2017 14:45:12 -0800
Subject: Max Spam Check Size
In-Reply-To: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
References: <244758119.648666.1513197294202.JavaMail.zimbra@vdb.nl>
Message-ID: <400c068a-a110-54d3-0091-6996f5d773e2@msapiro.net>
On 12/13/2017 12:34 PM, Thom van der Boon wrote:
>
> After reviewing the log files, all messages which are uncaught have a
> size between 200k and 225k (most arround 215k) and look to be targeted
> to get past a MailScanner installation
>
> I would suggest to set the new default value for this parameter from
> 200k to at least 300k in a future MailScanner version.
I agree that there is now much spam that is larger than 200K bytes,
however if you are correct that it is targeted to be just over the
MailScanner default limit, raising the default limit will just provoke
the spammers to raise their message size and it would be better for
individual sites to raise the limit on their own.
On the other hand, I'm skeptical that this observation is more than a
coincidence, and I think a 500K default limit might make more sense.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From Eoin.Kim at rcst.com.au Wed Dec 13 21:32:00 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Wed, 13 Dec 2017 21:32:00 +0000
Subject: SpamAssassin installation failure
In-Reply-To:
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
Message-ID: <518380e5c1a241b68f13b69d2e530517@rcst.com.au>
Hi Shawn,
The installation without flags looks different but I am not sure if this is successful or not. I?ll attach the installation log file. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 10:05 PM
To: MailScanner Discussion
Subject: Re: SpamAssassin installation failure
Eoin,
If you install without using the flags for install.sh and answer the prompts, does spamassassin install successfully?
On Tue, Dec 12, 2017 at 8:12 PM, Eoin Kim > wrote:
Hi Shawn,
I checked the install.sh script and it looks like --force options is missing.
#Install SpamaAssassin, use standard cpan in normail install, or App::cpanminus in unattended install
perldoc -l ${MODSA} >/dev/null 2>&1
if [ $? != 0 ]; then
clear
echo "${MODSA} is missing. Installing via CPAN ..."; echo;
timewait 1
if [ $AUTOCPAN -eq 0 ]; then
perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
else
cpanm --no-interactive ${MODSA}
fi
fi
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 9:09 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Hi Shawn,
My apologies for messy emails but I?d like to make things clear. So, here?s what I did step by step:
1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo apt-get upgrade && sudo reboot).
2. Installed few packages: ca-certificates, libgeo-ip-perl, libnet-patricia-perl
3. Downloaded the MailScanner installer.
4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
During the procedure, I watched the log and this showed up.
--> Working on Digest::SHA1
Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
Configuring Digest-SHA1-2.13 ... OK
Building and testing Digest-SHA1-2.13 ... OK
Successfully installed Digest-SHA1-2.13
1 distribution installed
Mail::SpamAssassin is missing. Installing via CPAN ...
--> Working on Mail::SpamAssassin
Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz ... OK
Configuring Mail-SpamAssassin-3.004001 ... OK
Building and testing Mail-SpamAssassin-3.004001 ... ! Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
FAIL
It kept going and installation finished. And when I looked the /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:23 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mailscanner-install.log
Type: application/octet-stream
Size: 440943 bytes
Desc: mailscanner-install.log
URL:
From mark at msapiro.net Wed Dec 13 22:50:58 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Dec 2017 14:50:58 -0800
Subject: SpamAssassin installation failure
In-Reply-To: <518380e5c1a241b68f13b69d2e530517@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
<518380e5c1a241b68f13b69d2e530517@rcst.com.au>
Message-ID: <050ca77c-b891-71ca-f692-692d54ed1f95@msapiro.net>
On 12/13/2017 01:32 PM, Eoin Kim wrote:
> Hi Shawn,
>
> ?
>
> The installation without flags looks different but I am not sure if this
> is successful or not. I?ll attach the installation log file. Thanks.
>
> ?
>
> Eoin
>
> ?
>
> *From:*MailScanner
> [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info]
> *On Behalf Of *Shawn Iverson
> *Sent:* Wednesday, 13 December 2017 10:05 PM
> *To:* MailScanner Discussion
> *Subject:* Re: SpamAssassin installation failure
>
> ?
>
> Eoin,
>
> ?
>
> If you install without using the flags for install.sh and answer the
> prompts, does spamassassin install successfully?
>
> ?
>
> On Tue, Dec 12, 2017 at 8:12 PM, Eoin Kim > wrote:
>
> Hi Shawn,
>
> ?
>
> I checked the install.sh script and it looks like --force options is
> missing.
>
> ?
>
> #Install SpamaAssassin, use standard cpan in normail install, or
> App::cpanminus in unattended install
>
> ??? perldoc -l ${MODSA} >/dev/null 2>&1
>
> ??? if [ $? != 0 ]; then
>
> ??????? clear
>
> ??????? echo "${MODSA} is missing. Installing via CPAN ..."; echo;
>
> ??????? timewait 1
>
> ??????? if [ $AUTOCPAN -eq 0 ]; then
>
> ??????????? perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
>
> ??????? else
>
> ??????????? cpanm --no-interactive ${MODSA}
>
> ??????? fi
>
> ??? fi
>
> ?
>
> Eoin
>
> ?
>
> *From:*MailScanner [mailto:mailscanner-bounces+eoin.kim
> =rcst.com.au at lists.mailscanner.info
> ] *On Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 9:09 AM
> *To:* MailScanner Discussion >
> *Subject:* RE: SpamAssassin installation failure
>
> ?
>
> Hi Shawn,
>
> ?
>
> My apologies for messy emails but I?d like to make things clear. So,
> here?s what I did step by step:
>
> 1. Installed Debian Jessie and upgraded (sudo apt-get update &&
> sudo apt-get upgrade && sudo reboot).
> 2. Installed few packages: ca-certificates, libgeo-ip-perl,
> libnet-patricia-perl
> 3. Downloaded the MailScanner installer.
> 4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y
> --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
>
> ?
>
> During the procedure, I watched the log and this showed up.
>
> ?
>
> --> Working on Digest::SHA1
>
> Fetching
> http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
>
> Configuring Digest-SHA1-2.13 ... OK
>
> Building and testing Digest-SHA1-2.13 ... OK
>
> Successfully installed Digest-SHA1-2.13
>
> 1 distribution installed
>
> Mail::SpamAssassin is missing. Installing via CPAN ...
>
> ?
>
> --> Working on Mail::SpamAssassin
>
> Fetching
> http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz
> ... OK
>
> Configuring Mail-SpamAssassin-3.004001 ... OK
>
> Building and testing Mail-SpamAssassin-3.004001 ... ! Installing
> Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry with
> --force to force install it.
>
> FAIL
>
> ?
>
> It kept going and installation finished. And when I looked the
> /root/.cpanm/work/1513044980.46831/build.log file, at the end this
> shows.
>
> ?
>
> Test Summary Report
>
> -------------------
>
> t/sa_compile.t????????????????? (Wstat: 512 Tests: 2 Failed: 2)
>
> ? Failed tests:? 1-2
>
> ? Non-zero exit status: 2
>
> ? Parse errors: Bad plan.? You planned 5 tests but ran 2.
>
> Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr? 0.09 sys +
> 67.79 cusr? 5.12 csys = 73.69 CPU)
>
> Result: FAIL
>
> Failed 1/168 test programs. 2/3014 subtests failed.
>
> Makefile:1582: recipe for target 'test_dynamic' failed
>
> make: *** [test_dynamic] Error 255
>
> -> FAIL Installing Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry with
> --force to force install it.
>
> ?
>
> Eoin
>
> ?
>
> *From:*MailScanner
> [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info]
> *On Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 8:23 AM
> *To:* MailScanner Discussion >
> *Subject:* RE: SpamAssassin installation failure
>
> ?
>
> Sorry for flying emails but I used this file -
> https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
>
> ?
>
> I didn?t clone Github. Thanks.
>
> ?
>
> Eoin
>
> ?
>
> *From:*MailScanner
> [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info]
> *On Behalf Of *Eoin Kim
> *Sent:* Wednesday, 13 December 2017 8:18 AM
> *To:* MailScanner Discussion >
> *Subject:* RE: SpamAssassin installation failure
>
> ?
>
> Thanks Shawn,
>
> ?
>
> I am using the latest kernel for your information (I did sudo
> apt-get update && sudo apt-get upgrade && sudo reboot).
>
> ?
>
> sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$
>
> uname -a
>
> Linux mx1.bne.lab.boof.com
> 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
>
> ?
>
> Thanks again.
>
> ?
>
> Eoin
>
> ?
>
> *From:*MailScanner
> [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info]
> *On Behalf Of *Shawn Iverson
> *Sent:* Wednesday, 13 December 2017 8:15 AM
> *To:* MailScanner Discussion >
> *Subject:* Re: SpamAssassin installation failure
>
> ?
>
> Eoin,
>
> ?
>
> I am spinning up a Jessie instance to see if i can reproduce the issue.
>
> ?
>
> On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
>
> Hi all,
>
> ?
>
> I am trying to install MailScanner (v.5.0.6-5) on my Debian
> Jessie and it looks like installing SpamAssassin is failed.
> Below is the end of log message.
>
> ?
>
> Test Summary Report
>
> -------------------
>
> t/sa_compile.t????????????????? (Wstat: 512 Tests: 2 Failed: 2)
>
> ? Failed tests:? 1-2
>
> ? Non-zero exit status: 2
>
> ? Parse errors: Bad plan.? You planned 5 tests but ran 2.
>
> Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr? 0.09 sys +
> 67.79 cusr? 5.12 csys = 73.69 CPU)
>
> Result: FAIL
>
> Failed 1/168 test programs. 2/3014 subtests failed.
>
> Makefile:1582: recipe for target 'test_dynamic' failed
>
> make: *** [test_dynamic] Error 255
>
> -> FAIL Installing Mail::SpamAssassin failed. See
> /root/.cpanm/work/1513044980.46831/build.log for details. Retry
> with --force to force install it.
>
> ?
>
> I used this command - ./install.sh --MTA=postfix
> --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
>
> ?
>
> What is the possible cause of this error and how can I rectify
> this? Thanks a lot.
>
> ?
>
> *Eoin Kim*
>
> Systems Administrator
>
> ?
>
> *RCS Telecommunications *
>
> Level 1 ? The Annexe
>
> 133 Mary Street
>
> Brisbane, QLD, 4000
>
> Office:?? 07 3228 0843
>
> Mobile:?0419 726 231
>
> ?
>
> RCST logo drop shadow
>
> ?
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
>
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
> ?
>
> --
>
> Shawn Iverson, CETL
>
> Director of Technology
>
> Rush County Schools
>
> 765-932-3901 x1171
>
> iversons at rushville.k12.in.us
>
> ?
>
> Image removed by sender.Image removed by sender.
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
>
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
> ?
>
> --
>
> Shawn Iverson, CETL
>
> Director of Technology
>
> Rush County Schools
>
> 765-932-3901 x1171
>
> iversons at rushville.k12.in.us
>
> ?
>
> Image removed by sender.Image removed by sender.
>
>
>
>
>
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From mark at msapiro.net Wed Dec 13 22:57:25 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Dec 2017 14:57:25 -0800
Subject: SpamAssassin installation failure
In-Reply-To: <050ca77c-b891-71ca-f692-692d54ed1f95@msapiro.net>
References: <050ca77c-b891-71ca-f692-692d54ed1f95@msapiro.net>
Message-ID: <40af3e81-4c69-b3a4-2563-aa8bec5f7330@msapiro.net>
Mark Sapiro wrote:
> On 12/13/2017 01:32 PM, Eoin Kim wrote:
>> Hi Shawn,
>>
...
Sorry for the noise. My fumble fingers apologize for the repost.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From Antony.Stone at mailscanner.open.source.it Wed Dec 13 22:58:49 2017
From: Antony.Stone at mailscanner.open.source.it (Antony Stone)
Date: Wed, 13 Dec 2017 23:58:49 +0100
Subject: postfix and mailscanner
In-Reply-To: <01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Message-ID: <201712132358.50149.Antony.Stone@mailscanner.open.source.it>
On Wednesday 13 December 2017 at 23:36:54, Jerry Benton wrote:
> Because MailScanner does not use a proper milter for Postfix. Instead, it
> gets the email from a hold directory and drops it back in the Postfix
> queue.
>
>
> This is how it is supposed to work:
>
> Postfix > milter > hold > scan > injection to Postfix > delivery
>
>
> This is how it actually works:
>
> Postfix > hold > scan > drop into Postfix
>
>
> Technically, this is incorrect.
That's how it works with sendmail and Exim, too, so why do the postfix people
say that this "will result in corruption or loss of mail"?
Has this been verified?
Antony.
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.i
> n fo] On Behalf Of Maarten
> Sent: Wednesday, December 13, 2017 17:34
> To: MailScanner Discussion
> Subject: postfix and mailscanner
>
> Don't want to start a flame war here, but just a question, why does
> postfix.org advise against using mailscanner? Saw the following on the
> postfix website:
>
> mailscanner: system, works with Postfix and other MTAs. WARNING: This
> software uses unsupported methods to manipulate Postfix queue files
> directly. This will result in corruption or loss of mail. The mailscanner
> authors have sofar refused to discuss a proper access API or protocol.
>
> When reading through mailinglists it seems that some mails can get lost as
> in how mailscanner handles mail from the postfix mailqueue, and that it's
> safer to use one of the virus/spam/content filters that that uses the SMTP
> proxy interface or the Milter Interface. I wouldn't know if this is true or
> how to know if any mails every got lost(is there a way to know of having
> lost mails), but have there ever been talks between postfix devs and
> mailscanner devs about this?
--
The first fifty percent of an engineering project takes ninety percent of the
time, and the remaining fifty percent takes another ninety percent of the time.
Please reply to the list;
please *don't* CC me.
From Eoin.Kim at rcst.com.au Wed Dec 13 23:00:05 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Wed, 13 Dec 2017 23:00:05 +0000
Subject: SpamAssassin installation failure
In-Reply-To: <40af3e81-4c69-b3a4-2563-aa8bec5f7330@msapiro.net>
References: <050ca77c-b891-71ca-f692-692d54ed1f95@msapiro.net>
<40af3e81-4c69-b3a4-2563-aa8bec5f7330@msapiro.net>
Message-ID: <71c528d048bf4c638fe1865e12a7e524@rcst.com.au>
G'day Mark,
My bad, will cancel from next time. I tried to cancel via the link but it looks like already done by someone. Cheers.
Eoin
-----Original Message-----
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Mark Sapiro
Sent: Thursday, 14 December 2017 8:57 AM
To: mailscanner at lists.mailscanner.info
Subject: Re: SpamAssassin installation failure
Mark Sapiro wrote:
> On 12/13/2017 01:32 PM, Eoin Kim wrote:
>> Hi Shawn,
>>
...
Sorry for the noise. My fumble fingers apologize for the repost.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
From jerry.benton at mailborder.com Wed Dec 13 23:01:25 2017
From: jerry.benton at mailborder.com (Jerry Benton)
Date: Wed, 13 Dec 2017 18:01:25 -0500
Subject: postfix and mailscanner
In-Reply-To: <201712132358.50149.Antony.Stone@mailscanner.open.source.it>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
<201712132358.50149.Antony.Stone@mailscanner.open.source.it>
Message-ID: <01fa01d37466$4d47e580$e7d7b080$@mailborder.com>
Technically, it could because when putting back into the Postfix system you
are dropping it into a directory and not feeding it back in through and
outgoing milter. I have never seen it happen, but it is technically
possible.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
-----Original Message-----
From: MailScanner
[mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.in
fo] On Behalf Of Antony Stone
Sent: Wednesday, December 13, 2017 17:59
To: MailScanner Discussion
Subject: Re: postfix and mailscanner
On Wednesday 13 December 2017 at 23:36:54, Jerry Benton wrote:
> Because MailScanner does not use a proper milter for Postfix. Instead,
> it gets the email from a hold directory and drops it back in the
> Postfix queue.
>
>
> This is how it is supposed to work:
>
> Postfix > milter > hold > scan > injection to Postfix > delivery
>
>
> This is how it actually works:
>
> Postfix > hold > scan > drop into Postfix
>
>
> Technically, this is incorrect.
That's how it works with sendmail and Exim, too, so why do the postfix
people say that this "will result in corruption or loss of mail"?
Has this been verified?
Antony.
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscan
> ner.i
> n fo] On Behalf Of Maarten
> Sent: Wednesday, December 13, 2017 17:34
> To: MailScanner Discussion
> Subject: postfix and mailscanner
>
> Don't want to start a flame war here, but just a question, why does
> postfix.org advise against using mailscanner? Saw the following on the
> postfix website:
>
> mailscanner: system, works with Postfix and other MTAs. WARNING: This
> software uses unsupported methods to manipulate Postfix queue files
> directly. This will result in corruption or loss of mail. The
> mailscanner authors have sofar refused to discuss a proper access API or
protocol.
>
> When reading through mailinglists it seems that some mails can get
> lost as in how mailscanner handles mail from the postfix mailqueue,
> and that it's safer to use one of the virus/spam/content filters that
> that uses the SMTP proxy interface or the Milter Interface. I wouldn't
> know if this is true or how to know if any mails every got lost(is
> there a way to know of having lost mails), but have there ever been
> talks between postfix devs and mailscanner devs about this?
--
The first fifty percent of an engineering project takes ninety percent of
the time, and the remaining fifty percent takes another ninety percent of
the time.
Please reply to the list;
please *don't* CC
me.
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
From mailinglists at feedmebits.nl Wed Dec 13 23:12:03 2017
From: mailinglists at feedmebits.nl (Maarten)
Date: Thu, 14 Dec 2017 00:12:03 +0100
Subject: postfix and mailscanner
In-Reply-To: <01fa01d37466$4d47e580$e7d7b080$@mailborder.com>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
<201712132358.50149.Antony.Stone@mailscanner.open.source.it>
<01fa01d37466$4d47e580$e7d7b080$@mailborder.com>
Message-ID:
How would you be able to tell if this every happened?
On 12/14/2017 12:01 AM, Jerry Benton wrote:
> Technically, it could because when putting back into the Postfix system you
> are dropping it into a directory and not feeding it back in through and
> outgoing milter. I have never seen it happen, but it is technically
> possible.
>
>
> --
> Jerry Benton
> www.mailborder.com
> +1 (843) 800-8605
> +44 (020) 3883-8605
>
>
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.in
> fo] On Behalf Of Antony Stone
> Sent: Wednesday, December 13, 2017 17:59
> To: MailScanner Discussion
> Subject: Re: postfix and mailscanner
>
> On Wednesday 13 December 2017 at 23:36:54, Jerry Benton wrote:
>
>> Because MailScanner does not use a proper milter for Postfix. Instead,
>> it gets the email from a hold directory and drops it back in the
>> Postfix queue.
>>
>>
>> This is how it is supposed to work:
>>
>> Postfix > milter > hold > scan > injection to Postfix > delivery
>>
>>
>> This is how it actually works:
>>
>> Postfix > hold > scan > drop into Postfix
>>
>>
>> Technically, this is incorrect.
> That's how it works with sendmail and Exim, too, so why do the postfix
> people say that this "will result in corruption or loss of mail"?
>
> Has this been verified?
>
>
> Antony.
>
>> -----Original Message-----
>> From: MailScanner
>> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscan
>> ner.i
>> n fo] On Behalf Of Maarten
>> Sent: Wednesday, December 13, 2017 17:34
>> To: MailScanner Discussion
>> Subject: postfix and mailscanner
>>
>> Don't want to start a flame war here, but just a question, why does
>> postfix.org advise against using mailscanner? Saw the following on the
>> postfix website:
>>
>> mailscanner: system, works with Postfix and other MTAs. WARNING: This
>> software uses unsupported methods to manipulate Postfix queue files
>> directly. This will result in corruption or loss of mail. The
>> mailscanner authors have sofar refused to discuss a proper access API or
> protocol.
>> When reading through mailinglists it seems that some mails can get
>> lost as in how mailscanner handles mail from the postfix mailqueue,
>> and that it's safer to use one of the virus/spam/content filters that
>> that uses the SMTP proxy interface or the Milter Interface. I wouldn't
>> know if this is true or how to know if any mails every got lost(is
>> there a way to know of having lost mails), but have there ever been
>> talks between postfix devs and mailscanner devs about this?
> --
> The first fifty percent of an engineering project takes ninety percent of
> the time, and the remaining fifty percent takes another ninety percent of
> the time.
>
> Please reply to the list;
> please *don't* CC
> me.
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
>
From jerry.benton at mailborder.com Wed Dec 13 23:14:17 2017
From: jerry.benton at mailborder.com (Jerry Benton)
Date: Wed, 13 Dec 2017 18:14:17 -0500
Subject: postfix and mailscanner
In-Reply-To:
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
<201712132358.50149.Antony.Stone@mailscanner.open.source.it>
<01fa01d37466$4d47e580$e7d7b080$@mailborder.com>
Message-ID: <01fb01d37468$19773560$4c65a020$@mailborder.com>
You would see corrupted email in Postfix's /var/spool/postfix/corrupt/
directory. Now that I think about it, I have seen corrupted emails before,
but I don't know if that was due to MailScanner or not.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
-----Original Message-----
From: MailScanner
[mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.in
fo] On Behalf Of Maarten
Sent: Wednesday, December 13, 2017 18:12
To: MailScanner Discussion
Subject: Re: postfix and mailscanner
How would you be able to tell if this every happened?
On 12/14/2017 12:01 AM, Jerry Benton wrote:
> Technically, it could because when putting back into the Postfix
> system you are dropping it into a directory and not feeding it back in
> through and outgoing milter. I have never seen it happen, but it is
> technically possible.
>
>
> --
> Jerry Benton
> www.mailborder.com
> +1 (843) 800-8605
> +44 (020) 3883-8605
>
>
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscan
> ner.in
> fo] On Behalf Of Antony Stone
> Sent: Wednesday, December 13, 2017 17:59
> To: MailScanner Discussion
> Subject: Re: postfix and mailscanner
>
> On Wednesday 13 December 2017 at 23:36:54, Jerry Benton wrote:
>
>> Because MailScanner does not use a proper milter for Postfix.
>> Instead, it gets the email from a hold directory and drops it back in
>> the Postfix queue.
>>
>>
>> This is how it is supposed to work:
>>
>> Postfix > milter > hold > scan > injection to Postfix > delivery
>>
>>
>> This is how it actually works:
>>
>> Postfix > hold > scan > drop into Postfix
>>
>>
>> Technically, this is incorrect.
> That's how it works with sendmail and Exim, too, so why do the postfix
> people say that this "will result in corruption or loss of mail"?
>
> Has this been verified?
>
>
> Antony.
>
>> -----Original Message-----
>> From: MailScanner
>> [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailsca
>> n
>> ner.i
>> n fo] On Behalf Of Maarten
>> Sent: Wednesday, December 13, 2017 17:34
>> To: MailScanner Discussion
>> Subject: postfix and mailscanner
>>
>> Don't want to start a flame war here, but just a question, why does
>> postfix.org advise against using mailscanner? Saw the following on
>> the postfix website:
>>
>> mailscanner: system, works with Postfix and other MTAs. WARNING: This
>> software uses unsupported methods to manipulate Postfix queue files
>> directly. This will result in corruption or loss of mail. The
>> mailscanner authors have sofar refused to discuss a proper access API
>> or
> protocol.
>> When reading through mailinglists it seems that some mails can get
>> lost as in how mailscanner handles mail from the postfix mailqueue,
>> and that it's safer to use one of the virus/spam/content filters that
>> that uses the SMTP proxy interface or the Milter Interface. I
>> wouldn't know if this is true or how to know if any mails every got
>> lost(is there a way to know of having lost mails), but have there
>> ever been talks between postfix devs and mailscanner devs about this?
> --
> The first fifty percent of an engineering project takes ninety percent
> of the time, and the remaining fifty percent takes another ninety
> percent of the time.
>
> Please reply to the
list;
> please
> *don't* CC me.
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
>
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
From mark at msapiro.net Wed Dec 13 23:36:38 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Dec 2017 15:36:38 -0800
Subject: postfix and mailscanner
In-Reply-To: <201712132358.50149.Antony.Stone@mailscanner.open.source.it>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
<201712132358.50149.Antony.Stone@mailscanner.open.source.it>
Message-ID: <7655fadb-871e-d780-7f9a-01d54da674b3@msapiro.net>
On 12/13/2017 02:58 PM, Antony Stone wrote:
>
> That's how it works with sendmail and Exim, too, so why do the postfix people
> say that this "will result in corruption or loss of mail"?
>
> Has this been verified?
I have never seen lost mail. If you look at mail logs you will see that
mail arrives and Postfix puts it in 'hold'. Then MailScanner picks it up
and processes it and may decide to do things other than send it, but if
MailScanner wants to send it , it logs a 'requeue' to 'incoming' and
then Postfix picks it up and sends it.
This is a typical sequence where MailScanner doesn't forward the message
(maybe just quarantines it) Some domains elided to get past outgoing
MailScanner.
> Dec 10 06:51:23 sbh16 postfix/cleanup[1564]: AB06E11E00AA: hold: header Received: from xxx (unknown [195.110.8.16])??by sbh16.songbird.com (Postfix) with ESMTP id AB06E11E00AA??for ; Sun, 10 Dec 2017 06:51:23 -0800 (PST) from unknown[195.110.8.16]; from=<24627-23098-114862-4267-gpc+2Dtalk+2Dbounces=grizz.org at xxx> to= proto=ESMTP helo=
> Dec 10 06:51:23 sbh16 postfix/cleanup[1564]: AB06E11E00AA: message-id=
> Dec 10 06:51:24 sbh16 postfix/smtpd[1560]: disconnect from unknown[195.110.8.16] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
> Dec 10 06:51:24 sbh16 MailScanner[32550]: New Batch: Scanning 1 messages, 9709 bytes
> Dec 10 06:51:24 sbh16 MailScanner[32550]: Virus and Content Scanning: Starting
> Dec 10 06:51:24 sbh16 MailScanner[32550]: Expired 3 records from the SpamAssassin cache
> Dec 10 06:51:25 sbh16 MailScanner[32550]: Spam Checks: Found 1 spam messages
> Dec 10 06:51:25 sbh16 MailScanner[32550]: Deleted 1 messages from processing-database
and here's a sequence where MailScanner has disarmed a web bug but
delivered the message.
> Dec 10 07:23:11 sbh16 postfix/cleanup[2738]: 25E7011E00AA: hold: header Received: from mail68.sea31.mcsv.net (mail68.sea31.mcsv.net [148.105.11.68])??by sbh16.songbird.com (Postfix) with ESMTP id 25E7011E00AA??for ; Sun, 10 Dec 2017 07:23:11 -0800 (PST) from mail68.sea31.mcsv.net[148.105.11.68]; from= to= proto=ESMTP helo=
> Dec 10 07:23:11 sbh16 postfix/cleanup[2738]: 25E7011E00AA: message-id=
> Dec 10 07:23:11 sbh16 opendkim[1920]: 25E7011E00AA: signature=r+iJbEQD domain=mail68.sea31.mcsv.net selector=k1 result="no signature error"
> Dec 10 07:23:11 sbh16 opendkim[1920]: 25E7011E00AA: DKIM verification successful
> Dec 10 07:23:11 sbh16 opendkim[1920]: 25E7011E00AA: s=k1 d=mail68.sea31.mcsv.net SSL
> Dec 10 07:23:11 sbh16 postfix/smtpd[2735]: disconnect from mail68.sea31.mcsv.net[148.105.11.68] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
> Dec 10 07:23:16 sbh16 MailScanner[2322]: New Batch: Scanning 1 messages, 113205 bytes
> Dec 10 07:23:16 sbh16 MailScanner[2322]: Virus and Content Scanning: Starting
> Dec 10 07:23:18 sbh16 MailScanner[2322]: Content Checks: Detected and have disarmed web bug tags in HTML message in 25E7011E00AA.AE29E from bounce-mc.us3_26220743.447333-mark=msapiro.net at mail68.sea31.mcsv.net
> Dec 10 07:23:18 sbh16 MailScanner[2322]: Requeue: 25E7011E00AA.AE29E to EFAF711E0114
> Dec 10 07:23:18 sbh16 MailScanner[2322]: Uninfected: Delivered 1 messages
> Dec 10 07:23:18 sbh16 postfix/qmgr[2800]: EFAF711E0114: from=, size=112060, nrcpt=1 (queue active)
> Dec 10 07:23:18 sbh16 MailScanner[2322]: Deleted 1 messages from processing-database
> Dec 10 07:23:18 sbh16 postfix/local[2750]: EFAF711E0114: to=, orig_to=, relay=local, delay=7.8, delays=7.8/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
> Dec 10 07:23:18 sbh16 postfix/qmgr[2800]: EFAF711E0114: removed
I suppose one could write some kind of script to ignore 'normal
sequences like
> Dec 10 07:23:11 sbh16 postfix/cleanup[2738]: 25E7011E00AA: hold: header Received: ...
> Dec 10 07:23:18 sbh16 MailScanner[2322]: Requeue: 25E7011E00AA.AE29E to EFAF711E0114
> Dec 10 07:23:18 sbh16 postfix/qmgr[2800]: EFAF711E0114: from=...
or
> Dec 10 06:51:23 sbh16 postfix/cleanup[1564]: AB06E11E00AA: hold: header Received: ...
followed by messages like
> Dec 10 06:51:25 sbh16 MailScanner[32550]: Spam Checks: Found 1 spam messages
or things like 'Virus Scanning: Found 1 viruses' and/or 'Saved entire
message to'
and see if there are any others.
Years ago, when I first started using MailScanner, I saw rare
occurrences of duplicate messages and I reduced the number of
MailScanner children from five to one, and haven't seen any problems
since. To the best of my knowledge, I've never seen MailScanner lose a
message.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From iversons at rushville.k12.in.us Wed Dec 13 23:49:57 2017
From: iversons at rushville.k12.in.us (Shawn Iverson)
Date: Wed, 13 Dec 2017 18:49:57 -0500
Subject: postfix and mailscanner
In-Reply-To: <01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Message-ID:
For anyone curious, I am researching creating a mailscanner milter for
postfix. I have gotten as far to conclude it is possible and that it might
bring additional functionality when using postfix and mailscanner
together. For example, it would be possible to reject a message for
various reasons and still have detailed reports on the messages. It would
also be possible to have more granular whitelisting capabilities (virus
scan only, spam scan only, no scan, etc.). It is a ways off, but I've been
looking at milter code on various things for a while.
On Wed, Dec 13, 2017 at 5:36 PM, Jerry Benton
wrote:
> Because MailScanner does not use a proper milter for Postfix. Instead, it
> gets the email from a hold directory and drops it back in the Postfix
> queue.
>
>
> This is how it is supposed to work:
>
> Postfix > milter > hold > scan > injection to Postfix > delivery
>
>
> This is how it actually works:
>
> Postfix > hold > scan > drop into Postfix
>
>
> Technically, this is incorrect.
>
>
> --
> Jerry Benton
> www.mailborder.com
> +1 (843) 800-8605
> +44 (020) 3883-8605
>
>
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+jerry.benton=mailborder.com@
> lists.mailscanner.in
> fo] On Behalf Of Maarten
> Sent: Wednesday, December 13, 2017 17:34
> To: MailScanner Discussion
> Subject: postfix and mailscanner
>
> Don't want to start a flame war here, but just a question, why does
> postfix.org advise against using mailscanner? Saw the following on the
> postfix website:
>
> mailscanner: system, works with Postfix and other MTAs. WARNING: This
> software uses unsupported methods to manipulate Postfix queue files
> directly. This will result in corruption or loss of mail. The mailscanner
> authors have sofar refused to discuss a proper access API or protocol.
>
> When reading through mailinglists it seems that some mails can get lost as
> in how mailscanner handles mail from the postfix mailqueue, and that it's
> safer to use one of the virus/spam/content filters that that uses the SMTP
> proxy interface or the Milter Interface. I wouldn't know if this is true or
> how to know if any mails every got lost(is there a way to know of having
> lost mails), but have there ever been talks between postfix devs and
> mailscanner devs about this?
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jerry.benton at mailborder.com Thu Dec 14 00:05:19 2017
From: jerry.benton at mailborder.com (Jerry Benton)
Date: Wed, 13 Dec 2017 19:05:19 -0500
Subject: postfix and mailscanner
In-Reply-To:
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Message-ID: <023601d3746f$3afe42d0$b0fac870$@mailborder.com>
It is possible. I have written one for Mailborder v5 in PHP. I have gone so far as to write an entire new scanning engine in C and PHP as well for Mailborder v5. The milter won?t work with MailScanner because it is designed to work with the upcoming Mailborder scan engine, but I can share some information to help build a MailScanner milter.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
From: MailScanner [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, December 13, 2017 18:50
To: MailScanner Discussion
Subject: Re: postfix and mailscanner
For anyone curious, I am researching creating a mailscanner milter for postfix. I have gotten as far to conclude it is possible and that it might bring additional functionality when using postfix and mailscanner together. For example, it would be possible to reject a message for various reasons and still have detailed reports on the messages. It would also be possible to have more granular whitelisting capabilities (virus scan only, spam scan only, no scan, etc.). It is a ways off, but I've been looking at milter code on various things for a while.
On Wed, Dec 13, 2017 at 5:36 PM, Jerry Benton > wrote:
Because MailScanner does not use a proper milter for Postfix. Instead, it
gets the email from a hold directory and drops it back in the Postfix queue.
This is how it is supposed to work:
Postfix > milter > hold > scan > injection to Postfix > delivery
This is how it actually works:
Postfix > hold > scan > drop into Postfix
Technically, this is incorrect.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
-----Original Message-----
From: MailScanner
[mailto:mailscanner-bounces+jerry.benton =mailborder.com at lists.mailscanner.in
fo] On Behalf Of Maarten
Sent: Wednesday, December 13, 2017 17:34
To: MailScanner Discussion >
Subject: postfix and mailscanner
Don't want to start a flame war here, but just a question, why does
postfix.org advise against using mailscanner? Saw the following on the
postfix website:
mailscanner: system, works with Postfix and other MTAs. WARNING: This
software uses unsupported methods to manipulate Postfix queue files
directly. This will result in corruption or loss of mail. The mailscanner
authors have sofar refused to discuss a proper access API or protocol.
When reading through mailinglists it seems that some mails can get lost as
in how mailscanner handles mail from the postfix mailqueue, and that it's
safer to use one of the virus/spam/content filters that that uses the SMTP
proxy interface or the Milter Interface. I wouldn't know if this is true or
how to know if any mails every got lost(is there a way to know of having
lost mails), but have there ever been talks between postfix devs and
mailscanner devs about this?
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mark at msapiro.net Thu Dec 14 00:21:51 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Dec 2017 16:21:51 -0800
Subject: postfix and mailscanner
In-Reply-To:
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Message-ID:
On 12/13/2017 03:49 PM, Shawn Iverson wrote:
> For anyone curious, I am researching creating a mailscanner milter for
> postfix.? I have gotten as far to conclude it is possible and that it
> might bring additional functionality when using postfix and mailscanner
> together.? For example, it would be possible to reject a message for
> various reasons and still have detailed reports on the messages.
I think this is great Shawn. The ability to reject mail at incoming SMTP
time is the one single thing that I find lacking in MailScanner.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From Eoin.Kim at rcst.com.au Thu Dec 14 02:01:46 2017
From: Eoin.Kim at rcst.com.au (Eoin Kim)
Date: Thu, 14 Dec 2017 02:01:46 +0000
Subject: SpamAssassin installation failure
In-Reply-To: <518380e5c1a241b68f13b69d2e530517@rcst.com.au>
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
<518380e5c1a241b68f13b69d2e530517@rcst.com.au>
Message-ID:
Hi Shawn,
Just wonder if you require further information regarding this. Thanks.
Eoin
From: Eoin Kim
Sent: Thursday, 14 December 2017 7:32 AM
To: MailScanner Discussion
Subject: RE: SpamAssassin installation failure
Hi Shawn,
The installation without flags looks different but I am not sure if this is successful or not. I?ll attach the installation log file. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 10:05 PM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
If you install without using the flags for install.sh and answer the prompts, does spamassassin install successfully?
On Tue, Dec 12, 2017 at 8:12 PM, Eoin Kim > wrote:
Hi Shawn,
I checked the install.sh script and it looks like --force options is missing.
#Install SpamaAssassin, use standard cpan in normail install, or App::cpanminus in unattended install
perldoc -l ${MODSA} >/dev/null 2>&1
if [ $? != 0 ]; then
clear
echo "${MODSA} is missing. Installing via CPAN ..."; echo;
timewait 1
if [ $AUTOCPAN -eq 0 ]; then
perl -MCPAN -e "CPAN::Shell->force(qw(install ${MODSA} ));"
else
cpanm --no-interactive ${MODSA}
fi
fi
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 9:09 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Hi Shawn,
My apologies for messy emails but I?d like to make things clear. So, here?s what I did step by step:
1. Installed Debian Jessie and upgraded (sudo apt-get update && sudo apt-get upgrade && sudo reboot).
2. Installed few packages: ca-certificates, libgeo-ip-perl, libnet-patricia-perl
3. Downloaded the MailScanner installer.
4. Ran the command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
During the procedure, I watched the log and this showed up.
--> Working on Digest::SHA1
Fetching http://www.cpan.org/authors/id/G/GA/GAAS/Digest-SHA1-2.13.tar.gz ... OK
Configuring Digest-SHA1-2.13 ... OK
Building and testing Digest-SHA1-2.13 ... OK
Successfully installed Digest-SHA1-2.13
1 distribution installed
Mail::SpamAssassin is missing. Installing via CPAN ...
--> Working on Mail::SpamAssassin
Fetching http://www.cpan.org/authors/id/K/KM/KMCGRAIL/SpamAssassin/Mail-SpamAssassin-3.4.1.tar.gz ... OK
Configuring Mail-SpamAssassin-3.004001 ... OK
Building and testing Mail-SpamAssassin-3.004001 ... ! Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
FAIL
It kept going and installation finished. And when I looked the /root/.cpanm/work/1513044980.46831/build.log file, at the end this shows.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:23 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Sorry for flying emails but I used this file - https://s3.amazonaws.com/msv5/release/MailScanner-5.0.6-5.deb.tar.gz
I didn?t clone Github. Thanks.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Eoin Kim
Sent: Wednesday, 13 December 2017 8:18 AM
To: MailScanner Discussion >
Subject: RE: SpamAssassin installation failure
Thanks Shawn,
I am using the latest kernel for your information (I did sudo apt-get update && sudo apt-get upgrade && sudo reboot).
sysadmin at mx1.bne.lab.boof.com:/usr/local/src/MailScanner-5.0.6-5$ uname -a
Linux mx1.bne.lab.boof.com 3.16.0-4-amd64 #1 SMP Debian 3.16.51-2 (2017-12-03) x86_64 GNU/Linux
Thanks again.
Eoin
From: MailScanner [mailto:mailscanner-bounces+eoin.kim=rcst.com.au at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, 13 December 2017 8:15 AM
To: MailScanner Discussion >
Subject: Re: SpamAssassin installation failure
Eoin,
I am spinning up a Jessie instance to see if i can reproduce the issue.
On Tue, Dec 12, 2017 at 5:01 PM, Eoin Kim > wrote:
Hi all,
I am trying to install MailScanner (v.5.0.6-5) on my Debian Jessie and it looks like installing SpamAssassin is failed. Below is the end of log message.
Test Summary Report
-------------------
t/sa_compile.t (Wstat: 512 Tests: 2 Failed: 2)
Failed tests: 1-2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 5 tests but ran 2.
Files=168, Tests=3014, 333 wallclock secs ( 0.69 usr 0.09 sys + 67.79 cusr 5.12 csys = 73.69 CPU)
Result: FAIL
Failed 1/168 test programs. 2/3014 subtests failed.
Makefile:1582: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
-> FAIL Installing Mail::SpamAssassin failed. See /root/.cpanm/work/1513044980.46831/build.log for details. Retry with --force to force install it.
I used this command - ./install.sh --MTA=postfix --installClamav=Y --installCPAN=Y --ignoreDeps=N --ramdiskSize=0
What is the possible cause of this error and how can I rectify this? Thanks a lot.
Eoin Kim
Systems Administrator
RCS Telecommunications
Level 1 ? The Annexe
133 Mary Street
Brisbane, QLD, 4000
Office: 07 3228 0843
Mobile: 0419 726 231
[RCST logo drop shadow]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner
--
Shawn Iverson, CETL
Director of Technology
Rush County Schools
765-932-3901 x1171
iversons at rushville.k12.in.us
[Image removed by sender.][Image removed by sender.]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3384 bytes
Desc: image001.jpg
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 823 bytes
Desc: image002.jpg
URL:
From manuel at palachuk.com Thu Dec 14 16:00:39 2017
From: manuel at palachuk.com (=?utf-8?Q?Manuel_Palachuk?=)
Date: Thu, 14 Dec 2017 11:00:39 -0500
Subject: One domain in my postfix config is not being scanned by mailscanner
Message-ID:
Hello,
I have several domains in postfix and all are sending and receiving email fine.
Mailscanner is installed with a very standard setup with basic install as indicated on the mailscanner setup page.
i see inbound email in mail.log being scanned by mailscanner, and is tagging emails as it should for all domains except one.
One domain is receiving large numbers of spam emails and it appears that mailscanner is not tagging those emails as it does for all other domains.
The emails are blatant spam that always gets tagged for other recipient domains.
how do I troubleshoot one domain not having it's emails tagged?
Thank you
Manuel Palachuk
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jerry.benton at mailborder.com Thu Dec 14 18:17:19 2017
From: jerry.benton at mailborder.com (Jerry Benton)
Date: Thu, 14 Dec 2017 13:17:19 -0500
Subject: One domain in my postfix config is not being scanned by
mailscanner
In-Reply-To:
References:
Message-ID: <004401d37507$c75f2a80$561d7f80$@mailborder.com>
Is that domain actually going through the server? Unless you have configured it to do so, it is not going to pick and choose what it decides to scan for destination domains.
--
Jerry Benton
www.mailborder.com
+1 (843) 800-8605
+44 (020) 3883-8605
From: MailScanner [mailto:mailscanner-bounces+jerry.benton=mailborder.com at lists.mailscanner.info] On Behalf Of Manuel Palachuk via MailScanner
Sent: Thursday, December 14, 2017 11:01
To: mailscanner at lists.mailscanner.info
Cc: Manuel Palachuk
Subject: One domain in my postfix config is not being scanned by mailscanner
Hello,
I have several domains in postfix and all are sending and receiving email fine.
Mailscanner is installed with a very standard setup with basic install as indicated on the mailscanner setup page.
i see inbound email in mail.log being scanned by mailscanner, and is tagging emails as it should for all domains except one.
One domain is receiving large numbers of spam emails and it appears that mailscanner is not tagging those emails as it does for all other domains.
The emails are blatant spam that always gets tagged for other recipient domains.
how do I troubleshoot one domain not having it's emails tagged?
Thank you
Manuel Palachuk
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From kevin.miller at juneau.org Thu Dec 14 18:22:00 2017
From: kevin.miller at juneau.org (Kevin Miller)
Date: Thu, 14 Dec 2017 18:22:00 +0000
Subject: postfix and mailscanner
In-Reply-To:
References: <40ecb8f5-7bb6-1810-70a3-31df268ed267@feedmebits.nl>
<01f401d37462$e0a122f0$a1e368d0$@mailborder.com>
Message-ID:
I vaguely recall some discussion about that from probably 10 or more years ago. IIRC, Jules? steered away from that sort of approach, as it was called for each message. He specifically designed MailScanner to work on batches for more efficiency. I have no idea where the bell curve falls between the two. With a low level volume it probably doesn?t make much difference but with a very large number of messages coming in there?s probably some efficiencies to be gained. But with today?s hardware and memory available, it may be a wash.
I run MailScanner and Postfix and have never had a problem (that I know of). I also reject a lot of mail at MTA time via greylisting, RBLs, SPF, and lack of full circle reverse DNS. That means, of course, that if one of my users asked if mail was mis-identified as spam that I have to first check MailScanner (via the Mailwtch interface) and if I don?t see it there, jump onto the CLI and grep mail.log for filtered mail. No biggie, but one stop shopping would be a welcome addition?
...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: 307357
From: MailScanner [mailto:mailscanner-bounces+kevin.miller=juneau.org at lists.mailscanner.info] On Behalf Of Shawn Iverson
Sent: Wednesday, December 13, 2017 2:50 PM
To: MailScanner Discussion
Subject: Re: postfix and mailscanner
For anyone curious, I am researching creating a mailscanner milter for postfix. I have gotten as far to conclude it is possible and that it might bring additional functionality when using postfix and mailscanner together. For example, it would be possible to reject a message for various reasons and still have detailed reports on the messages. It would also be possible to have more granular whitelisting capabilities (virus scan only, spam scan only, no scan, etc.). It is a ways off, but I've been looking at milter code on various things for a while.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From mark at msapiro.net Thu Dec 14 18:55:00 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Dec 2017 10:55:00 -0800
Subject: One domain in my postfix config is not being scanned by
mailscanner
In-Reply-To:
References:
Message-ID: <15c4ebf0-512f-9ac2-54df-8d11eb0ae2d7@msapiro.net>
On 12/14/2017 08:00 AM, Manuel Palachuk via MailScanner wrote:
>
> One domain is receiving large numbers of spam emails and it appears that
> mailscanner is not tagging those emails as it does for all other domains.
>
> The emails are blatant spam that always gets tagged for other recipient
> domains.
Do you have any rulesets configured for settings like Scan Messages or
Spam Checks?
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
From iversons at rushville.k12.in.us Thu Dec 14 19:06:28 2017
From: iversons at rushville.k12.in.us (Shawn Iverson)
Date: Thu, 14 Dec 2017 14:06:28 -0500
Subject: SpamAssassin installation failure
In-Reply-To:
References: <07f4dc8ea5bf41148575acfe1d9fd165@rcst.com.au>
<9a79299c4d844ca3afd0101607336e80@rcst.com.au>
<077cb9fbb23c4321b0a94d34f891a8e6@rcst.com.au>
<518380e5c1a241b68f13b69d2e530517@rcst.com.au>