The folder location is correct for Ubuntu. I checked the files this morning and they all updated ok. It looks like it is curl that was causing the problem. Curl is used to download the gpg keys, if that fails, the rest fails.
Copying the .curlrc file with the proxy settings to /var/lib/spamassassin (Debian-spamd's home folder) seems to have helped. I will leave it A few days more to ensure its working ok. Peter Hutchison MCP Senior Network Systems SpecialistS S 01484 473716 Networks Team University of Huddersfield | Queensgate | Huddersfield | HD1 3DH > -----Original Message----- > From: Bill Cole [mailto:sausers-20150...@billmail.scconsult.com] > Sent: 07 June 2018 06:11 > To: Spam Assassin <users@spamassassin.apache.org> > Subject: Re: Problem with sa-update via proxy > > On 5 Jun 2018, at 4:24, Peter Hutchison wrote: > > > I have recently upgraded my mail mta servers from Ubuntu 14.04 to > > Ubuntu 16.04 but the daily spamassassin cron job is failing to update > > the database in > > /usr/lib/spamassassin/3.9004001/update_spamassassin_org folder. > > That's a very odd version number. Is that an Ubuntu thing? > > > I have made sure that the cron job has the proxy env variables set and > > also updated /etc/wgetrc But it still regularly fails with this > > error. I have even configured .curlrc file in root profile with proxy > > settings. > > > > > > /etc/cron.daily/spamassassin: > > > > channel: could not find working mirror, channel failed sa-update > > failed for unknown reasons I can manually update it ok, but not via a > > cron job. What else do I need to configure to ensure it works every > > time? > > Impossible to say for sure. Adding "-D" to the actual sa-update > invocation in /etc/cron.daily/spamassassin would provide more extensive > detail about what's happening. University of Huddersfield inspiring tomorrow's professionals. [http://marketing.hud.ac.uk/_HOSTED/EmailSig2014/EmailSigFooter.jpg] This transmission is confidential and may be legally privileged. If you receive it in error, please notify us immediately by e-mail and remove it from your system. If the content of this e-mail does not relate to the business of the University of Huddersfield, then we do not endorse it and will accept no liability.
