v4.85.1.0 Beta for Linux RPM Available

[Jerry Benton]

After an absurd amount of face-palming over two weeks:

https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz

Note: This is beta! If you install on on a production box, that’s on you.


Please give me feedback via this list if you test this build. It is built for RHEL 5,6,7 and tested on CentOS 32 and 64 bit (Except for EL7 of course.) I built the installer to use the Yum package manger as much as possible.

- Order of install priority is Base > EPEL > Custom RPM > CPAN (All based on the options you select.)
- For RHEL 6 the dependencies are fulfilled 100% by yum if you elect to use EPEL.
- For RHEL 5 only tnef is missing via yum when using EPEL. The installer gives the option to install an RPM package I built from source if it can’t find tnef after trying to install it with yum.
- For RHEL 7 tnef, perl-Filesys-Df, and perl-Sys-Hostname-Long and not available in base or EPEL. You are given the option to install these via RPMs after the installer tries to install them using yum. Tnef was built by me from source and the others were built by other people. From what I tested they seem to work fine.
- You can elect to not install perl-Filesys-Df and perl-Sys-Hostname-Long from these RPMs and they will be installed via CPAN if you want to do that.
- If you elect to install missing modules via CPAN, —nodeps will be used when installing the MailScanner RPM. This is because rpm’s auto require does not recognize things not installed via RPM. So, for example, even if Filesys::Df is installed and available to perl because the installer used CPAN to install it, the rpm installer doesn’t see it.
- The last released version of MailScanner had 2 dependencies attached to the RPM: perl and perl-MIME-Tools. This version has 85 dependencies attached to the RPM. Why? Glad you asked … I poured over all of the MailScanner source code. If a perl module is used in the code I made it a dependency. (Many are included with the base perl package.) If an optional module like Mail::ClamAV is available, its dependency was added, which would be openssl-devel and Inline::C in the case of Mail::ClamAV.
- Using ClamAV as an example again … The installer will ask if you want to install ClamAV, but only if you elect to use EPEL. (Not available in base.) If you elect to install ClamAV the installer will check for the perl module Mail::ClamAV, which is used by MailScanner if you are using ClamAV. The installer will check to see if it is installed. If not, it goes through the Base > EPEL > Custom > CPAN routine of installing it. The same is true for Mail::SpamAssassin if you elect to install spamassassin.


I have already completed the tarball source for the next version, but I want to go over it again. SuSE after that. After that I will work on the Debian package. FreeBSD guys, you are on your own :)

-
Jerry Benton
www.mailborder.com

[Johan Hendriks]

I will try the source on FreeBSD maybe later next week. I am not a
developer, but will try to make it run.
Why are we always left in the cold. :-)
FreeBSD is so nice to work with.

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.
Please give me feedback via this list if you test this build. It is built
for RHEL 5,6,7 and tested on CentOS 32 and 64 bit (Except for EL7 of
course.) I built the installer to use the Yum package manger as much as
possible.
- Order of install priority is Base > EPEL > Custom RPM > CPAN (All based
on the options you select.)
- For RHEL 6 the dependencies are fulfilled 100% by yum if you elect to use EPEL.
- For RHEL 5 only tnef is missing via yum when using EPEL. The installer
gives the option to install an RPM package I built from source if it can’t
find tnef after trying to install it with yum.
- For RHEL 7 tnef, perl-Filesys-Df, and perl-Sys-Hostname-Long and not
available in base or EPEL. You are given the option to install these via
RPMs after the installer tries to install them using yum. Tnef was built by
me from source and the others were built by other people. From what I
tested they seem to work fine.
- You can elect to not install perl-Filesys-Df and perl-Sys-Hostname-Long
from these RPMs and they will be installed via CPAN if you want to do that.
- If you elect to install missing modules via CPAN, —nodeps will be used
when installing the MailScanner RPM. This is because rpm’s auto require
does not recognize things not installed via RPM. So, for example, even if
Filesys::Df is installed and available to perl because the installer used
CPAN to install it, the rpm installer doesn’t see it.
- The last released version of MailScanner had 2 dependencies attached to
the RPM: perl and perl-MIME-Tools. This version has 85 dependencies
attached to the RPM. Why? Glad you asked 
 I poured over all of the
MailScanner source code. If a perl module is used in the code I made it a
dependency. (Many are included with the base perl package.) If an optional
module like Mail::ClamAV is available, its dependency was added, which
would be openssl-devel and Inline::C in the case of Mail::ClamAV.
- Using ClamAV as an example again 
 The installer will ask if you want to
install ClamAV, but only if you elect to use EPEL. (Not available in base.)
If you elect to install ClamAV the installer will check for the perl module
Mail::ClamAV, which is used by MailScanner if you are using ClamAV. The
installer will check to see if it is installed. If not, it goes through the
Base > EPEL > Custom > CPAN routine of installing it. The same is true for
Mail::SpamAssassin if you elect to install spamassassin.
I have already completed the tarball source for the next version, but I
want to go over it again. SuSE after that. After that I will work on the
Debian package. FreeBSD guys, you are on your own :)
-
Jerry Benton
www.mailborder.com
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Johan Hendriks]

Sorry forget to ask.
Where can I find the tarball?

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.
Please give me feedback via this list if you test this build. It is built
for RHEL 5,6,7 and tested on CentOS 32 and 64 bit (Except for EL7 of
course.) I built the installer to use the Yum package manger as much as
possible.
- Order of install priority is Base > EPEL > Custom RPM > CPAN (All based
on the options you select.)
- For RHEL 6 the dependencies are fulfilled 100% by yum if you elect to use EPEL.
- For RHEL 5 only tnef is missing via yum when using EPEL. The installer
gives the option to install an RPM package I built from source if it can’t
find tnef after trying to install it with yum.
- For RHEL 7 tnef, perl-Filesys-Df, and perl-Sys-Hostname-Long and not
available in base or EPEL. You are given the option to install these via
RPMs after the installer tries to install them using yum. Tnef was built by
me from source and the others were built by other people. From what I
tested they seem to work fine.
- You can elect to not install perl-Filesys-Df and perl-Sys-Hostname-Long
from these RPMs and they will be installed via CPAN if you want to do that.
- If you elect to install missing modules via CPAN, —nodeps will be used
when installing the MailScanner RPM. This is because rpm’s auto require
does not recognize things not installed via RPM. So, for example, even if
Filesys::Df is installed and available to perl because the installer used
CPAN to install it, the rpm installer doesn’t see it.
- The last released version of MailScanner had 2 dependencies attached to
the RPM: perl and perl-MIME-Tools. This version has 85 dependencies
attached to the RPM. Why? Glad you asked 
 I poured over all of the
