MailWatch and CustomConfig.pm

Julian Field mailscanner at ecs.soton.ac.uk
Tue Mar 23 12:20:43 GMT 2004


See 4.29.5. You can have a whole directory of them, rather than just a
single file.

At 22:15 22/03/2004, you wrote:
>Alternate suggestion:
>
>Config parameter
>
>Local Custom Config = <path to custom config file>
>
>This can then be preserved across upgrades by upgrade_MailScanner_conf.
>
> > -----Original Message-----
> > From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
> > Behalf Of James A. Pattie
> > Sent: Monday, March 22, 2004 4:27 PM
> > To: MAILSCANNER at JISCMAIL.AC.UK
> > Subject: Re: MailWatch and CustomConfig.pm
> >
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Julian Field wrote:
> > | At 19:29 22/03/2004, you wrote:
> > |
> > |> As a tarball user, I would also like to see this change.
> > |>
> > |> Preferrably including something in the MailScanner/etc directory.
> > |
> > |
> > | It shouldn't go in etc as it's not  a configuration file,
> > it's executable
> > | code. /opt/MailScanner/lib/MailScanner would be the right
> > place in my
> > | opinion. If not right, then the best we've easily got.
> >
> > Using Debian as an example, they have modified programs
> > (Horde, etc.) to look
> > for user configuration settings in /etc/<packagename>/...
> > instead of putting
> > them in a config file in the web tree, etc.
> >
> > It makes it much easier to look at
> > /etc/MailScanner/CustomConfig.pm or something
> > similiar.  You might even use a directory and any filenames
> > in that directory
> > would be the files to require.
> >
> > Ex:  /etc/MailScanner/CustomConfig/MailWatch.pm
> >
> > would then cause a 'require MailScanner/MailWatch.pm' to be
> > executed in the
> > CustomConfig.pm module.
> >
> > Using the directory approach would allow any new programs to
> > just touch a file
> > in the include directory and voila, their enhancement is
> > available the next time
> > MailScanner reloads.  Now getting a config override so we
> > don't have to hack on
> > the MailScanner.conf file directly, but say source and
> > overload the values from
> > this directory would be even cooler. :)
> >
> > |
> > | I'll try to remember to write this tomorrow. Had enough for
> > tonight (fixing
> > | bugs in binhex decoder).
> > |
> > |
> >
> >
> > - --
> > James A. Pattie
> > james at pcxperience.com
> >
> > Linux -- SysAdmin / Programmer
> > Xperience, Inc.
> > http://www.pcxperience.com/
> > http://www.xperienceinc.com/
> > http://www.pcxperience.org/
> >
> > GPG Key Available at http://www.pcxperience.com/gpgkeys/james.html
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.4 (GNU/Linux)
> > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> >
> > iD8DBQFAX1oQtUXjwPIRLVERAujNAKCDpHxBmesKxBVrYRvOEjREFb5WYACeKLYT
> > EB8/GJRQ+s06ZNcYXOPs+EQ=
> > =CA8b
> > -----END PGP SIGNATURE-----
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> > MailScanner thanks transtec Computers for their support.
> >

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654



More information about the MailScanner mailing list