t.d.lee at durham.ac.uk
Fri Feb 22 14:49:29 GMT 2008
Julian: A suggestion to assist large sites which sit behind tight
The "cron.daily" scripts "update_phishing_sites" and "update_spamassassin"
need to reach out to remote websites. But at some large sites, the
general practice is for web browsers to divert via a cache service. In
this context the MS "update*" scripts are web clients (pseudo-browsers)
and so the site-friendly way for the sites to work would be to honour any
"http_proxy" environment variable.
That is almost, but not quite, already in place. (Run manually, with
explicit "http_proxy", it works.)
What still seems absent is recognising "http_proxy" when run under "cron".
Those scripts already do:
if [ -f /etc/sysconfig/MailScanner ] ; then
But that file seems oriented to variables specific to "MailScanner.conf".
Could there also be a "/etc/sysconfig/MailScannerEnv" (or similar) whose
purpose would be for environment variables for scripts?
(I suppose the whole lot could be overloaded into the existing "sysconfig"
file; my reason for suggesting a second file was a clean separation
between script/envir variables and MS.conf variables.)
Just a thought.
What would be your recommendation for getting "http_proxy" recognised by
those scripts under cron?
: David Lee I.T. Service :
: Senior Systems Programmer Computer Centre :
: UNIX Team Leader Durham University :
: South Road :
: http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE :
: Phone: +44 191 334 2752 U.K. :
More information about the MailScanner