MailScanner source code. If a perl module is used in the code I made it a
dependency. (Many are included with the base perl package.) If an optional
module like Mail::ClamAV is available, its dependency was added, which
would be openssl-devel and Inline::C in the case of Mail::ClamAV.
- Using ClamAV as an example again 
 The installer will ask if you want to
install ClamAV, but only if you elect to use EPEL. (Not available in base.)
If you elect to install ClamAV the installer will check for the perl module
Mail::ClamAV, which is used by MailScanner if you are using ClamAV. The
installer will check to see if it is installed. If not, it goes through the
Base > EPEL > Custom > CPAN routine of installing it. The same is true for
Mail::SpamAssassin if you elect to install spamassassin.
I have already completed the tarball source for the next version, but I
want to go over it again. SuSE after that. After that I will work on the
Debian package. FreeBSD guys, you are on your own :)
-
Jerry Benton
www.mailborder.com
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Jerry Benton]

Johan,

Not released yet. I want to work on it some more and double check it.

-
Jerry Benton
www.mailborder.com

Post by Johan Hendriks
Sorry forget to ask.
Where can I find the tarball?
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz <https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz>
Note: This is beta! If you install on on a production box, that’s on you.
Please give me feedback via this list if you test this build. It is built for RHEL 5,6,7 and tested on CentOS 32 and 64 bit (Except for EL7 of course.) I built the installer to use the Yum package manger as much as possible.
- Order of install priority is Base > EPEL > Custom RPM > CPAN (All based on the options you select.)
- For RHEL 6 the dependencies are fulfilled 100% by yum if you elect to use EPEL.
- For RHEL 5 only tnef is missing via yum when using EPEL. The installer gives the option to install an RPM package I built from source if it can’t find tnef after trying to install it with yum.
- For RHEL 7 tnef, perl-Filesys-Df, and perl-Sys-Hostname-Long and not available in base or EPEL. You are given the option to install these via RPMs after the installer tries to install them using yum. Tnef was built by me from source and the others were built by other people. From what I tested they seem to work fine.
- You can elect to not install perl-Filesys-Df and perl-Sys-Hostname-Long from these RPMs and they will be installed via CPAN if you want to do that.
- If you elect to install missing modules via CPAN, —nodeps will be used when installing the MailScanner RPM. This is because rpm’s auto require does not recognize things not installed via RPM. So, for example, even if Filesys::Df is installed and available to perl because the installer used CPAN to install it, the rpm installer doesn’t see it.
- The last released version of MailScanner had 2 dependencies attached to the RPM: perl and perl-MIME-Tools. This version has 85 dependencies attached to the RPM. Why? Glad you asked 
 I poured over all of the MailScanner source code. If a perl module is used in the code I made it a dependency. (Many are included with the base perl package.) If an optional module like Mail::ClamAV is available, its dependency was added, which would be openssl-devel and Inline::C in the case of Mail::ClamAV.
- Using ClamAV as an example again 
 The installer will ask if you want to install ClamAV, but only if you elect to use EPEL. (Not available in base.) If you elect to install ClamAV the installer will check for the perl module Mail::ClamAV, which is used by MailScanner if you are using ClamAV. The installer will check to see if it is installed. If not, it goes through the Base > EPEL > Custom > CPAN routine of installing it. The same is true for Mail::SpamAssassin if you elect to install spamassassin.
I have already completed the tarball source for the next version, but I want to go over it again. SuSE after that. After that I will work on the Debian package. FreeBSD guys, you are on your own :)
-
Jerry Benton
www.mailborder.com <http://www.mailborder.com/>
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner <http://lists.mailscanner.info/mailman/listinfo/mailscanner>
Before posting, read http://wiki.mailscanner.info/posting <http://wiki.mailscanner.info/posting>
Support MailScanner development - buy the book off the website!
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Christophe GRENIER]

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that¢s on you.

Hi

I have tested the install script on CentOS 6.

Here are my results:
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected

- For RHEL 6 the dependencies are NOT fulfilled 100% by yum even if you
elect to use EPEL:
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...

- bzip2-devel need to be installed otherwise Mail::ClamAV failed to be
compiled:
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'

- IMOO answers should default to recommanded values (Y instead of N).

- After rerunning the install script,
/etc/MailScanner/phishing.bad.sites.conf is missing (renamed as .old):
MailScanner --lint

Could not read file /etc/MailScanner/phishing.bad.sites.conf at /usr/lib/MailScanner/MailScanner/Config.pm line 2864
Error in line 990, file "/etc/MailScanner/phishing.bad.sites.conf" for phishingblacklist does not exist (or can not be read) at /usr/lib/MailScanner/MailScanner/Config.pm line 3066

- Some configurations is needed (I am using postfix), you may want to
add it in QuickInstall.txt:

Could not read directory /var/spool/mqueue at /usr/lib/MailScanner/MailScanner/Config.pm line 2874
Error in configuration file line 169, directory /var/spool/mqueue for outqueuedir does not exist (or is not readable) at /usr/lib/MailScanner/MailScanner/Config.pm line 3238
Read 868 hostnames from the phishing whitelist

- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check
filenames and filetypes. Virus scanning is not affected.

Two possibilities: switch to internal unrar or install it...

- config: failed to parse line, skipping, in "/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0

