I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
) In case you need to change it back to its old behaviour, you want to
look at lines 413 and 414 of SweepOther.pm.
Line 413 is the old code (commented out) and line 414 is the new code.
Simply move the comment symbol # to the other line to revert to the old
behaviour.

All it does is only look in the output of the file command (or of "file
-i") for all the filetype-desribing text up to, but not including, the
first "," instead of until the end of the line. This improves the
behaviour with some filetypes, particularly Word documents, where the
output of "file" includes loads of information extracted from the file
being studied. That extra information may contain all sorts of things
which are detected as keywords in your filetype.rules.conf file.

Hopefully that will make the upgrade a whole lot easier for you!

Jules.

On 03/08/2010 15:50, Peter Ong wrote:
> Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.
>
> It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.
>
> Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.
>
> And by the way, my servers have a load of over 100K per day too. (o:`,
>
> As to my luck, well, the lottery here is up to 42 million again. We'll see.
>
> hehehe
>
> p
>
>
> ----- Original Message -----
>
>
>> From: "Hostmaster"<>
>> To: "MailScanner discussion"<>
>> Sent: Tuesday, August 3, 2010 7:23:32 AM
>> Subject: RE: New beta release 4.81.2
>>
>> Peter,
>> At the risk of jinxing it, I do have to jump to MailScanner's defence
>> and say
>> that in three years of updating MailScanner on a system which handles
>> 25-30,000
>> emails a day, I am yet to encounter an issue during an upgrade.
>>
>> Perhaps I have just been lucky, or you have been especially unlucky?
>>
>> Kind Regards,
>> Richard
>>
>> -----Original Message-----
>> From: mailscanner-
>> [mailto:mailscanner-] On Behalf Of Peter
>> Ong
>> Posted At: 03 August 2010 15:07
>> Posted To: Hostmaster
>> Conversation: New beta release 4.81.2
>> Subject: Re: New beta release 4.81.2
>>
>>
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>>
>> When I was a kid, my mom would take me to Bank of America, and I would
>> marvel at
>> how complicated the computers and their networks must have been in
>> order to keep
>> track of every single transaction for every single customer. Then, I
>> got to work
>> for a bank for 6 years as the person responsible for the money
>> transfer system.
>> Now I fear putting money in any bank, especially that one.
>>
>> MailScanner took me a few weeks to tame what with all the "file"
>> command issues
>> we had. Now that I'm seeing the behind the scenes of the upgrade and
>> I'm still
>> licking my wounds, I dread this upgrade.
>>
>> p
>>
>> ----- Original Message -----
>>
>>
>>> From: "Julian Field"<>
>>> To: "MailScanner discussion"<>
>>> Sent: Tuesday, August 3, 2010 3:33:56 AM
>>> Subject: New beta release 4.81.2
>>>
>>> I have just released a new beta, with the intention of it becoming
>>>
>> a
>>
>>> stable release Real Soon Now(tm).
>>> Since 4.79, quite a few things have happened:
>>>
>>> * New Features and Improvements *
>>> 1 Upgraded AVG support to AVG version 8. Support no longer
>>>
>> guaranteed
>>
>>> for older versions.
>>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
>>> directory if the file or link exists.
>>> 3 Added support for McAfee version 6. Use the virus scanner name
>>> "mcafee6" to get this support. Many thanks to Phil Randal and
>>>
>> Michael
>>
>>> Miller for all their hard work on this.
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>> 5 Added facility for over-riding MailScanner.conf settings and
>>> rulesets with those held in an SQL database.
>>> New settings are:
>>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
>>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
>>> See the MailScanner.conf file for more details.
>>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
>>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
>>> dependency.
>>> 1 Slight improvement to check_mailscanner script to send some
>>>
>> output
>>
>>> to /dev/null for Greg Kuhnert.
>>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
>>> nothing else at all. This makes simple setups where you only want
>>> virus scanning a whole lot easier to set up.
>>>
>>> * Fixes *
>>> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
>>> odd
>>> opinions about tainting data.
>>> 1 Minor tweak to avoid warning about insecure dependency in
>>> WorkArea.pm.
>>> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
>>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
>>>
>> message
>>
>>> about "MSlint" directory permissions.
>>> 3 Fixed error in MIME boundary checking that stopped a few very
>>>
>> rare
>>
>>> cases being checked.
>>> 5 Fixed issue where zip files in messages were unpacked with
>>>
>> incorrect
>>
>>> permissions.
>>> 5-2 Fixed bug introduced in 5-1.
>>> 7 Fixed ruleset-from-function bug introduced in 5-1.
>>> 9 Fixed bug where %variables% would not work in ruleset files.
>>> 10 Fixed bug on Linux systems where Postfix systems would change
>>>
>> the
>>
>>> ownership of the queue and work directories every time MailScanner
>>>
>> was
>>
>>> started.
>>> 1 Deny File MIME Types was ignored if new filetype rules used MIME
>>> checks.
>>> 2 Slightly improvement to phishing trap to handle links with " in
>>> them.
>>> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>>>
>>> All available from www.mailscanner.info as usual.
>>>
>>> I would be very grateful if you could test this release and prove
>>>
>> it's
>>
>>> okay. In a few days I will release a stable version, if I get
>>>
>> enough
>>
>>> response that it is indeed all working okay.
>>>
>>> Thanks folks!
>>>
>>> Jules
>>>
>>> --
>>> Julian Field MEng CITP CEng
>>> www.MailScanner.info
>>> Buy the MailScanner book at www.MailScanner.info/store
>>>
>>> Need help customising MailScanner?
>>> Contact me!
>>> Need help fixing or optimising your systems?
>>> Contact me!
>>> Need help getting you started solving new requirements from your
>>>
>> boss?
>>
>>> Contact me!
>>>
>>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>>
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> --
>>> 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!
>>
>>
>> All E-Mail communications are monitored in addition to being content
>> checked for malicious codes or viruses. The success of scanning
>> products is not guaranteed, therefore the recipient(s) should carry
>> out any checks that they believe to be appropriate in this respect.
>>
>> This message (including any attachments and/or related materials) is
>> confidential to and is the property of Computer Service Centre, unless
>> otherwise noted. If you are not the intended recipient, you should
>> delete this message and are hereby notified that any disclosure,
>> copying, or distribution of this message, or the taking of any action
>> based on it, is strictly prohibited.
>>
>> Any views or opinions presented are solely those of the author and do
>> not necessarily represent those of Computer Service Centre.
>> --
>> 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!
>>

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
) In case you need to change it back to its old behaviour, you want to
look at lines 413 and 414 of SweepOther.pm.
Line 413 is the old code (commented out) and line 414 is the new code.
Simply move the comment symbol # to the other line to revert to the old
behaviour.

All it does is only look in the output of the file command (or of "file
-i") for all the filetype-desribing text up to, but not including, the
first "," instead of until the end of the line. This improves the
behaviour with some filetypes, particularly Word documents, where the
output of "file" includes loads of information extracted from the file
being studied. That extra information may contain all sorts of things
which are detected as keywords in your filetype.rules.conf file.

Hopefully that will make the upgrade a whole lot easier for you!

Jules.

On 03/08/2010 15:50, Peter Ong wrote:
> Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.
>
> It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.
>
> Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.
>
> And by the way, my servers have a load of over 100K per day too. (o:`,
>
> As to my luck, well, the lottery here is up to 42 million again. We'll see.
>
> hehehe
>
> p
>
>
> ----- Original Message -----
>
>
>> From: "Hostmaster"<>
>> To: "MailScanner discussion"<>
>> Sent: Tuesday, August 3, 2010 7:23:32 AM
>> Subject: RE: New beta release 4.81.2
>>
>> Peter,
>> At the risk of jinxing it, I do have to jump to MailScanner's defence
>> and say
>> that in three years of updating MailScanner on a system which handles
>> 25-30,000
>> emails a day, I am yet to encounter an issue during an upgrade.
>>
>> Perhaps I have just been lucky, or you have been especially unlucky?
>>
>> Kind Regards,
>> Richard
>>
>> -----Original Message-----
>> From: mailscanner-
>> [mailto:mailscanner-] On Behalf Of Peter
>> Ong
>> Posted At: 03 August 2010 15:07
>> Posted To: Hostmaster
>> Conversation: New beta release 4.81.2
>> Subject: Re: New beta release 4.81.2
>>
>>
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>>
>> When I was a kid, my mom would take me to Bank of America, and I would
>> marvel at
>> how complicated the computers and their networks must have been in
>> order to keep
>> track of every single transaction for every single customer. Then, I
>> got to work
>> for a bank for 6 years as the person responsible for the money
>> transfer system.
>> Now I fear putting money in any bank, especially that one.
>>
>> MailScanner took me a few weeks to tame what with all the "file"
>> command issues
>> we had. Now that I'm seeing the behind the scenes of the upgrade and
>> I'm still
>> licking my wounds, I dread this upgrade.
>>
>> p
>>
>> ----- Original Message -----
>>
>>
>>> From: "Julian Field"<>
>>> To: "MailScanner discussion"<>
>>> Sent: Tuesday, August 3, 2010 3:33:56 AM
>>> Subject: New beta release 4.81.2
>>>
>>> I have just released a new beta, with the intention of it becoming
>>>
>> a
>>
>>> stable release Real Soon Now(tm).
>>> Since 4.79, quite a few things have happened:
>>>
>>> * New Features and Improvements *
>>> 1 Upgraded AVG support to AVG version 8. Support no longer
>>>
>> guaranteed
>>
>>> for older versions.
>>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
>>> directory if the file or link exists.
>>> 3 Added support for McAfee version 6. Use the virus scanner name
>>> "mcafee6" to get this support. Many thanks to Phil Randal and
>>>
>> Michael
>>
>>> Miller for all their hard work on this.
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>> 5 Added facility for over-riding MailScanner.conf settings and
>>> rulesets with those held in an SQL database.
>>> New settings are:
>>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
>>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
>>> See the MailScanner.conf file for more details.
>>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
>>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
>>> dependency.
>>> 1 Slight improvement to check_mailscanner script to send some
>>>
>> output
>>
>>> to /dev/null for Greg Kuhnert.
>>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
>>> nothing else at all. This makes simple setups where you only want
>>> virus scanning a whole lot easier to set up.
>>>
>>> * Fixes *
>>> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
>>> odd
>>> opinions about tainting data.
>>> 1 Minor tweak to avoid warning about insecure dependency in
>>> WorkArea.pm.
>>> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
>>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
>>>
>> message
>>
>>> about "MSlint" directory permissions.
>>> 3 Fixed error in MIME boundary checking that stopped a few very
>>>
>> rare
>>
>>> cases being checked.
>>> 5 Fixed issue where zip files in messages were unpacked with
>>>
>> incorrect
>>
>>> permissions.
>>> 5-2 Fixed bug introduced in 5-1.
>>> 7 Fixed ruleset-from-function bug introduced in 5-1.
>>> 9 Fixed bug where %variables% would not work in ruleset files.
>>> 10 Fixed bug on Linux systems where Postfix systems would change
>>>
>> the
>>
>>> ownership of the queue and work directories every time MailScanner
>>>
>> was
>>
>>> started.
>>> 1 Deny File MIME Types was ignored if new filetype rules used MIME
>>> checks.
>>> 2 Slightly improvement to phishing trap to handle links with " in
>>> them.
>>> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>>>
>>> All available from www.mailscanner.info as usual.
>>>
>>> I would be very grateful if you could test this release and prove
>>>
>> it's
>>
>>> okay. In a few days I will release a stable version, if I get
>>>
>> enough
>>
>>> response that it is indeed all working okay.
>>>
>>> Thanks folks!
>>>
>>> Jules
>>>
>>> --
>>> Julian Field MEng CITP CEng
>>> www.MailScanner.info
>>> Buy the MailScanner book at www.MailScanner.info/store
>>>
>>> Need help customising MailScanner?
>>> Contact me!
>>> Need help fixing or optimising your systems?
>>> Contact me!
>>> Need help getting you started solving new requirements from your
>>>
>> boss?
>>
>>> Contact me!
>>>
>>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>>
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> --
>>> 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!
>>
>>
>> All E-Mail communications are monitored in addition to being content
>> checked for malicious codes or viruses. The success of scanning
>> products is not guaranteed, therefore the recipient(s) should carry
>> out any checks that they believe to be appropriate in this respect.
>>
>> This message (including any attachments and/or related materials) is
>> confidential to and is the property of Computer Service Centre, unless
>> otherwise noted. If you are not the intended recipient, you should
>> delete this message and are hereby notified that any disclosure,
>> copying, or distribution of this message, or the taking of any action
>> based on it, is strictly prohibited.
>>
>> Any views or opinions presented are solely those of the author and do
>> not necessarily represent those of Computer Service Centre.
>> --
>> 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!
>>

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
) > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the
> fiery tempers of my users and especially the impatience of my higher
> ups.

Peter, given that, I'd highly recommend setting up a testing server
where you can send a "shadow copy" of all your production e-mail in
order to run it through the new version and see how things behave. This
is what I do here and allows me to run a new version with production
data but without having to touch the production server until I'm ready
to deploy. This type of set up may alleviate some of your concerns
about upgrading to newer versions. But I do know where you are coming
from - if it ain't broke, don't fix it, as they say.

cheers,


--tom


--
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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
) In case you need to change it back to its old behaviour, you want to
look at lines 413 and 414 of SweepOther.pm.
Line 413 is the old code (commented out) and line 414 is the new code.
Simply move the comment symbol # to the other line to revert to the old
behaviour.

