complaint from 4.68.4 (now 4.68.5)

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Jeff A. Earickson wrote:
> On Tue, 18 Mar 2008, Julian Field wrote:
> Julian,
>
> Ok, nevermind about hostname, I just saw the "perl -wc" complaint and
> wondered...
>
>>> Is there any particular requirement on the white space in this file, 
>>> eg:
>>>
>>>    127.0.0.1[something]100000
>>>
>>> Does [something] have to be a tab, or can it be any whitespace?
>
> The burning question for me right now...  ???!!
Try commenting out the IPBlock stuff from CustomConfig.pm and see if it 
then does a --lint okay.
>
> Here's the "perl -wc" complaints I see right now:
>
> (190)> perl -wc CustomConfig.pm
> Unquoted string "hostname" may clash with future reserved word at 
> CustomConfig.pm line 300.
> Parameterless "use IO" deprecated at CustomConfig.pm line 749
> "my" variable $LimitsH masks earlier declaration in same scope at 
> CustomConfig.pm line 796.
> Use of implicit split to @_ is deprecated at CustomConfig.pm line 822.
> Use of implicit split to @_ is deprecated at CustomConfig.pm line 838.
> CustomConfig.pm syntax OK
> (191)> perl -wc Config.pm
> Useless use of hash element in void context at Config.pm line 892.
> Use of implicit split to @_ is deprecated at Config.pm line 2066.
> Name "MailScanner::Config::ConfFile" used only once: possible typo at 
> Config.pm line 806.
> Config.pm syntax OK
>
> Jeff Earickson

Jules

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

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.1 (Build 2523)
Comment: Use Thunderbird Enigmail to verify this message
Charset: ISO-8859-1

wj8DBQFH4AtWEfZZRxQVtlQRAobCAJ9NhAxwN5R9M0d0lG7bHUV9XGUtRACgy3nk
sLeTwI9KtZOmk4IwN/oZKhw=
=D9Dv
-----END PGP SIGNATURE-----

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