I haven't test this version of MailScanner for the moment, only the
install script.

Thanks for your work

Regards,

Christophe

[Jerry Benton]

Thanks for the feedback.

- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.


Thanks for testing it out.


-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at /usr/lib/MailScanner/MailScanner/Config.pm line 2864
Error in line 990, file "/etc/MailScanner/phishing.bad.sites.conf" for phishingblacklist does not exist (or can not be read) at /usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at /usr/lib/MailScanner/MailScanner/Config.pm line 2874
Error in configuration file line 169, directory /var/spool/mqueue for outqueuedir does not exist (or is not readable) at /usr/lib/MailScanner/MailScanner/Config.pm line 3238
Read 868 hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check
filenames and filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in "/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Randal, Phil]

Mail::Clamav should be sent to the great bit bucket in the sky.

If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.

Cheers,

Phil


-----Original Message-----
From: mailscanner-***@lists.mailscanner.info [mailto:mailscanner-***@lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available

Thanks for the feedback.

- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.


Thanks for testing it out.


-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
***@lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE

"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."

[Jerry Benton]

Phil,

I agree, but someone else may not. It doesn’t hurt to have the module available.

-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Glenn Steen]

Actually, it could. The way it sucks up resources, it really should
not only be deprecated, but removed entirely. Loading a fat copy of
the sigs into every MailWScanner child was OK when the sigs were
relatively few, but ... these days, the only sane way to use clamav is
via clamd.

Cheers!
--
-- Glenn

Post by Jerry Benton
Phil,
I agree, but someone else may not. It doesn’t hurt to have the module available.
-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se

[Randal, Phil]

To expand on that:

1: each child has a full copy of the ClamAV database - that makes MailScanner children real memory hogs

2: each child has to load that DB on startup - which adds to server load and slows down throughput

3: weren't there issues with Mail::ClamAV and later versions of ClamAV, anyhow? See https://rt.cpan.org/Public/Bug/Display.html?id=96876

Cheers,

Phil

-----Original Message-----
From: mailscanner-***@lists.mailscanner.info [mailto:mailscanner-***@lists.mailscanner.info] On Behalf Of Glenn Steen
Sent: 18 February 2015 14:41
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available

Actually, it could. The way it sucks up resources, it really should not only be deprecated, but removed entirely. Loading a fat copy of the sigs into every MailWScanner child was OK when the sigs were relatively few, but ... these days, the only sane way to use clamav is via clamd.

Cheers!
--
-- Glenn

Post by Jerry Benton
Phil,
I agree, but someone else may not. It doesn’t hurt to have the module available.
-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Jerry Benton
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.g
z
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595 Registered
office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
--
MailScanner mailing list
***@lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!

[Jerry Benton]

Ok, we need to stop beating this dead horse.

In General:
- I am aware that clamd is better.
- I am aware of how a MailScanner child behaves when using the Mail::ClamAV module and the implications of doing so.
- I am aware that any perl module can have, or appear to have, a bug when a new version of some other software comes out.

The Installer:
- You do not have to use the CPAN module remediation when using the new installer if you don’t want to.
- You don’t have to opt to install ClamAV during installation and thus the installer will not even attempt to install the Mail::ClamAV module even if you select CPAN remediation for other items.
- You can edit the installer and comment out line number 374 before you run it in the event that you do want to installer to try and remediate modules via CPAN but not Mail::ClamAV.

The Conclusion:
- The Mail::ClamAV perl module install option is staying in place until any use or reference to that module has been completely removed from the MailScanner source.


So please stop beating me over the head regarding this issue. I am sure that each and every one raising this issue knows, or should know, that you just can’t rip something out based on your personal opinion regardless of supporting evidence without thorough review and testing of the item to include the implications of removing said item in respect to the insane number of MailScanner installations out there.

If you have an actual solution, present it. Please do not just make a statement on how it should be in your opinion without a serious amount of research and testing supporting a documented solution. If you do this and it makes sense, then I guarantee you it will get done.


-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
1: each child has a full copy of the ClamAV database - that makes MailScanner children real memory hogs
2: each child has to load that DB on startup - which adds to server load and slows down throughput
3: weren't there issues with Mail::ClamAV and later versions of ClamAV, anyhow? See https://rt.cpan.org/Public/Bug/Display.html?id=96876
Cheers,
Phil
-----Original Message-----
Sent: 18 February 2015 14:41
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Actually, it could. The way it sucks up resources, it really should not only be deprecated, but removed entirely. Loading a fat copy of the sigs into every MailWScanner child was OK when the sigs were relatively few, but ... these days, the only sane way to use clamav is via clamd.
Cheers!
--
-- Glenn

Post by Jerry Benton
Phil,
I agree, but someone else may not. It doesn’t hurt to have the module available.
-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Jerry Benton
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.g
z
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595 Registered
office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Randal, Phil]

My comments were there to encourage list readers to switch to clamd if they already haven't.

Cheers,

Phil


