Experimental repository for RHEL 5 / Centos 5

Julian Field MailScanner at ecs.soton.ac.uk
Wed Nov 21 15:15:13 GMT 2007


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



Brendan Pirie wrote:
> Hugo van der Kooij wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Scott Silva wrote:
>>
>>> Ran this repo today and it gets all requires very well. Installed on
>>> X86-64 with no issues. Are there any optional modules that anyone 
>>> thinks
>>> are helpful?
>>> I would vote for perl-Mail-ClamAV, perl-Convert-TNEF, and maybe the SPF
>>> modules for spamassassin.
>>
>> There is not really an optional thing in rpm terms. So if the
>> requirement is defined one is stuck with the modules wether one uses
>> them or not.
>>
>> I am not sure what would be wise here. Perhaps two wrappers instead of
>> one. So the current one defines the absolute minimum and a
>> mailscanner-wrapper-complete version that will pull in lots of other
>> usefull modules as well as the basic wrapper but some of these extra
>> modules may never be used depending on the configuration.
>>
>> In such case I would also like to describe them briefly. So one can
>> discard the outer wrapper and then remove the unneeded modules with a
>> small guidance.
>>
>> I am thinking along the lines of a text file with entries like:
>>
>>  <some MS config option>
>>     Requires: <some perl module>
>>
>> Nothing fancy (TM).
>>
>> Feel free to think out loud on the matter. I didn't hesitate either ;-)
>>
>> Hugo.
>>
> Another possibility would be something like MailScanner.rpm for the 
> "most common" install options, and MailScanner-extras.rpm for features 
> not everyone needs as an additional rpm, instead of packaging 
> MailScanner twice.  This would also reduce space on the server and 
> bandwidth usage.
>
> Depending on needs/wants/opinions the "extras" could be further broken 
> down, such as MailScanner-spf.rpm, etc.. and people could install only 
> those extra features/packages they want.
That is making it very complicated for new users to be able to use. They 
won't know what features/packages they want. It has to be *very* simple 
for new users to get a sane default setup that includes all the 
protection they are likely to need.

>
> Just thinking out loud (pre-coffee) ;)
>
> Brendan
>
> P.S.  As a CentOS user myself, I naturally think a MailScanner 
> addition to rpmforge is a great idea! :)  (It also gives me another 
> argument for MailScanner when discussing MailScanner vs. Amavis with 
> fellow CentOS users)
>

Jules

- -- 
Julian Field MEng CITP
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
For all your IT requirements visit www.transtec.co.uk


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.7.0 (Build 867)
Comment: Use Thunderbird's Enigmail Add-on to verify this message
Charset: ISO-8859-1

wj8DBQFHREuHEfZZRxQVtlQRAt4nAKDC3sLr/9CjbQovuAPWtusaBH3lawCgu3sm
0/FFPSuOGjy4HszmXdaMnAk=
=8rQd
-----END PGP SIGNATURE-----

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



More information about the MailScanner mailing list