All it does is only look in the output of the file command (or of "file
-i") for all the filetype-desribing text up to, but not including, the
first "," instead of until the end of the line. This improves the
behaviour with some filetypes, particularly Word documents, where the
output of "file" includes loads of information extracted from the file
being studied. That extra information may contain all sorts of things
which are detected as keywords in your filetype.rules.conf file.

Hopefully that will make the upgrade a whole lot easier for you!

Jules.

On 03/08/2010 15:50, Peter Ong wrote:
> Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.
>
> It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.
>
> Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.
>
> And by the way, my servers have a load of over 100K per day too. (o:`,
>
> As to my luck, well, the lottery here is up to 42 million again. We'll see.
>
> hehehe
>
> p
>
>
> ----- Original Message -----
>
>
>> From: "Hostmaster"<>
>> To: "MailScanner discussion"<>
>> Sent: Tuesday, August 3, 2010 7:23:32 AM
>> Subject: RE: New beta release 4.81.2
>>
>> Peter,
>> At the risk of jinxing it, I do have to jump to MailScanner's defence
>> and say
>> that in three years of updating MailScanner on a system which handles
>> 25-30,000
>> emails a day, I am yet to encounter an issue during an upgrade.
>>
>> Perhaps I have just been lucky, or you have been especially unlucky?
>>
>> Kind Regards,
>> Richard
>>
>> -----Original Message-----
>> From: mailscanner-
>> [mailto:mailscanner-] On Behalf Of Peter
>> Ong
>> Posted At: 03 August 2010 15:07
>> Posted To: Hostmaster
>> Conversation: New beta release 4.81.2
>> Subject: Re: New beta release 4.81.2
>>
>>
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>>
>> When I was a kid, my mom would take me to Bank of America, and I would
>> marvel at
>> how complicated the computers and their networks must have been in
>> order to keep
>> track of every single transaction for every single customer. Then, I
>> got to work
>> for a bank for 6 years as the person responsible for the money
>> transfer system.
>> Now I fear putting money in any bank, especially that one.
>>
>> MailScanner took me a few weeks to tame what with all the "file"
>> command issues
>> we had. Now that I'm seeing the behind the scenes of the upgrade and
>> I'm still
>> licking my wounds, I dread this upgrade.
>>
>> p
>>
>> ----- Original Message -----
>>
>>
>>> From: "Julian Field"<>
>>> To: "MailScanner discussion"<>
>>> Sent: Tuesday, August 3, 2010 3:33:56 AM
>>> Subject: New beta release 4.81.2
>>>
>>> I have just released a new beta, with the intention of it becoming
>>>
>> a
>>
>>> stable release Real Soon Now(tm).
>>> Since 4.79, quite a few things have happened:
>>>
>>> * New Features and Improvements *
>>> 1 Upgraded AVG support to AVG version 8. Support no longer
>>>
>> guaranteed
>>
>>> for older versions.
>>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
>>> directory if the file or link exists.
>>> 3 Added support for McAfee version 6. Use the virus scanner name
>>> "mcafee6" to get this support. Many thanks to Phil Randal and
>>>
>> Michael
>>
>>> Miller for all their hard work on this.
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>> 5 Added facility for over-riding MailScanner.conf settings and
>>> rulesets with those held in an SQL database.
>>> New settings are:
>>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
>>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
>>> See the MailScanner.conf file for more details.
>>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
>>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
>>> dependency.
>>> 1 Slight improvement to check_mailscanner script to send some
>>>
>> output
>>
>>> to /dev/null for Greg Kuhnert.
>>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
>>> nothing else at all. This makes simple setups where you only want
>>> virus scanning a whole lot easier to set up.
>>>
>>> * Fixes *
>>> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
>>> odd
>>> opinions about tainting data.
>>> 1 Minor tweak to avoid warning about insecure dependency in
>>> WorkArea.pm.
>>> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
>>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
>>>
>> message
>>
>>> about "MSlint" directory permissions.
>>> 3 Fixed error in MIME boundary checking that stopped a few very
>>>
>> rare
>>
>>> cases being checked.
>>> 5 Fixed issue where zip files in messages were unpacked with
>>>
>> incorrect
>>
>>> permissions.
>>> 5-2 Fixed bug introduced in 5-1.
>>> 7 Fixed ruleset-from-function bug introduced in 5-1.
>>> 9 Fixed bug where %variables% would not work in ruleset files.
>>> 10 Fixed bug on Linux systems where Postfix systems would change
>>>
>> the
>>
>>> ownership of the queue and work directories every time MailScanner
>>>
>> was
>>
>>> started.
>>> 1 Deny File MIME Types was ignored if new filetype rules used MIME
>>> checks.
>>> 2 Slightly improvement to phishing trap to handle links with " in
>>> them.
>>> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>>>
>>> All available from www.mailscanner.info as usual.
>>>
>>> I would be very grateful if you could test this release and prove
>>>
>> it's
>>
>>> okay. In a few days I will release a stable version, if I get
>>>
>> enough
>>
>>> response that it is indeed all working okay.
>>>
>>> Thanks folks!
>>>
>>> Jules
>>>
>>> --
>>> Julian Field MEng CITP CEng
>>> www.MailScanner.info
>>> Buy the MailScanner book at www.MailScanner.info/store
>>>
>>> Need help customising MailScanner?
>>> Contact me!
>>> Need help fixing or optimising your systems?
>>> Contact me!
>>> Need help getting you started solving new requirements from your
>>>
>> boss?
>>
>>> Contact me!
>>>
>>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>>
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> --
>>> 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!
>>
>>
>> All E-Mail communications are monitored in addition to being content
>> checked for malicious codes or viruses. The success of scanning
>> products is not guaranteed, therefore the recipient(s) should carry
>> out any checks that they believe to be appropriate in this respect.
>>
>> This message (including any attachments and/or related materials) is
>> confidential to and is the property of Computer Service Centre, unless
>> otherwise noted. If you are not the intended recipient, you should
>> delete this message and are hereby notified that any disclosure,
>> copying, or distribution of this message, or the taking of any action
>> based on it, is strictly prohibited.
>>
>> Any views or opinions presented are solely those of the author and do
>> not necessarily represent those of Computer Service Centre.
>> --
>> 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!
>>

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
) > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the
> fiery tempers of my users and especially the impatience of my higher
> ups.

Peter, given that, I'd highly recommend setting up a testing server
where you can send a "shadow copy" of all your production e-mail in
order to run it through the new version and see how things behave. This
is what I do here and allows me to run a new version with production
data but without having to touch the production server until I'm ready
to deploy. This type of set up may alleviate some of your concerns
about upgrading to newer versions. But I do know where you are coming
from - if it ain't broke, don't fix it, as they say.

cheers,


--tom


--
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!
) Thanks, Thomas. Actually I already do that. In fact, I have a mini-replica of the office at home. I run my own email server at home; trying to avoid getting caught in the next round of warrantless tapping by the next time the Patriot Act is invoked. I know I'll still be all over google's servers, but I'll at least minimize it. Hahaha.

In any case, yes, I'll test the upgrade at my crib first, and then see how well that goes. When I get a good feeling about it, I'll deploy in the office. Thanks.

p

----- Original Message -----

> From: "Thomas Lohman" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 8:53:42 AM
> Subject: Re: New beta release 4.81.2
>
> > Given the trauma I incurred during that time and seeing the "file"
> > command related fixes in this release, I don't know how they will
> > affect the configurations that were painstakingly borne from the
> > fiery tempers of my users and especially the impatience of my
> higher
> > ups.
>
> Peter, given that, I'd highly recommend setting up a testing server
> where you can send a "shadow copy" of all your production e-mail in
> order to run it through the new version and see how things behave.
> This
> is what I do here and allows me to run a new version with production
> data but without having to touch the production server until I'm ready
>
> to deploy. This type of set up may alleviate some of your concerns
> about upgrading to newer versions. But I do know where you are coming
>
> from - if it ain't broke, don't fix it, as they say.
>
> cheers,
>
>
> --tom
>
>
> --
> 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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
) In case you need to change it back to its old behaviour, you want to
look at lines 413 and 414 of SweepOther.pm.
Line 413 is the old code (commented out) and line 414 is the new code.
Simply move the comment symbol # to the other line to revert to the old
behaviour.

All it does is only look in the output of the file command (or of "file
-i") for all the filetype-desribing text up to, but not including, the
first "," instead of until the end of the line. This improves the
behaviour with some filetypes, particularly Word documents, where the
output of "file" includes loads of information extracted from the file
being studied. That extra information may contain all sorts of things
which are detected as keywords in your filetype.rules.conf file.

Hopefully that will make the upgrade a whole lot easier for you!

Jules.

On 03/08/2010 15:50, Peter Ong wrote:
> Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.
>
> It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.
>
> Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.
>
> And by the way, my servers have a load of over 100K per day too. (o:`,
>
> As to my luck, well, the lottery here is up to 42 million again. We'll see.
>
> hehehe
>
> p
>
>
> ----- Original Message -----
>
>
>> From: "Hostmaster"<>
>> To: "MailScanner discussion"<>
>> Sent: Tuesday, August 3, 2010 7:23:32 AM
>> Subject: RE: New beta release 4.81.2
>>
>> Peter,
>> At the risk of jinxing it, I do have to jump to MailScanner's defence
>> and say
>> that in three years of updating MailScanner on a system which handles
>> 25-30,000
>> emails a day, I am yet to encounter an issue during an upgrade.
>>
>> Perhaps I have just been lucky, or you have been especially unlucky?
>>
>> Kind Regards,
>> Richard
>>
>> -----Original Message-----
>> From: mailscanner-
>> [mailto:mailscanner-] On Behalf Of Peter
>> Ong
>> Posted At: 03 August 2010 15:07
>> Posted To: Hostmaster
>> Conversation: New beta release 4.81.2
>> Subject: Re: New beta release 4.81.2
>>
>>
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>>
>> When I was a kid, my mom would take me to Bank of America, and I would
>> marvel at
>> how complicated the computers and their networks must have been in
>> order to keep
>> track of every single transaction for every single customer. Then, I
>> got to work
>> for a bank for 6 years as the person responsible for the money
>> transfer system.
>> Now I fear putting money in any bank, especially that one.
>>
>> MailScanner took me a few weeks to tame what with all the "file"
>> command issues
>> we had. Now that I'm seeing the behind the scenes of the upgrade and
>> I'm still
>> licking my wounds, I dread this upgrade.
>>
>> p
>>
>> ----- Original Message -----
>>
>>
>>> From: "Julian Field"<>
>>> To: "MailScanner discussion"<>
>>> Sent: Tuesday, August 3, 2010 3:33:56 AM
>>> Subject: New beta release 4.81.2
>>>
>>> I have just released a new beta, with the intention of it becoming
>>>
>> a
>>
>>> stable release Real Soon Now(tm).
>>> Since 4.79, quite a few things have happened:
>>>
>>> * New Features and Improvements *
>>> 1 Upgraded AVG support to AVG version 8. Support no longer
>>>
>> guaranteed
>>
>>> for older versions.
>>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
>>> directory if the file or link exists.
>>> 3 Added support for McAfee version 6. Use the virus scanner name
>>> "mcafee6" to get this support. Many thanks to Phil Randal and
>>>
>> Michael
>>
>>> Miller for all their hard work on this.
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>> 5 Added facility for over-riding MailScanner.conf settings and
>>> rulesets with those held in an SQL database.
>>> New settings are:
>>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
>>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
>>> See the MailScanner.conf file for more details.
>>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
>>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
>>> dependency.
>>> 1 Slight improvement to check_mailscanner script to send some
>>>
>> output
>>
>>> to /dev/null for Greg Kuhnert.
>>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
>>> nothing else at all. This makes simple setups where you only want
>>> virus scanning a whole lot easier to set up.
>>>
>>> * Fixes *
>>> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
>>> odd
>>> opinions about tainting data.
>>> 1 Minor tweak to avoid warning about insecure dependency in
>>> WorkArea.pm.
>>> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
>>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
>>>
>> message
>>
>>> about "MSlint" directory permissions.
>>> 3 Fixed error in MIME boundary checking that stopped a few very
>>>
>> rare
>>
>>> cases being checked.
>>> 5 Fixed issue where zip files in messages were unpacked with
>>>
>> incorrect
>>
>>> permissions.
>>> 5-2 Fixed bug introduced in 5-1.
>>> 7 Fixed ruleset-from-function bug introduced in 5-1.
>>> 9 Fixed bug where %variables% would not work in ruleset files.
>>> 10 Fixed bug on Linux systems where Postfix systems would change
>>>
>> the
>>
>>> ownership of the queue and work directories every time MailScanner
>>>
>> was
>>
>>> started.
>>> 1 Deny File MIME Types was ignored if new filetype rules used MIME
>>> checks.
>>> 2 Slightly improvement to phishing trap to handle links with " in
>>> them.
>>> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>>>
>>> All available from www.mailscanner.info as usual.
>>>
>>> I would be very grateful if you could test this release and prove
>>>
>> it's
>>
>>> okay. In a few days I will release a stable version, if I get
>>>
>> enough
>>
>>> response that it is indeed all working okay.
>>>
>>> Thanks folks!
>>>
>>> Jules
>>>
>>> --
>>> Julian Field MEng CITP CEng
>>> www.MailScanner.info
>>> Buy the MailScanner book at www.MailScanner.info/store
>>>
>>> Need help customising MailScanner?
>>> Contact me!
>>> Need help fixing or optimising your systems?
>>> Contact me!
>>> Need help getting you started solving new requirements from your
>>>
>> boss?
>>
>>> Contact me!
>>>
>>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>>
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> --
>>> 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!
>>
>>
>> All E-Mail communications are monitored in addition to being content
>> checked for malicious codes or viruses. The success of scanning
>> products is not guaranteed, therefore the recipient(s) should carry
>> out any checks that they believe to be appropriate in this respect.
>>
>> This message (including any attachments and/or related materials) is
>> confidential to and is the property of Computer Service Centre, unless
>> otherwise noted. If you are not the intended recipient, you should
>> delete this message and are hereby notified that any disclosure,
>> copying, or distribution of this message, or the taking of any action
>> based on it, is strictly prohibited.
>>
>> Any views or opinions presented are solely those of the author and do
>> not necessarily represent those of Computer Service Centre.
>> --
>> 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!
>>

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
) > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the
> fiery tempers of my users and especially the impatience of my higher
> ups.

Peter, given that, I'd highly recommend setting up a testing server
where you can send a "shadow copy" of all your production e-mail in
order to run it through the new version and see how things behave. This
is what I do here and allows me to run a new version with production
data but without having to touch the production server until I'm ready
to deploy. This type of set up may alleviate some of your concerns
about upgrading to newer versions. But I do know where you are coming
from - if it ain't broke, don't fix it, as they say.

cheers,


--tom


--
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!
) Thanks, Thomas. Actually I already do that. In fact, I have a mini-replica of the office at home. I run my own email server at home; trying to avoid getting caught in the next round of warrantless tapping by the next time the Patriot Act is invoked. I know I'll still be all over google's servers, but I'll at least minimize it. Hahaha.