-----Original Message-----
From: mailscanner-***@lists.mailscanner.info [mailto:mailscanner-***@lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: 18 February 2015 16:25
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available

Ok, we need to stop beating this dead horse.

In General:
- I am aware that clamd is better.
- I am aware of how a MailScanner child behaves when using the Mail::ClamAV module and the implications of doing so.
- I am aware that any perl module can have, or appear to have, a bug when a new version of some other software comes out.

The Installer:
- You do not have to use the CPAN module remediation when using the new installer if you don’t want to.
- You don’t have to opt to install ClamAV during installation and thus the installer will not even attempt to install the Mail::ClamAV module even if you select CPAN remediation for other items.
- You can edit the installer and comment out line number 374 before you run it in the event that you do want to installer to try and remediate modules via CPAN but not Mail::ClamAV.

The Conclusion:
- The Mail::ClamAV perl module install option is staying in place until any use or reference to that module has been completely removed from the MailScanner source.


So please stop beating me over the head regarding this issue. I am sure that each and every one raising this issue knows, or should know, that you just can’t rip something out based on your personal opinion regardless of supporting evidence without thorough review and testing of the item to include the implications of removing said item in respect to the insane number of MailScanner installations out there.

If you have an actual solution, present it. Please do not just make a statement on how it should be in your opinion without a serious amount of research and testing supporting a documented solution. If you do this and it makes sense, then I guarantee you it will get done.


-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
1: each child has a full copy of the ClamAV database - that makes
MailScanner children real memory hogs
2: each child has to load that DB on startup - which adds to server
load and slows down throughput
3: weren't there issues with Mail::ClamAV and later versions of
ClamAV, anyhow? See
https://rt.cpan.org/Public/Bug/Display.html?id=96876
Cheers,
Phil
-----Original Message-----
Steen
Sent: 18 February 2015 14:41
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Actually, it could. The way it sucks up resources, it really should not only be deprecated, but removed entirely. Loading a fat copy of the sigs into every MailWScanner child was OK when the sigs were relatively few, but ... these days, the only sane way to use clamav is via clamd.
Cheers!
--
-- Glenn

Post by Jerry Benton
Phil,
I agree, but someone else may not. It doesn’t hurt to have the module available.
-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Jerry Benton
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.
g
z
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595 Registered
office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
***@lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!

[Jerry Benton]

Again, I do not disagree. However, there may be a situation for someone, somewhere, that cannot meet what we both consider to be sane. The file for the perl module existing on a system is not going to do any harm. The “rm” command could do a lot more damage if used improperly, but we are not going to remove it just because of that.

-
Jerry Benton
www.mailborder.com

Post by Glenn Steen
Actually, it could. The way it sucks up resources, it really should
not only be deprecated, but removed entirely. Loading a fat copy of
the sigs into every MailWScanner child was OK when the sigs were
relatively few, but ... these days, the only sane way to use clamav is
via clamd.
Cheers!
--
-- Glenn

Post by Jerry Benton
Phil,
I agree, but someone else may not. It doesn’t hurt to have the module available.
-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be installed with a note to the user to configure MailScanner to use clamd.
Cheers,
Phil
-----Original Message-----
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Rick Cooper]

Post by Glenn Steen
Actually, it could. The way it sucks up resources, it really should
not only be deprecated, but removed entirely. Loading a fat copy of
the sigs into every MailWScanner child was OK when the sigs were
relatively few, but ... these days, the only sane way to use clamav is
via clamd.
Cheers!
--
-- Glenn
On 18 February 2015 at 14:13, Jerry Benton

Phil,
I agree, but someone else may not. It doesn't hurt to have the
module available.
-
Jerry Benton
www.mailborder.com

On Feb 18, 2015, at 7:35 AM, Randal, Phil
Mail::Clamav should be sent to the great bit bucket in the sky.
If ClamAV is selected during install, clamd and clamav should be
installed with a note to the user to configure MailScanner to use
clamd.
Cheers,
Phil
-----Original Message-----
Jerry Benton
Sent: 16 February 2015 21:24
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script
attempts to install it if you elect to install Clam AV. There is no
RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not
as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did
install during the tests I did.
- You are missing /var/spool/mqueue because either you did not
install an MTA or you did not configure MailScanner.conf to use
your MTA. The script does not install an MTA for you or setup
MailScanner.conf. If you installed sendmail, you wouldn't get the
errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the
/etc/mail/spamassassin directory to the spam.assassin.prefs.conf
file in /etc/MailScanner. If you did not elect to install
spamassassin the link won't be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

On Feb 16, 2015, at 12:23 PM, Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that's
on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
- For RHEL 6 the dependencies are NOT fulfilled 100% by yum even
if you elect to use EPEL: File::ShareDir::Install is missing.
Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
- bzip2-devel need to be installed otherwise Mail::ClamAV failed
to be compiled: ... /usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
| | | ==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are
those of the individual and not necessarily those of Hoople Ltd.
You should be aware that Hoople Ltd. monitors its email service.
This e-mail and any attached files are confidential and intended
solely for the use of the addressee. This communication may contain
material protected by law from being passed on. If you are not the
intended recipient and have received this e-mail in error, you are
advised that any use, dissemination, forwarding, printing or
copying of this e-mail is strictly prohibited. If you have received
this e-mail in error please contact the sender immediately and
destroy all copies of it." -- MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se

This applies to SpamAssassin as well. I sent Jules code to move MailScanner
to use the Spamd process years ago. Now the clamav module had a lot of
issues because when internal defs within the clam code changed the module
would puke until someone patched the module but it makes no sense to me why
anything MailScanner shares should be based on a perl module if there is a
daemon available to communicate with. Spamd protocol is pretty simple and
fairly easy to integrate within MailScanner. The difference in speed is
pretty much nil but the difference in MailScanner memory usage per child is
significant. When I originally worked with JF to integrate the clamd code
his biggest hesitation was he wasn't comfortable with network code... I
would bet that was the biggest reason for handling postfix the way it's
handled as well. Whoever is currently developing MS should really look at
moving toward spamd support in place of the perl module

Rick

[Kevin Miller]

So I'm confused. Pretty much my normal state <g>.

Is the clamavmodule loaded at MS startup, or merely installed on the drive? If the latter, then there's no performance hit unless you're down to your last few hundred bytes of free space, in which case you probably have imminent bigger issues.

In my MailScanner.conf is the line:
Virus Scanners = f-secure clamd

I get hits with both scanners, so apparently clamd is working as advertised. I don't understand the reference to "network code" and "moving toward spamd support". Isn't spamd support there already?

If all the installer is doing is dropping a perl module in place then it's just offering an option to those that perhaps can't run clamd for some reason, right? Or am I missing something...

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: [phone], Fax: [phone]
Registered Linux User No: 307357

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move
MailScanner to use the Spamd process years ago. Now the clamav module
had a lot of issues because when internal defs within the clam code
changed the module would puke until someone patched the module but it
makes no sense to me why anything MailScanner shares should be based on
a perl module if there is a daemon available to communicate with. Spamd
protocol is pretty simple and fairly easy to integrate within
MailScanner. The difference in speed is pretty much nil but the
difference in MailScanner memory usage per child is significant. When I
originally worked with JF to integrate the clamd code his biggest
hesitation was he wasn't comfortable with network code... I would bet
that was the biggest reason for handling postfix the way it's handled as
well. Whoever is currently developing MS should really look at moving
toward spamd support in place of the perl module

