Feedback on MailScanner 4.56.1-1 beta

[Jim Holland]

Hi Julian

I installed the above beta version this evening on Red Hat 7.1 earlier 
this evening, just after installing sendmail 8.13.8.  See details of 
configuration below (you may notice that it is using Sys::Syslog version 
0.01 - the current version does not compile on RH 7.1).

The installation went fine, but I experienced the following error when 
trying to start MailScanner:

	Can't locate Sys/Hostname/Long.pm in @INC . . .

That was solved by installing Sys::Hostname::Long using cpan and it worked 
fine after that.

You have very kindly included a new facility for providing separate 
reports for messages and attachments which have been blocked or 
quarantined due to user specified size restrictions.  I have done some 
testing on both oversize messages and attachments, and am pleased to 
report that it works exactly as intended for attachments, giving a report 
such as:

	MailScanner: Attachment is too large: 154303 bytes

However in the case of oversize messages, the report is just:

	MailScanner: Message is too large

with no indication of the size of the message that has been quarantined.  
Would it be possible to include the size in that case as well?  That would 
be very helpful for people who don't want to unquarantine a message that 
is far too large for them to handle.

I was not able to test the sender.size.report.txt as the production site
is not bouncing any MailScanner reports back to sender. To be honest, I am
not quite sure how to enable these for test purposes.  I presume it is
just a matter of changing no to yes in:

	# Do you want to notify the people who sent you messages containing
	# viruses or badly-named filenames?
	# This can also be the filename of a ruleset.
	Notify Senders = no
and
	# *If* "Notify Senders" is set to yes, do you want to notify people
	# who sent you messages containing other blocked content, such as
	# partial messages or messages with external bodies?
	# This can also be the filename of a ruleset.
	Notify Senders Of Other Blocked Content = no

The other test not done is to see how the deleted.size.message.txt report 
works.  We are not deleting any messages or attachments at the moment - 
everything gets quarantined.  However to test this, is the only option to
change yes to no in:

	# Do you want to store copies of the infected attachments and messages?
	# This can also be the filename of a ruleset.
	Quarantine Infections = yes

That would mean that everything that was suspect would be deleted.  I 
presume that there is no means of being more selective to delete only 
messages with blocked content, for example?

With clarification on the above I will set up MailScanner on a test server
to confirm that these also work as intended.

Thanks again for your assistance.

Regards

Jim Holland
System Administrator
MANGO - Zimbabwe's non-profit e-mail service


Running on
Linux mail.mango.zw 2.4.20-28.7 #1 Thu Dec 18 11:15:04 EST 2003 i686 unknown
This is Red Hat Linux release 7.1 (Seawolf)
This is Perl version 5.006001 (5.6.1)

This is MailScanner version 4.56.1
Module versions are:
1.14	Archive::Zip
1.119 	Convert::BinHex
1.03	Fcntl
2.6	File::Basename
2.03	File::Copy
2.00	FileHandle
1.0404	File::Path
0.16	File::Temp
0.92	Filesys::Df
1.35	HTML::Entities
3.54	HTML::Parser
2.37	HTML::TokeParser
1.20	IO
1.08	IO::File
1.121	IO::Pipe
1.71	Mail::Header
3.05	MIME::Base64
5.420	MIME::Decoder
5.420	MIME::Decoder::UU
5.420	MIME::Head
5.420	MIME::Parser
3.03	MIME::QuotedPrint
5.420	MIME::Tools
0.10	Net::CIDR
1.03	POSIX
1.72	Socket
1.4	Sys::Hostname::Long
0.01	Sys::Syslog
1.86	Time::HiRes
1.01	Time::localtime

Optional module versions are:
0.17	Convert::TNEF
1.75	DB_File
1.12	DBD::SQLite
1.50	DBI
1.10	Digest
missing	Digest::HMAC
2.36	Digest::MD5
missing	Digest::SHA1
missing	Inline
missing	Mail::ClamAV
missing	Mail::SpamAssassin
missing	Mail::SPF::Query
missing	Net::CIDR::Lite
missing	Net::IP
missing	Net::DNS
missing	Net::LDAP
missing	Parse::RecDescent
missing	SAVI
2.46	Test::Harness
0.62	Test::Simple
missing	Text::Balanced
1.35	URI