In any case, yes, I'll test the upgrade at my crib first, and then see how well that goes. When I get a good feeling about it, I'll deploy in the office. Thanks.

p

----- Original Message -----

> From: "Thomas Lohman" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 8:53:42 AM
> Subject: Re: New beta release 4.81.2
>
> > Given the trauma I incurred during that time and seeing the "file"
> > command related fixes in this release, I don't know how they will
> > affect the configurations that were painstakingly borne from the
> > fiery tempers of my users and especially the impatience of my
> higher
> > ups.
>
> Peter, given that, I'd highly recommend setting up a testing server
> where you can send a "shadow copy" of all your production e-mail in
> order to run it through the new version and see how things behave.
> This
> is what I do here and allows me to run a new version with production
> data but without having to touch the production server until I'm ready
>
> to deploy. This type of set up may alleviate some of your concerns
> about upgrading to newer versions. But I do know where you are coming
>
> from - if it ain't broke, don't fix it, as they say.
>
> cheers,
>
>
> --tom
>
>
> --
> 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!
) Thanks Julian. I'm making a note of it.

p


----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 8:24:55 AM
> Subject: Re: New beta release 4.81.2
>
> In case you need to change it back to its old behaviour, you want to
> look at lines 413 and 414 of SweepOther.pm.
> Line 413 is the old code (commented out) and line 414 is the new
> code.
> Simply move the comment symbol # to the other line to revert to the
> old
> behaviour.
>
> All it does is only look in the output of the file command (or of
> "file
> -i") for all the filetype-desribing text up to, but not including, the
>
> first "," instead of until the end of the line. This improves the
> behaviour with some filetypes, particularly Word documents, where the
>
> output of "file" includes loads of information extracted from the file
>
> being studied. That extra information may contain all sorts of things
>
> which are detected as keywords in your filetype.rules.conf file.
>
> Hopefully that will make the upgrade a whole lot easier for you!
>
> Jules.
>
> On 03/08/2010 15:50, Peter Ong wrote:
> > Oh no, I was just drawing similarities, but not intended as an
> indictment to MailScanner at all. In fact, I suggested once that its
> name should be changed to Awesome MailScanner.
> >
> > It's just that the file command was a very hairy situation for me
> until I got it working the way I wanted it; and I was hardly getting
> any love from everyone about it. Of course, whether what I did was the
> right thing remains unknown, but it is now doing what I want it to
> do.
> >
> > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the fiery
> tempers of my users and especially the impatience of my higher ups.
> >
> > And by the way, my servers have a load of over 100K per day too.
> (o:`,
> >
> > As to my luck, well, the lottery here is up to 42 million again.
> We'll see.
> >
> > hehehe
> >
> > p
> >
> >
> > ----- Original Message -----
> >
> >
> >> From: "Hostmaster"<>
> >> To: "MailScanner discussion"<>
> >> Sent: Tuesday, August 3, 2010 7:23:32 AM
> >> Subject: RE: New beta release 4.81.2
> >>
> >> Peter,
> >> At the risk of jinxing it, I do have to jump to MailScanner's
> defence
> >> and say
> >> that in three years of updating MailScanner on a system which
> handles
> >> 25-30,000
> >> emails a day, I am yet to encounter an issue during an upgrade.
> >>
> >> Perhaps I have just been lucky, or you have been especially
> unlucky?
> >>
> >> Kind Regards,
> >> Richard
> >>
> >> -----Original Message-----
> >> From: mailscanner-
> >> [mailto:mailscanner-] On Behalf Of
> Peter
> >> Ong
> >> Posted At: 03 August 2010 15:07
> >> Posted To: Hostmaster
> >> Conversation: New beta release 4.81.2
> >> Subject: Re: New beta release 4.81.2
> >>
> >>
> >>> 4 Improved "file" command output processing so it stops at 1st
> ","
> >>>
> >> to
> >>
> >>> reduce false alarms greatly.
> >>>
> >> When I was a kid, my mom would take me to Bank of America, and I
> would
> >> marvel at
> >> how complicated the computers and their networks must have been in
> >> order to keep
> >> track of every single transaction for every single customer. Then,
> I
> >> got to work
> >> for a bank for 6 years as the person responsible for the money
> >> transfer system.
> >> Now I fear putting money in any bank, especially that one.
> >>
> >> MailScanner took me a few weeks to tame what with all the "file"
> >> command issues
> >> we had. Now that I'm seeing the behind the scenes of the upgrade
> and
> >> I'm still
> >> licking my wounds, I dread this upgrade.
> >>
> >> p
> >>
> >> ----- Original Message -----
> >>
> >>
> >>> From: "Julian Field"<>
> >>> To: "MailScanner discussion"<>
> >>> Sent: Tuesday, August 3, 2010 3:33:56 AM
> >>> Subject: New beta release 4.81.2
> >>>
> >>> I have just released a new beta, with the intention of it
> becoming
> >>>
> >> a
> >>
> >>> stable release Real Soon Now(tm).
> >>> Since 4.79, quite a few things have happened:
> >>>
> >>> * New Features and Improvements *
> >>> 1 Upgraded AVG support to AVG version 8. Support no longer
> >>>
> >> guaranteed
> >>
> >>> for older versions.
> >>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> >>> directory if the file or link exists.
> >>> 3 Added support for McAfee version 6. Use the virus scanner name
> >>> "mcafee6" to get this support. Many thanks to Phil Randal and
> >>>
> >> Michael
> >>
> >>> Miller for all their hard work on this.
> >>> 4 Improved "file" command output processing so it stops at 1st
> ","
> >>>
> >> to
> >>
> >>> reduce false alarms greatly.
> >>> 5 Added facility for over-riding MailScanner.conf settings and
> >>> rulesets with those held in an SQL database.
> >>> New settings are:
> >>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL
> Quick
> >>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL
> Debug.
> >>> See the MailScanner.conf file for more details.
> >>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> >>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> >>> dependency.
> >>> 1 Slight improvement to check_mailscanner script to send some
> >>>
> >> output
> >>
> >>> to /dev/null for Greg Kuhnert.
> >>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> >>> nothing else at all. This makes simple setups where you only want
> >>> virus scanning a whole lot easier to set up.
> >>>
> >>> * Fixes *
> >>> 1 A minor rewrite of a bit of the TNEF code to handle some
> systems'
> >>> odd
> >>> opinions about tainting data.
> >>> 1 Minor tweak to avoid warning about insecure dependency in
> >>> WorkArea.pm.
> >>> 2 Fixed documentation for "Allow Multiple HTML Signatures"
> setting.
> >>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
> >>>
> >> message
> >>
> >>> about "MSlint" directory permissions.
> >>> 3 Fixed error in MIME boundary checking that stopped a few very
> >>>
> >> rare
> >>
> >>> cases being checked.
> >>> 5 Fixed issue where zip files in messages were unpacked with
> >>>
> >> incorrect
> >>
> >>> permissions.
> >>> 5-2 Fixed bug introduced in 5-1.
> >>> 7 Fixed ruleset-from-function bug introduced in 5-1.
> >>> 9 Fixed bug where %variables% would not work in ruleset files.
> >>> 10 Fixed bug on Linux systems where Postfix systems would change
> >>>
> >> the
> >>
> >>> ownership of the queue and work directories every time
> MailScanner
> >>>
> >> was
> >>
> >>> started.
> >>> 1 Deny File MIME Types was ignored if new filetype rules used
> MIME
> >>> checks.
> >>> 2 Slightly improvement to phishing trap to handle links with " in
> >>> them.
> >>> 2 Worked around nasty behaviour of Perl's "each()". Thanks
> Timofey!
> >>>
> >>> All available from www.mailscanner.info as usual.
> >>>
> >>> I would be very grateful if you could test this release and prove
> >>>
> >> it's
> >>
> >>> okay. In a few days I will release a stable version, if I get
> >>>
> >> enough
> >>
> >>> response that it is indeed all working okay.
> >>>
> >>> Thanks folks!
> >>>
> >>> Jules
> >>>
> >>> --
> >>> Julian Field MEng CITP CEng
> >>> www.MailScanner.info
> >>> Buy the MailScanner book at www.MailScanner.info/store
> >>>
> >>> Need help customising MailScanner?
> >>> Contact me!
> >>> Need help fixing or optimising your systems?
> >>> Contact me!
> >>> Need help getting you started solving new requirements from your
> >>>
> >> boss?
> >>
> >>> Contact me!
> >>>
> >>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> >>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >>>
> >>>
> >>> --
> >>> This message has been scanned for viruses and dangerous content
> by
> >>> MailScanner, and is believed to be clean.
> >>>
> >>> --
> >>> 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!
> >>
> >>
> >> All E-Mail communications are monitored in addition to being
> content
> >> checked for malicious codes or viruses. The success of scanning
> >> products is not guaranteed, therefore the recipient(s) should
> carry
> >> out any checks that they believe to be appropriate in this
> respect.
> >>
> >> This message (including any attachments and/or related materials)
> is
> >> confidential to and is the property of Computer Service Centre,
> unless
> >> otherwise noted. If you are not the intended recipient, you should
> >> delete this message and are hereby notified that any disclosure,
> >> copying, or distribution of this message, or the taking of any
> action
> >> based on it, is strictly prohibited.
> >>
> >> Any views or opinions presented are solely those of the author and
> do
> >> not necessarily represent those of Computer Service Centre.
> >> --
> >> 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!
> >>
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
)

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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 --lint
Missing right curly or square bracket at
/usr/lib/MailScanner/MailScanner/MessageBatch.pm line 1392, at end of
line
syntax error at /usr/lib/MailScanner/MailScanner/MessageBatch.pm line
1392, at EOF
Compilation failed in require at /usr/sbin/MailScanner line 103.
BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 103.

Cheers,

Phil
--
Phil Randal | Networks Engineer
NHS Herefordshire & Herefordshire Council | Deputy Chief Executive's
Office | I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT

email:

Any opinion expressed in this e-mail or any attached files are those of
the individual and not necessarily those of Herefordshire Council.

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.
-----Original Message-----
[mailto:mailscanner-] On Behalf Of Julian
Field
Sent: 03 August 2010 11:34
Subject: New beta release 4.81.2

I have just released a new beta, with the intention of it becoming a
stable release Real Soon Now(tm).
Since 4.79, quite a few things have happened:

* New Features and Improvements *
1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
for older versions.
2 Installers no longer over-write mailscanner.cf in SpamAssassin
directory if the file or link exists.
3 Added support for McAfee version 6. Use the virus scanner name
"mcafee6" to get this support. Many thanks to Phil Randal and Michael
Miller for all their hard work on this.
4 Improved "file" command output processing so it stops at 1st "," to
reduce false alarms greatly.
5 Added facility for over-riding MailScanner.conf settings and rulesets
with those held in an SQL database.
New settings are:
DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick Peek,
SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
See the MailScanner.conf file for more details.
5 Added dependency "Sys::SigAction" Perl modules to installers.
6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib dependency.
1 Slight improvement to check_mailscanner script to send some output to
/dev/null for Greg Kuhnert.
2 "Scan Messages = virus" will *only* scan mail for viruses and nothing
else at all. This makes simple setups where you only want virus scanning
a whole lot easier to set up.

* Fixes *
1 A minor rewrite of a bit of the TNEF code to handle some systems' odd
opinions about tainting data.
1 Minor tweak to avoid warning about insecure dependency in WorkArea.pm.
2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
3 Fixed "MailScanner --lint" to not throw an erroneous error message
about "MSlint" directory permissions.
3 Fixed error in MIME boundary checking that stopped a few very rare
cases being checked.
5 Fixed issue where zip files in messages were unpacked with incorrect
permissions.
5-2 Fixed bug introduced in 5-1.
7 Fixed ruleset-from-function bug introduced in 5-1.
9 Fixed bug where %variables% would not work in ruleset files.
10 Fixed bug on Linux systems where Postfix systems would change the
ownership of the queue and work directories every time MailScanner was
started.
1 Deny File MIME Types was ignored if new filetype rules used MIME
checks.
2 Slightly improvement to phishing trap to handle links with " in them.
2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!

All available from www.mailscanner.info as usual.

I would be very grateful if you could test this release and prove it's
okay. In a few days I will release a stable version, if I get enough
response that it is indeed all working okay.

Thanks folks!

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Herefordshire Council.
You should be aware that Herefordshire Council 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!
)
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at how complicated the computers and their networks must have been in order to keep track of every single transaction for every single customer. Then, I got to work for a bank for 6 years as the person responsible for the money transfer system. Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets
> with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek,
> SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to
> /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing
> else at all. This makes simple setups where you only want virus
> scanning
> a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) Peter,
At the risk of jinxing it, I do have to jump to MailScanner's defence and say
that in three years of updating MailScanner on a system which handles 25-30,000
emails a day, I am yet to encounter an issue during an upgrade.

Perhaps I have just been lucky, or you have been especially unlucky?

Kind Regards,
Richard

-----Original Message-----
[mailto:mailscanner-] On Behalf Of Peter Ong
Posted At: 03 August 2010 15:07
Posted To: Hostmaster
Conversation: New beta release 4.81.2
Subject: Re: New beta release 4.81.2

> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.

When I was a kid, my mom would take me to Bank of America, and I would marvel at
how complicated the computers and their networks must have been in order to keep
track of every single transaction for every single customer. Then, I got to work
for a bank for 6 years as the person responsible for the money transfer system.
Now I fear putting money in any bank, especially that one.

MailScanner took me a few weeks to tame what with all the "file" command issues
we had. Now that I'm seeing the behind the scenes of the upgrade and I'm still
licking my wounds, I dread this upgrade.

p

----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 3:33:56 AM
> Subject: New beta release 4.81.2
>
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
> Since 4.79, quite a few things have happened:
>
> * New Features and Improvements *
> 1 Upgraded AVG support to AVG version 8. Support no longer guaranteed
>
> for older versions.
> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> directory if the file or link exists.
> 3 Added support for McAfee version 6. Use the virus scanner name
> "mcafee6" to get this support. Many thanks to Phil Randal and Michael
>
> Miller for all their hard work on this.
> 4 Improved "file" command output processing so it stops at 1st "," to
>
> reduce false alarms greatly.
> 5 Added facility for over-riding MailScanner.conf settings and
> rulesets with those held in an SQL database.
> New settings are:
> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> See the MailScanner.conf file for more details.
> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> dependency.
> 1 Slight improvement to check_mailscanner script to send some output
> to /dev/null for Greg Kuhnert.
> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> nothing else at all. This makes simple setups where you only want
> virus scanning a whole lot easier to set up.
>
> * Fixes *
> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> odd
> opinions about tainting data.
> 1 Minor tweak to avoid warning about insecure dependency in
> WorkArea.pm.
> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> 3 Fixed "MailScanner --lint" to not throw an erroneous error message
> about "MSlint" directory permissions.
> 3 Fixed error in MIME boundary checking that stopped a few very rare
> cases being checked.
> 5 Fixed issue where zip files in messages were unpacked with incorrect
>
> permissions.
> 5-2 Fixed bug introduced in 5-1.
> 7 Fixed ruleset-from-function bug introduced in 5-1.
> 9 Fixed bug where %variables% would not work in ruleset files.
> 10 Fixed bug on Linux systems where Postfix systems would change the
> ownership of the queue and work directories every time MailScanner was
>
> started.
> 1 Deny File MIME Types was ignored if new filetype rules used MIME
> checks.
> 2 Slightly improvement to phishing trap to handle links with " in
> them.
> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>
> All available from www.mailscanner.info as usual.
>
> I would be very grateful if you could test this release and prove it's
>
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.
>
> Thanks folks!
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> --
> 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!
 
 
All E-Mail communications are monitored in addition to being content checked for malicious codes or viruses. The success of scanning products is not guaranteed, therefore the recipient(s) should carry out any checks that they believe to be appropriate in this respect.
 
This message (including any attachments and/or related materials) is confidential to and is the property of Computer Service Centre, unless otherwise noted. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
 
Any views or opinions presented are solely those of the author and do not necessarily represent those of Computer Service Centre.
--
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!
)
Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.

It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.

Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.

And by the way, my servers have a load of over 100K per day too. (o:`,

As to my luck, well, the lottery here is up to 42 million again. We'll see.

hehehe

p


----- Original Message -----

> From: "Hostmaster" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 7:23:32 AM
> Subject: RE: New beta release 4.81.2
>
> Peter,
> At the risk of jinxing it, I do have to jump to MailScanner's defence
> and say
> that in three years of updating MailScanner on a system which handles
> 25-30,000
> emails a day, I am yet to encounter an issue during an upgrade.
>
> Perhaps I have just been lucky, or you have been especially unlucky?
>
> Kind Regards,
> Richard
>
> -----Original Message-----
> From: mailscanner-
> [mailto:mailscanner-] On Behalf Of Peter
> Ong
> Posted At: 03 August 2010 15:07
> Posted To: Hostmaster
> Conversation: New beta release 4.81.2
> Subject: Re: New beta release 4.81.2
>
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
>
> When I was a kid, my mom would take me to Bank of America, and I would
> marvel at
> how complicated the computers and their networks must have been in
> order to keep
> track of every single transaction for every single customer. Then, I
> got to work
> for a bank for 6 years as the person responsible for the money
> transfer system.
> Now I fear putting money in any bank, especially that one.
>
> MailScanner took me a few weeks to tame what with all the "file"
> command issues
> we had. Now that I'm seeing the behind the scenes of the upgrade and
> I'm still
> licking my wounds, I dread this upgrade.
>
> p
>
> ----- Original Message -----
>
> > From: "Julian Field" <>
> > To: "MailScanner discussion" <>
> > Sent: Tuesday, August 3, 2010 3:33:56 AM
> > Subject: New beta release 4.81.2
> >
> > I have just released a new beta, with the intention of it becoming
> a
> > stable release Real Soon Now(tm).
> > Since 4.79, quite a few things have happened:
> >
> > * New Features and Improvements *
> > 1 Upgraded AVG support to AVG version 8. Support no longer
> guaranteed
> >
> > for older versions.
> > 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> > directory if the file or link exists.
> > 3 Added support for McAfee version 6. Use the virus scanner name
> > "mcafee6" to get this support. Many thanks to Phil Randal and
> Michael
> >
> > Miller for all their hard work on this.
> > 4 Improved "file" command output processing so it stops at 1st ","
> to
> >
> > reduce false alarms greatly.
> > 5 Added facility for over-riding MailScanner.conf settings and
> > rulesets with those held in an SQL database.
> > New settings are:
> > DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
> > Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
> > See the MailScanner.conf file for more details.
> > 5 Added dependency "Sys::SigAction" Perl modules to installers.
> > 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> > dependency.
> > 1 Slight improvement to check_mailscanner script to send some
> output
> > to /dev/null for Greg Kuhnert.
> > 2 "Scan Messages = virus" will *only* scan mail for viruses and
> > nothing else at all. This makes simple setups where you only want
> > virus scanning a whole lot easier to set up.
> >
> > * Fixes *
> > 1 A minor rewrite of a bit of the TNEF code to handle some systems'
> > odd
> > opinions about tainting data.
> > 1 Minor tweak to avoid warning about insecure dependency in
> > WorkArea.pm.
> > 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
> > 3 Fixed "MailScanner --lint" to not throw an erroneous error
> message
> > about "MSlint" directory permissions.
> > 3 Fixed error in MIME boundary checking that stopped a few very
> rare
> > cases being checked.
> > 5 Fixed issue where zip files in messages were unpacked with
> incorrect
> >
> > permissions.
> > 5-2 Fixed bug introduced in 5-1.
> > 7 Fixed ruleset-from-function bug introduced in 5-1.
> > 9 Fixed bug where %variables% would not work in ruleset files.
> > 10 Fixed bug on Linux systems where Postfix systems would change
> the
> > ownership of the queue and work directories every time MailScanner
> was
> >
> > started.
> > 1 Deny File MIME Types was ignored if new filetype rules used MIME
> > checks.
> > 2 Slightly improvement to phishing trap to handle links with " in
> > them.
> > 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
> >
> > All available from www.mailscanner.info as usual.
> >
> > I would be very grateful if you could test this release and prove
> it's
> >
> > okay. In a few days I will release a stable version, if I get
> enough
> > response that it is indeed all working okay.
> >
> > Thanks folks!
> >
> > Jules
> >
> > --
> > Julian Field MEng CITP CEng
> > www.MailScanner.info
> > Buy the MailScanner book at www.MailScanner.info/store
> >
> > Need help customising MailScanner?
> > Contact me!
> > Need help fixing or optimising your systems?
> > Contact me!
> > Need help getting you started solving new requirements from your
> boss?
> > Contact me!
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> > Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> > --
> > 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!
>  
>  
> All E-Mail communications are monitored in addition to being content
> checked for malicious codes or viruses. The success of scanning
> products is not guaranteed, therefore the recipient(s) should carry
> out any checks that they believe to be appropriate in this respect.
>  
> This message (including any attachments and/or related materials) is
> confidential to and is the property of Computer Service Centre, unless
> otherwise noted. If you are not the intended recipient, you should
> delete this message and are hereby notified that any disclosure,
> copying, or distribution of this message, or the taking of any action
> based on it, is strictly prohibited.
>  
> Any views or opinions presented are solely those of the author and do
> not necessarily represent those of Computer Service Centre.
> --
> 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!
) In case you need to change it back to its old behaviour, you want to
look at lines 413 and 414 of SweepOther.pm.
Line 413 is the old code (commented out) and line 414 is the new code.
Simply move the comment symbol # to the other line to revert to the old
behaviour.

All it does is only look in the output of the file command (or of "file
-i") for all the filetype-desribing text up to, but not including, the
first "," instead of until the end of the line. This improves the
behaviour with some filetypes, particularly Word documents, where the
output of "file" includes loads of information extracted from the file
being studied. That extra information may contain all sorts of things
which are detected as keywords in your filetype.rules.conf file.

Hopefully that will make the upgrade a whole lot easier for you!

Jules.

On 03/08/2010 15:50, Peter Ong wrote:
> Oh no, I was just drawing similarities, but not intended as an indictment to MailScanner at all. In fact, I suggested once that its name should be changed to Awesome MailScanner.
>
> It's just that the file command was a very hairy situation for me until I got it working the way I wanted it; and I was hardly getting any love from everyone about it. Of course, whether what I did was the right thing remains unknown, but it is now doing what I want it to do.
>
> Given the trauma I incurred during that time and seeing the "file" command related fixes in this release, I don't know how they will affect the configurations that were painstakingly borne from the fiery tempers of my users and especially the impatience of my higher ups.
>
> And by the way, my servers have a load of over 100K per day too. (o:`,
>
> As to my luck, well, the lottery here is up to 42 million again. We'll see.
>
> hehehe
>
> p
>
>
> ----- Original Message -----
>
>
>> From: "Hostmaster"<>
>> To: "MailScanner discussion"<>
>> Sent: Tuesday, August 3, 2010 7:23:32 AM
>> Subject: RE: New beta release 4.81.2
>>
>> Peter,
>> At the risk of jinxing it, I do have to jump to MailScanner's defence
>> and say
>> that in three years of updating MailScanner on a system which handles
>> 25-30,000
>> emails a day, I am yet to encounter an issue during an upgrade.
>>
>> Perhaps I have just been lucky, or you have been especially unlucky?
>>
>> Kind Regards,
>> Richard
>>
>> -----Original Message-----
>> From: mailscanner-
>> [mailto:mailscanner-] On Behalf Of Peter
>> Ong
>> Posted At: 03 August 2010 15:07
>> Posted To: Hostmaster
>> Conversation: New beta release 4.81.2
>> Subject: Re: New beta release 4.81.2
>>
>>
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>>
>> When I was a kid, my mom would take me to Bank of America, and I would
>> marvel at
>> how complicated the computers and their networks must have been in
>> order to keep
>> track of every single transaction for every single customer. Then, I
>> got to work
>> for a bank for 6 years as the person responsible for the money
>> transfer system.
>> Now I fear putting money in any bank, especially that one.
>>
>> MailScanner took me a few weeks to tame what with all the "file"
>> command issues
>> we had. Now that I'm seeing the behind the scenes of the upgrade and
>> I'm still
>> licking my wounds, I dread this upgrade.
>>
>> p
>>
>> ----- Original Message -----
>>
>>
>>> From: "Julian Field"<>
>>> To: "MailScanner discussion"<>
>>> Sent: Tuesday, August 3, 2010 3:33:56 AM
>>> Subject: New beta release 4.81.2
>>>
>>> I have just released a new beta, with the intention of it becoming
>>>
>> a
>>
>>> stable release Real Soon Now(tm).
>>> Since 4.79, quite a few things have happened:
>>>
>>> * New Features and Improvements *
>>> 1 Upgraded AVG support to AVG version 8. Support no longer
>>>
>> guaranteed
>>
>>> for older versions.
>>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
>>> directory if the file or link exists.
>>> 3 Added support for McAfee version 6. Use the virus scanner name
>>> "mcafee6" to get this support. Many thanks to Phil Randal and
>>>
>> Michael
>>
>>> Miller for all their hard work on this.
>>> 4 Improved "file" command output processing so it stops at 1st ","
>>>
>> to
>>
>>> reduce false alarms greatly.
>>> 5 Added facility for over-riding MailScanner.conf settings and
>>> rulesets with those held in an SQL database.
>>> New settings are:
>>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL Quick
>>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL Debug.
>>> See the MailScanner.conf file for more details.
>>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
>>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
>>> dependency.
>>> 1 Slight improvement to check_mailscanner script to send some
>>>
>> output
>>
>>> to /dev/null for Greg Kuhnert.
>>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
>>> nothing else at all. This makes simple setups where you only want
>>> virus scanning a whole lot easier to set up.
>>>
>>> * Fixes *
>>> 1 A minor rewrite of a bit of the TNEF code to handle some systems'
>>> odd
>>> opinions about tainting data.
>>> 1 Minor tweak to avoid warning about insecure dependency in
>>> WorkArea.pm.
>>> 2 Fixed documentation for "Allow Multiple HTML Signatures" setting.
>>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
>>>
>> message
>>
>>> about "MSlint" directory permissions.
>>> 3 Fixed error in MIME boundary checking that stopped a few very
>>>
>> rare
>>
>>> cases being checked.
>>> 5 Fixed issue where zip files in messages were unpacked with
>>>
>> incorrect
>>
>>> permissions.
>>> 5-2 Fixed bug introduced in 5-1.
>>> 7 Fixed ruleset-from-function bug introduced in 5-1.
>>> 9 Fixed bug where %variables% would not work in ruleset files.
>>> 10 Fixed bug on Linux systems where Postfix systems would change
>>>
>> the
>>
>>> ownership of the queue and work directories every time MailScanner
>>>
>> was
>>
>>> started.
>>> 1 Deny File MIME Types was ignored if new filetype rules used MIME
>>> checks.
>>> 2 Slightly improvement to phishing trap to handle links with " in
>>> them.
>>> 2 Worked around nasty behaviour of Perl's "each()". Thanks Timofey!
>>>
>>> All available from www.mailscanner.info as usual.
>>>
>>> I would be very grateful if you could test this release and prove
>>>
>> it's
>>
>>> okay. In a few days I will release a stable version, if I get
>>>
>> enough
>>
>>> response that it is indeed all working okay.
>>>
>>> Thanks folks!
>>>
>>> Jules
>>>
>>> --
>>> Julian Field MEng CITP CEng
>>> www.MailScanner.info
>>> Buy the MailScanner book at www.MailScanner.info/store
>>>
>>> Need help customising MailScanner?
>>> Contact me!
>>> Need help fixing or optimising your systems?
>>> Contact me!
>>> Need help getting you started solving new requirements from your
>>>
>> boss?
>>
>>> Contact me!
>>>
>>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>>
>>>
>>> --
>>> This message has been scanned for viruses and dangerous content by
>>> MailScanner, and is believed to be clean.
>>>
>>> --
>>> 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!
>>
>>
>> All E-Mail communications are monitored in addition to being content
>> checked for malicious codes or viruses. The success of scanning
>> products is not guaranteed, therefore the recipient(s) should carry
>> out any checks that they believe to be appropriate in this respect.
>>
>> This message (including any attachments and/or related materials) is
>> confidential to and is the property of Computer Service Centre, unless
>> otherwise noted. If you are not the intended recipient, you should
>> delete this message and are hereby notified that any disclosure,
>> copying, or distribution of this message, or the taking of any action
>> based on it, is strictly prohibited.
>>
>> Any views or opinions presented are solely those of the author and do
>> not necessarily represent those of Computer Service Centre.
>> --
>> 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!
>>

Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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!
) > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the
> fiery tempers of my users and especially the impatience of my higher
> ups.

Peter, given that, I'd highly recommend setting up a testing server
where you can send a "shadow copy" of all your production e-mail in
order to run it through the new version and see how things behave. This
is what I do here and allows me to run a new version with production
data but without having to touch the production server until I'm ready
to deploy. This type of set up may alleviate some of your concerns
about upgrading to newer versions. But I do know where you are coming
from - if it ain't broke, don't fix it, as they say.

cheers,


--tom


--
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!
) Thanks, Thomas. Actually I already do that. In fact, I have a mini-replica of the office at home. I run my own email server at home; trying to avoid getting caught in the next round of warrantless tapping by the next time the Patriot Act is invoked. I know I'll still be all over google's servers, but I'll at least minimize it. Hahaha.

In any case, yes, I'll test the upgrade at my crib first, and then see how well that goes. When I get a good feeling about it, I'll deploy in the office. Thanks.

p

----- Original Message -----

> From: "Thomas Lohman" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 8:53:42 AM
> Subject: Re: New beta release 4.81.2
>
> > Given the trauma I incurred during that time and seeing the "file"
> > command related fixes in this release, I don't know how they will
> > affect the configurations that were painstakingly borne from the
> > fiery tempers of my users and especially the impatience of my
> higher
> > ups.
>
> Peter, given that, I'd highly recommend setting up a testing server
> where you can send a "shadow copy" of all your production e-mail in
> order to run it through the new version and see how things behave.
> This
> is what I do here and allows me to run a new version with production
> data but without having to touch the production server until I'm ready
>
> to deploy. This type of set up may alleviate some of your concerns
> about upgrading to newer versions. But I do know where you are coming
>
> from - if it ain't broke, don't fix it, as they say.
>
> cheers,
>
>
> --tom
>
>
> --
> 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!
) Thanks Julian. I'm making a note of it.

p


----- Original Message -----

> From: "Julian Field" <>
> To: "MailScanner discussion" <>
> Sent: Tuesday, August 3, 2010 8:24:55 AM
> Subject: Re: New beta release 4.81.2
>
> In case you need to change it back to its old behaviour, you want to
> look at lines 413 and 414 of SweepOther.pm.
> Line 413 is the old code (commented out) and line 414 is the new
> code.
> Simply move the comment symbol # to the other line to revert to the
> old
> behaviour.
>
> All it does is only look in the output of the file command (or of
> "file
> -i") for all the filetype-desribing text up to, but not including, the
>
> first "," instead of until the end of the line. This improves the
> behaviour with some filetypes, particularly Word documents, where the
>
> output of "file" includes loads of information extracted from the file
>
> being studied. That extra information may contain all sorts of things
>
> which are detected as keywords in your filetype.rules.conf file.
>
> Hopefully that will make the upgrade a whole lot easier for you!
>
> Jules.
>
> On 03/08/2010 15:50, Peter Ong wrote:
> > Oh no, I was just drawing similarities, but not intended as an
> indictment to MailScanner at all. In fact, I suggested once that its
> name should be changed to Awesome MailScanner.
> >
> > It's just that the file command was a very hairy situation for me
> until I got it working the way I wanted it; and I was hardly getting
> any love from everyone about it. Of course, whether what I did was the
> right thing remains unknown, but it is now doing what I want it to
> do.
> >
> > Given the trauma I incurred during that time and seeing the "file"
> command related fixes in this release, I don't know how they will
> affect the configurations that were painstakingly borne from the fiery
> tempers of my users and especially the impatience of my higher ups.
> >
> > And by the way, my servers have a load of over 100K per day too.
> (o:`,
> >
> > As to my luck, well, the lottery here is up to 42 million again.
> We'll see.
> >
> > hehehe
> >
> > p
> >
> >
> > ----- Original Message -----
> >
> >
> >> From: "Hostmaster"<>
> >> To: "MailScanner discussion"<>
> >> Sent: Tuesday, August 3, 2010 7:23:32 AM
> >> Subject: RE: New beta release 4.81.2
> >>
> >> Peter,
> >> At the risk of jinxing it, I do have to jump to MailScanner's
> defence
> >> and say
> >> that in three years of updating MailScanner on a system which
> handles
> >> 25-30,000
> >> emails a day, I am yet to encounter an issue during an upgrade.
> >>
> >> Perhaps I have just been lucky, or you have been especially
> unlucky?
> >>
> >> Kind Regards,
> >> Richard
> >>
> >> -----Original Message-----
> >> From: mailscanner-
> >> [mailto:mailscanner-] On Behalf Of
> Peter
> >> Ong
> >> Posted At: 03 August 2010 15:07
> >> Posted To: Hostmaster
> >> Conversation: New beta release 4.81.2
> >> Subject: Re: New beta release 4.81.2
> >>
> >>
> >>> 4 Improved "file" command output processing so it stops at 1st
> ","
> >>>
> >> to
> >>
> >>> reduce false alarms greatly.
> >>>
> >> When I was a kid, my mom would take me to Bank of America, and I
> would
> >> marvel at
> >> how complicated the computers and their networks must have been in
> >> order to keep
> >> track of every single transaction for every single customer. Then,
> I
> >> got to work
> >> for a bank for 6 years as the person responsible for the money
> >> transfer system.
> >> Now I fear putting money in any bank, especially that one.
> >>
> >> MailScanner took me a few weeks to tame what with all the "file"
> >> command issues
> >> we had. Now that I'm seeing the behind the scenes of the upgrade
> and
> >> I'm still
> >> licking my wounds, I dread this upgrade.
> >>
> >> p
> >>
> >> ----- Original Message -----
> >>
> >>
> >>> From: "Julian Field"<>
> >>> To: "MailScanner discussion"<>
> >>> Sent: Tuesday, August 3, 2010 3:33:56 AM
> >>> Subject: New beta release 4.81.2
> >>>
> >>> I have just released a new beta, with the intention of it
> becoming
> >>>
> >> a
> >>
> >>> stable release Real Soon Now(tm).
> >>> Since 4.79, quite a few things have happened:
> >>>
> >>> * New Features and Improvements *
> >>> 1 Upgraded AVG support to AVG version 8. Support no longer
> >>>
> >> guaranteed
> >>
> >>> for older versions.
> >>> 2 Installers no longer over-write mailscanner.cf in SpamAssassin
> >>> directory if the file or link exists.
> >>> 3 Added support for McAfee version 6. Use the virus scanner name
> >>> "mcafee6" to get this support. Many thanks to Phil Randal and
> >>>
> >> Michael
> >>
> >>> Miller for all their hard work on this.
> >>> 4 Improved "file" command output processing so it stops at 1st
> ","
> >>>
> >> to
> >>
> >>> reduce false alarms greatly.
> >>> 5 Added facility for over-riding MailScanner.conf settings and
> >>> rulesets with those held in an SQL database.
> >>> New settings are:
> >>> DB DSN, DB Username, DB Password, SQL Serial Number, SQL
> Quick
> >>> Peek, SQL Config, SQL Ruleset, SQL SpamAssassin Config, SQL
> Debug.
> >>> See the MailScanner.conf file for more details.
> >>> 5 Added dependency "Sys::SigAction" Perl modules to installers.
> >>> 6 Updated to Archive::Zip 1.30 and added Compress::Raw::Zlib
> >>> dependency.
> >>> 1 Slight improvement to check_mailscanner script to send some
> >>>
> >> output
> >>
> >>> to /dev/null for Greg Kuhnert.
> >>> 2 "Scan Messages = virus" will *only* scan mail for viruses and
> >>> nothing else at all. This makes simple setups where you only want
> >>> virus scanning a whole lot easier to set up.
> >>>
> >>> * Fixes *
> >>> 1 A minor rewrite of a bit of the TNEF code to handle some
> systems'
> >>> odd
> >>> opinions about tainting data.
> >>> 1 Minor tweak to avoid warning about insecure dependency in
> >>> WorkArea.pm.
> >>> 2 Fixed documentation for "Allow Multiple HTML Signatures"
> setting.
> >>> 3 Fixed "MailScanner --lint" to not throw an erroneous error
> >>>
> >> message
> >>
> >>> about "MSlint" directory permissions.
> >>> 3 Fixed error in MIME boundary checking that stopped a few very
> >>>
> >> rare
> >>
> >>> cases being checked.
> >>> 5 Fixed issue where zip files in messages were unpacked with
> >>>
> >> incorrect
> >>
> >>> permissions.
> >>> 5-2 Fixed bug introduced in 5-1.
> >>> 7 Fixed ruleset-from-function bug introduced in 5-1.
> >>> 9 Fixed bug where %variables% would not work in ruleset files.
> >>> 10 Fixed bug on Linux systems where Postfix systems would change
> >>>
> >> the
> >>
> >>> ownership of the queue and work directories every time
> MailScanner
> >>>
> >> was
> >>
> >>> started.
> >>> 1 Deny File MIME Types was ignored if new filetype rules used
> MIME
> >>> checks.
> >>> 2 Slightly improvement to phishing trap to handle links with " in
> >>> them.
> >>> 2 Worked around nasty behaviour of Perl's "each()". Thanks
> Timofey!
> >>>
> >>> All available from www.mailscanner.info as usual.
> >>>
> >>> I would be very grateful if you could test this release and prove
> >>>
> >> it's
> >>
> >>> okay. In a few days I will release a stable version, if I get
> >>>
> >> enough
> >>
> >>> response that it is indeed all working okay.
> >>>
> >>> Thanks folks!
> >>>
> >>> Jules
> >>>
> >>> --
> >>> Julian Field MEng CITP CEng
> >>> www.MailScanner.info
> >>> Buy the MailScanner book at www.MailScanner.info/store
> >>>
> >>> Need help customising MailScanner?
> >>> Contact me!
> >>> Need help fixing or optimising your systems?
> >>> Contact me!
> >>> Need help getting you started solving new requirements from your
> >>>
> >> boss?
> >>
> >>> Contact me!
> >>>
> >>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> >>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
> >>>
> >>>
> >>> --
> >>> This message has been scanned for viruses and dangerous content
> by
> >>> MailScanner, and is believed to be clean.
> >>>
> >>> --
> >>> 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!
> >>
> >>
> >> All E-Mail communications are monitored in addition to being
> content
> >> checked for malicious codes or viruses. The success of scanning
> >> products is not guaranteed, therefore the recipient(s) should
> carry
> >> out any checks that they believe to be appropriate in this
> respect.
> >>
> >> This message (including any attachments and/or related materials)
> is
> >> confidential to and is the property of Computer Service Centre,
> unless
> >> otherwise noted. If you are not the intended recipient, you should
> >> delete this message and are hereby notified that any disclosure,
> >> copying, or distribution of this message, or the taking of any
> action
> >> based on it, is strictly prohibited.
> >>
> >> Any views or opinions presented are solely those of the author and
> do
> >> not necessarily represent those of Computer Service Centre.
> >> --
> >> 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!
> >>
>
> Jules
>
> --
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your
> boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> 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!
) On 11:59 AM, Julian Field wrote:
> I have just released a new beta, with the intention of it becoming a
> stable release Real Soon Now(tm).
[...]
> I would be very grateful if you could test this release and prove it's
> okay. In a few days I will release a stable version, if I get enough
> response that it is indeed all working okay.


Installed about an hour ago. All good so far.

--
Mark Sapiro <> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan

--
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!
)