[Rick Cooper]

Post by Kevin Miller
So I'm confused. Pretty much my normal state <g>.
Is the clamavmodule loaded at MS startup, or merely installed on the
drive? If the latter, then there's no performance hit unless you're
down to your last few hundred bytes of free space, in which case you
probably have imminent bigger issues.
Virus Scanners = f-secure clamd
I get hits with both scanners, so apparently clamd is working as
advertised. I don't understand the reference to "network code" and
"moving toward spamd support". Isn't spamd support there already?

If MS is not configured to use the module it doesn't load anything. The
network code statement really should have read sockets in general, TCP or
unix as both clamd and spamd will talk on either. With clamd MailScanner
communicates with the daemon via sockets (TCP/unix) and there is nothing
loaded such as signatures. MailScanner does NOT use spamd it uses a perl
module much like clamav module so for each child everything is loaded, IIRC
it's on the order of about 30+MB per child. MailScanner has no use for a
running instance of spamd, if it did it would reduce the MailScanner foot
print nearly as much as supporting clamd did way back when I first wrote the
code and JF finally agreed to include it in the code base.

Post by Kevin Miller
If all the installer is doing is dropping a perl module in place then
it's just offering an option to those that perhaps can't run clamd
for some reason, right? Or am I missing something...
...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: [phone], Fax: [phone]
Registered Linux User No: 307357

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move
MailScanner to use the Spamd process years ago. Now the clamav module
had a lot of issues because when internal defs within the clam code
changed the module would puke until someone patched the module but it
makes no sense to me why anything MailScanner shares should be based
on a perl module if there is a daemon available to communicate with.
Spamd protocol is pretty simple and fairly easy to integrate within
MailScanner. The difference in speed is pretty much nil but the
difference in MailScanner memory usage per child is significant.
When I originally worked with JF to integrate the clamd code his
biggest hesitation was he wasn't comfortable with network code... I
would bet that was the biggest reason for handling postfix the way
it's handled as well. Whoever is currently developing MS should
really look at moving toward spamd support in place of the perl
module

[Kevin Miller]

Ugh. Brain fart. Clamd != spamd. Got it.

Sigh...

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: [phone], Fax: [phone]
Registered Linux User No: 307357

Post by Randal, Phil
-----Original Message-----
Sent: Wednesday, February 18, 2015 11:00 AM
To: 'MailScanner discussion'
Subject: RE: v4.85.1.0 Beta for Linux RPM Available

Post by Kevin Miller
So I'm confused. Pretty much my normal state <g>.
Is the clamavmodule loaded at MS startup, or merely installed on the
drive? If the latter, then there's no performance hit unless you're
down to your last few hundred bytes of free space, in which case you
probably have imminent bigger issues.
Virus Scanners = f-secure clamd
I get hits with both scanners, so apparently clamd is working as
advertised. I don't understand the reference to "network code" and
"moving toward spamd support". Isn't spamd support there already?

If MS is not configured to use the module it doesn't load anything. The
network code statement really should have read sockets in general, TCP
or unix as both clamd and spamd will talk on either. With clamd
MailScanner communicates with the daemon via sockets (TCP/unix) and
there is nothing loaded such as signatures. MailScanner does NOT use
spamd it uses a perl module much like clamav module so for each child
everything is loaded, IIRC it's on the order of about 30+MB per child.
MailScanner has no use for a running instance of spamd, if it did it
would reduce the MailScanner foot print nearly as much as supporting
clamd did way back when I first wrote the code and JF finally agreed to
include it in the code base.

Post by Kevin Miller
If all the installer is doing is dropping a perl module in place then
it's just offering an option to those that perhaps can't run clamd for
some reason, right? Or am I missing something...
...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
307357

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move
MailScanner to use the Spamd process years ago. Now the clamav module
had a lot of issues because when internal defs within the clam code
changed the module would puke until someone patched the module but it
makes no sense to me why anything MailScanner shares should be based
on a perl module if there is a daemon available to communicate with.
Spamd protocol is pretty simple and fairly easy to integrate within
MailScanner. The difference in speed is pretty much nil but the
difference in MailScanner memory usage per child is significant.
When I originally worked with JF to integrate the clamd code his
biggest hesitation was he wasn't comfortable with network code... I
would bet that was the biggest reason for handling postfix the way
it's handled as well. Whoever is currently developing MS should
really look at moving toward spamd support in place of the perl
module

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Jerry Benton]

Post by Kevin Miller
If all the installer is doing is dropping a perl module in place then it's just offering an option to those that perhaps can't run clamd for some reason, right? Or am I missing something...

That is correct and my point.


-
Jerry Benton
www.mailborder.com

[Peter Bonivart]

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move MailScanner
to use the Spamd process years ago. Now the clamav module had a lot of
issues because when internal defs within the clam code changed the module
would puke until someone patched the module but it makes no sense to me why
anything MailScanner shares should be based on a perl module if there is a
daemon available to communicate with. Spamd protocol is pretty simple and
fairly easy to integrate within MailScanner. The difference in speed is
pretty much nil but the difference in MailScanner memory usage per child is
significant. When I originally worked with JF to integrate the clamd code
his biggest hesitation was he wasn't comfortable with network code... I
would bet that was the biggest reason for handling postfix the way it's
handled as well. Whoever is currently developing MS should really look at
moving toward spamd support in place of the perl module

That's still a great idea, I remember it from back in the day.
However, I think it's high time to close the wish list for this long
awaited release and start filling it for the next one or we may have
to wait a few more years. :)

/peter

[Jerry Benton]

Post by Peter Bonivart
That's still a great idea, I remember it from back in the day.
However, I think it's high time to close the wish list for this long
awaited release and start filling it for the next one or we may have
to wait a few more years. :)

I agreed to take over as lead for the project because my Mailborder business depends on the success of MailScanner. I have developed an affinity for things like food and shelter, so it is deeply in my interest that the MailScanner project succeed.

-
Jerry Benton
www.mailborder.com

[Kevin Miller]

Regardless of motive, we all appreciate your work in keeping MailScanner alive!

Re: the Postfix integration, Jules mentioned the disagreement between him and Venema on more than on occasion. The issue was one of efficiency, IIRC. MailScanner batches the virus and spam scanning on up to 30 messages at once (or some such). Doing it with a milter is going to spawn a scan for each inbound message taking more system resources. Or so the theory goes. I don't have any imperical data to substantiate the practical difference on a high volume mail server, but I always agreed with Jules because 1, he's a heck of a nice guy, and 2, I used sendmail with MailScanner. Gotta root for the home team after all. ;-) I got the impression that it was a bit of pride and a "not invented here" attitude on the postfix side but I've never had any interaction with Venema so that may not be the case at all.

I'm going to try Postfix on my new gateways, mostly because it purports to do LDAP lookups against AD for recipient verification. Exchange 2013 won't properly let me do a call-ahead with smf-sav so I need some sort of LDAP integration to cull out the non-existant users at MTA time to avoid back-scatter.

If you do attempt to implement a solution after the fashion that Venema recommends, it would be instructive to test it against a stock MailScanner installation, capturing time and load statistics. It may be a wash, or it may be that there's a significant difference. I burn through maybe 10K messages a day, with around 650 users so my servers probably wouldn't know the difference. I'd imagine that it would make a big difference however for servers that are doing multi-million messages a day...

...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: [phone], Fax: [phone]
Registered Linux User No: 307357

Post by Randal, Phil
-----Original Message-----
Sent: Wednesday, February 18, 2015 1:15 PM
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available

Post by Peter Bonivart
That's still a great idea, I remember it from back in the day.
However, I think it's high time to close the wish list for this long
awaited release and start filling it for the next one or we may have
to wait a few more years. :)

I agreed to take over as lead for the project because my Mailborder
business depends on the success of MailScanner. I have developed an
affinity for things like food and shelter, so it is deeply in my
interest that the MailScanner project succeed.
-
Jerry Benton
www.mailborder.com
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Jason Ede]

-----Original Message-----
From: mailscanner-***@lists.mailscanner.info [mailto:mailscanner-***@lists.mailscanner.info] On Behalf Of Kevin Miller
Sent: 18 February 2015 22:56
To: 'MailScanner discussion'
Subject: RE: v4.85.1.0 Beta for Linux RPM Available



Regardless of motive, we all appreciate your work in keeping MailScanner alive!



Re: the Postfix integration, Jules mentioned the disagreement between him and Venema on more than on occasion. The issue was one of efficiency, IIRC. MailScanner batches the virus and spam scanning on up to 30 messages at once (or some such). Doing it with a milter is going to spawn a scan for each inbound message taking more system resources. Or so the theory goes. I don't have any imperical data to substantiate the practical difference on a high volume mail server, but I always agreed with Jules because 1, he's a heck of a nice guy, and 2, I used sendmail with MailScanner. Gotta root for the home team after all. ;-) I got the impression that it was a bit of pride and a "not invented here" attitude on the postfix side but I've never had any interaction with Venema so that may not be the case at all.



I'm going to try Postfix on my new gateways, mostly because it purports to do LDAP lookups against AD for recipient verification. Exchange 2013 won't properly let me do a call-ahead with smf-sav so I need some sort of LDAP integration to cull out the non-existant users at MTA time to avoid back-scatter.



If you do attempt to implement a solution after the fashion that Venema recommends, it would be instructive to test it against a stock MailScanner installation, capturing time and load statistics. It may be a wash, or it may be that there's a significant difference. I burn through maybe 10K messages a day, with around 650 users so my servers probably wouldn't know the difference. I'd imagine that it would make a big difference however for servers that are doing multi-million messages a day...



We've always used postfix with MailScanner and never had a problem with it. At their peak our 2 servers were having around 5-6million connection attempts per month out of which MS scanned around 200,000-300,000 a month. The batch process to me always made sense especially when the system was busy as it means you're not duplicating resources. The only benefit I can see in a milter, besides keeping the postfix guys happy, is that it gives you the option to reject the message if you decide it's spam rather than having to quarantine it.



Running spamd as opposed to the perl module would make a lot of sense and would cut down the resources needed on the server. The benefits of being able to move clam to a daemon were fantastic.



Jason

[Jerry Benton]

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move MailScanner
to use the Spamd process years ago. Now the clamav module had a lot of
issues because when internal defs within the clam code changed the module
would puke until someone patched the module but it makes no sense to me why
anything MailScanner shares should be based on a perl module if there is a
daemon available to communicate with. Spamd protocol is pretty simple and
fairly easy to integrate within MailScanner. The difference in speed is
pretty much nil but the difference in MailScanner memory usage per child is
significant. When I originally worked with JF to integrate the clamd code
his biggest hesitation was he wasn't comfortable with network code... I
would bet that was the biggest reason for handling postfix the way it's
handled as well. Whoever is currently developing MS should really look at
moving toward spamd support in place of the perl module.

Rick,

Please send me the working code you have for this. I will add it to the development of the next version. The same is true for Postfix handling if you have anything. I have spoken to Wietse Venema regarding MailScanner integration of Postfix and he doesn’t like how it is currently done and posted a recommendation years ago on postfix.org that Postfix shouldn’t be used with MailScanner. In short, MailScanner should be using a milter for Postfix.

-
Jerry Benton
www.mailborder.com

[Rick Cooper]

Post by Jerry Benton

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move
MailScanner to use the Spamd process years ago. Now the clamav
module had a lot of issues because when internal defs within the
clam code changed the module would puke until someone patched the
module but it makes no sense to me why anything MailScanner shares
should be based on a perl module if there is a daemon available to
communicate with. Spamd protocol is pretty simple and fairly easy to
integrate within MailScanner. The difference in speed is pretty much
nil but the difference in MailScanner memory usage per child is
significant. When I originally worked with JF to integrate the clamd
code his biggest hesitation was he wasn't comfortable with network
code... I would bet that was the biggest reason for handling postfix
the way it's handled as well. Whoever is currently developing MS
should really look at moving toward spamd support in place of the
perl module.

Rick,
Please send me the working code you have for this. I will add it to
the development of the next version. The same is true for Postfix
handling if you have anything. I have spoken to Wietse Venema
regarding MailScanner integration of Postfix and he doesn't like how
it is currently done and posted a recommendation years ago on
postfix.org that Postfix shouldn't be used with MailScanner. In
short, MailScanner should be using a milter for Postfix.
-
Jerry Benton
www.mailborder.com

I will have to see what needs patch, I have not really maintained the
patches because of my wife's health issues so it's probably a few versions
back at least. I think the last patch I did was around the time that JF
moved away from the project. As far as postfix, I do not nor never will use
it. The author seems pretty full of himself without real justification. I
just remember the issues and it seemed they were all related to how postfix
handled it's mail queue and I believe the proper way discussed at that time
was it should be redelivered through some process which would have required
sockets again. You know, I think Glenn did *a lot* of the postfix code and
seems to know it very well. Dunno if he has time to take a crack or not.

Rick

[Glenn Steen]

Yeah well, the core parts of the postfix code is all JF, all I did was
(at the time when the p-records were introduced to the queue file
structure) hack up some not too inefficient code to make it cope with
the new stuff. Had to delve deep into the innarts of both postfix and
MailScanner, but ... Theat was a few years back;-).

I don't know of any development in postfix that would radically change
the frontline between MS and PF... They want us to sacrifice
efficiency to protect against possible corruption by using "published
interfaces" (LMTP/SMTP would make it wellnigh impossible to keep the
"batch scanning" functionality). We want to keep doing things as
efficiently as possible.

A fun fact is that during one of Jules rows with Wietse, Wietse
actually detailed all that needed be done (as a dettering example,
mind you) to "steal" the messages from the queue, break it apart,
reconstruct a new message (pretty much identical, but with a
completely new queue file/ID). Jules only comment was "Yes, that is
exactly what we do". After that, the lines of communication were a
bit... strained:-).

Anyway, unless there is something significantly different that can be
done vis-a-vis how postfix can interract with MailScanner, there
simply is nothing to be done. At least nothing that will improve
MailScanner. And mind you, I've been using Postfix/MailScanner
successfully for more than 10 years now... Deprecated indeed;-)

Cheers!
--
-- Glenn

Post by Rick Cooper

Post by Jerry Benton

Post by Rick Cooper
This applies to SpamAssassin as well. I sent Jules code to move
MailScanner to use the Spamd process years ago. Now the clamav
module had a lot of issues because when internal defs within the
clam code changed the module would puke until someone patched the
module but it makes no sense to me why anything MailScanner shares
should be based on a perl module if there is a daemon available to
communicate with. Spamd protocol is pretty simple and fairly easy to
integrate within MailScanner. The difference in speed is pretty much
nil but the difference in MailScanner memory usage per child is
significant. When I originally worked with JF to integrate the clamd
code his biggest hesitation was he wasn't comfortable with network
code... I would bet that was the biggest reason for handling postfix
the way it's handled as well. Whoever is currently developing MS
should really look at moving toward spamd support in place of the
perl module.

Rick,
Please send me the working code you have for this. I will add it to
the development of the next version. The same is true for Postfix
handling if you have anything. I have spoken to Wietse Venema
regarding MailScanner integration of Postfix and he doesn't like how
it is currently done and posted a recommendation years ago on
postfix.org that Postfix shouldn't be used with MailScanner. In
short, MailScanner should be using a milter for Postfix.
-
Jerry Benton
www.mailborder.com

I will have to see what needs patch, I have not really maintained the
patches because of my wife's health issues so it's probably a few versions
back at least. I think the last patch I did was around the time that JF
moved away from the project. As far as postfix, I do not nor never will use
it. The author seems pretty full of himself without real justification. I
just remember the issues and it seemed they were all related to how postfix
handled it's mail queue and I believe the proper way discussed at that time
was it should be redelivered through some process which would have required
sockets again. You know, I think Glenn did *a lot* of the postfix code and
seems to know it very well. Dunno if he has time to take a crack or not.
Rick
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se

[Jerry Benton]

Ok, updates were made based on feedback and further testing. I will do some more tests over the next 2 days in my lab on RHEL 5,6,7 on both 32 and 64 bit. Barring any other issues, I will move this to build 1 and release by Monday. I am working on the tarball release as well, but the MailScanner code won’t change once the RPM is finalized. Only the installer.

https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz



-
Jerry Benton
www.mailborder.com

Post by Jerry Benton
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at /usr/lib/MailScanner/MailScanner/Config.pm line 2864
Error in line 990, file "/etc/MailScanner/phishing.bad.sites.conf" for phishingblacklist does not exist (or can not be read) at /usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at /usr/lib/MailScanner/MailScanner/Config.pm line 2874
Error in configuration file line 169, directory /var/spool/mqueue for outqueuedir does not exist (or is not readable) at /usr/lib/MailScanner/MailScanner/Config.pm line 3238
Read 868 hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check
filenames and filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in "/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Randal, Phil]

By the way, tnef is available fro RGHEL/CentOS 5/6/7 from the repoforge yum repo.

Cheers,

Phil

-----Original Message-----
From: mailscanner-***@lists.mailscanner.info [mailto:mailscanner-***@lists.mailscanner.info] On Behalf Of Jerry Benton
Sent: 18 February 2015 13:35
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available

Ok, updates were made based on feedback and further testing. I will do some more tests over the next 2 days in my lab on RHEL 5,6,7 on both 32 and 64 bit. Barring any other issues, I will move this to build 1 and release by Monday. I am working on the tarball release as well, but the MailScanner code won’t change once the RPM is finalized. Only the installer.

https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz



-
Jerry Benton
www.mailborder.com

Post by Jerry Benton
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
***@lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE

"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."

[Jerry Benton]

It is listed for RHEL 5 and 6. Only 6 works. (5 isn’t actually available from EPEL for some reason.) There is nothing for 7. That is why I built an RPM for it from source. The new installer tries to install it from Yum. If it can’t, it will install it from the RPM I made if you elect to do so.

-
Jerry Benton
www.mailborder.com

Post by Randal, Phil
By the way, tnef is available fro RGHEL/CentOS 5/6/7 from the repoforge yum repo.
Cheers,
Phil
-----Original Message-----
Sent: 18 February 2015 13:35
To: MailScanner discussion
Subject: Re: v4.85.1.0 Beta for Linux RPM Available
Ok, updates were made based on feedback and further testing. I will do some more tests over the next 2 days in my lab on RHEL 5,6,7 on both 32 and 64 bit. Barring any other issues, I will move this to build 1 and release by Monday. I am working on the tarball release as well, but the MailScanner code won’t change once the RPM is finalized. Only the installer.
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
-
Jerry Benton
www.mailborder.com

Post by Jerry Benton
Thanks for the feedback.
- DFOPTION - fixed that.
- Mail::ClamAV is not a MailScanner dependency, but the script attempts to install it if you elect to install Clam AV. There is no RPM package for it.
- I will add the bzip2-devel to the base packages.
- I can look at what I can do with the default Y option. It is not as easy or straight forward as it seems.
- I will check check the phishing.bad.sites.conf issue, but it did install during the tests I did.
- You are missing /var/spool/mqueue because either you did not install an MTA or you did not configure MailScanner.conf to use your MTA. The script does not install an MTA for you or setup MailScanner.conf. If you installed sendmail, you wouldn’t get the errors because the defaults in MailScanner.conf are for sendmail.
- The unrar package is not a dependency.
- the mailscanner.cf is a soft link created in the /etc/mail/spamassassin directory to the spam.assassin.prefs.conf file in /etc/MailScanner. If you did not elect to install spamassassin the link won’t be created.
Thanks for testing it out.
-
Jerry Benton
www.mailborder.com

Post by Christophe GRENIER

Post by Jerry Benton
https://s3.amazonaws.com/mailscanner/MailScanner-4.85.1-0.rpm.tar.gz
Note: This is beta! If you install on on a production box, that’s on you.

Hi
I have tested the install script on CentOS 6.
- DFOPTION variable is undefined on non CentOS 7
./install.sh: line 409: [: ==: unary operator expected
File::ShareDir::Install is missing. Installing via CPAN ...
Mail::ClamAV is missing. Installing via CPAN ...
...
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status
make[1]: *** [blib/arch/auto/Mail/ClamAV/ClamAV.so] Error 1
make[1]: Leaving directory
`/root/.cpan/build/Mail-ClamAV-0.29-JoeFgy/_Inline/build/Mail/ClamAV'
- IMOO answers should default to recommanded values (Y instead of N).
- After rerunning the install script,
MailScanner --lint
Could not read file /etc/MailScanner/phishing.bad.sites.conf at
/usr/lib/MailScanner/MailScanner/Config.pm line 2864 Error in line
990, file "/etc/MailScanner/phishing.bad.sites.conf" for
phishingblacklist does not exist (or can not be read) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3066
- Some configurations is needed (I am using postfix), you may want to
Could not read directory /var/spool/mqueue at
/usr/lib/MailScanner/MailScanner/Config.pm line 2874 Error in
configuration file line 169, directory /var/spool/mqueue for
outqueuedir does not exist (or is not readable) at
/usr/lib/MailScanner/MailScanner/Config.pm line 3238 Read 868
hostnames from the phishing whitelist
- Unrar is not installed, it should be in /usr/bin/unrar.
This is required for RAR archives to be read to check filenames and
filetypes. Virus scanning is not affected.
Two possibilities: switch to internal unrar or install it...
- config: failed to parse line, skipping, in
"/etc/mail/spamassassin/mailscanner.cf": use_auto_whitelist 0
I haven't test this version of MailScanner for the moment, only the install script.
Thanks for your work
Regards,
Christophe
--
,-~~-.___. ._.
/ | ' \ | |--------. Christophe GRENIER
\_/-, ,----' | | |
==== !_!-v---v--.
/ \-'~; .--------. TestDisk & PhotoRec
/ __/~| ._-""|| | Data Recovery
=( _____|_|____||________| http://www.cgsecurity.org--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
Hoople Ltd, Registered in England and Wales No. 7556595
Registered office: Plough Lane, Hereford, HR4 0LE
"Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!

[Paul A Sand]

[tnef] is listed for RHEL 5 and 6. Only 6 works. (5 isn’t actually
available from EPEL for some reason.) There is nothing for 7. That is why
I built an RPM for it from source. The new installer tries to install it
from Yum. If it can’t, it will install it from the RPM I made if you elect
to do so.

I submitted a bug on this:

https://bugzilla.redhat.com/show_bug.cgi?id=1193160

The maintainer says he'll take a look over the weekend. (His attempted
build for el5 back in 2011 failed.)
--
-- Paul A Sand <***@unh.edu>
-- Information Technology / University of New Hampshire
-- http://pubpages.unh.edu/~pas
-- Rikki lost my number.

[Nerijus Baliunas]

Post by Paul A Sand
https://bugzilla.redhat.com/show_bug.cgi?id=1193160

Thanks a lot, soon there will be releases for both 5 and 7:

tnef-1.4.12-2.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/tnef-1.4.12-2.el7

tnef-1.4.12-2.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/tnef-1.4.12-2.el5

Regards,
Nerijus