Re: Requesting help, sa-update, cron, gpg, unsafe ownership on homedir

On 2024-07-12 at 10:51:08 UTC-0400 (Fri, 12 Jul 2024 10:51:08 -0400) Steve Charmer is rumored to have said: I have a cron job running as root, which calls sa-update it warns about unsafe ownership gpg: WARNING: unsafe ownership on homedir

Requesting help, sa-update, cron, gpg, unsafe ownership on homedir

I have a cron job running as root, which calls sa-update it warns about unsafe ownership gpg: WARNING: unsafe ownership on homedir `/var/lib/spamassassin/sa-update-keys' this is my cu

Re: sa-update

On 17 Mar 2023, at 16:03, Bill Cole wrote: Correct. We've had a problem with RuleQA, in that we have not had enough spam in the masscheck submissions to run the rescoring properly. I'm not sure whose submissions have dried up... The existing list of active rules and their scores is fine for n

Re: sa-update

On 2023-03-17 at 05:11:30 UTC-0400 (Fri, 17 Mar 2023 10:11:30 +0100) SA list is rumored to have said: Hello, I didn't get an update since 5 March (1908044). Correct. We've had a problem with RuleQA, in that we have not had enough spam in the masscheck submissions to run the rescoring proper

sa-update

Hello, I didn't get an update since 5 March (1908044). FreeBSD 12.4-RELEASE-p2 spamassassin 4.0.0_2 Mar 17 08:19:41.458 [41854] dbg: channel: metadata version = 1908044, from file /var/db/spamassassin/4.00/updates_spamassassin_org.cf Mar 17 08:19:41.471 [41854] dbg: dns: 0.0.4.updates.spam

sa-update note

Just FYI, Update available for channel updates.spamassassin.org: 1899935 -> 1900065 http: (curl) GET http://sa-update.verein-clean.net/1900065.tar.gz, success http: (curl) GET http://sa-update.verein-clean.net/1900065.tar.gz.sha512, FAILED, status: exit 22 http: (curl) GET http://sa-update.ver

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

On Sun, 25 Apr 2021 13:34:16 -0400 Steve Dondley wrote: > I’m experimenting with writing my own rules. My machines are using SA > 3.4.4 so I want to use the 3.4.4 rules. There is only one set of rules, "if" statements handle any differences.

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

On 2021-04-25 01:47 PM, Henrik K wrote: On Sun, Apr 25, 2021 at 01:28:31PM -0400, Steve Dondley wrote: > mass-check -c parameter expects to find every config file in that single > directory. Now it's missing spamassassin updates and specifically > 20_aux_tlds.cf from there. You could copy it

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

spamassassin -V reports: "SpamAssassin version 3.4.4" I imagine I have to checkout an older 3.4.4 point version from SVN and use the mass-check command from that. It's been ages since I've used SVN. How can I get to the older version via SVN? I solved this by downloading version 3.4.4 of S

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

s? Skipping this > file at > /root/spamassassin-3.4/masses/../lib/Mail/SpamAssassin/Conf/Parser.pm line > 414. svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk spamassassin-trunk Use the rules-directory found in spamassassin-trunk/rules, instead of sa-update directory.

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

On 4/25/21 7:34 PM, Steve Dondley wrote: On Apr 25, 2021, at 1:31 PM, Axb wrote: What are you trying to do? run masscheck for your rules or for the SA project? I’m experimenting with writing my own rules. My machines are using SA 3.4.4 so I want to use the 3.4.4 rules. this may give yo

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

> On Apr 25, 2021, at 1:31 PM, Axb wrote: > > What are you trying to do? > run masscheck for your rules or for the SA project? I’m experimenting with writing my own rules. My machines are using SA 3.4.4 so I want to use the 3.4.4 rules.

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

What are you trying to do? run masscheck for your rules or for the SA project? On 4/25/21 7:28 PM, Steve Dondley wrote: mass-check -c parameter expects to find every config file in that single directory.  Now it's missing spamassassin updates and specifically 20_aux_tlds.cf from there.  You co

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

mass-check -c parameter expects to find every config file in that single directory. Now it's missing spamassassin updates and specifically 20_aux_tlds.cf from there. You could copy it to /etc/spamassassin temporarily, but I'd rather make a completely separate directory that should include

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

t; > -c=/etc/spamassassin/ | grep '. 1' > > > > > > Everything appears to work as expected but I'm getting this warning/error > > when I do: > > > > "config: registryboundaries: no tlds defined, need to run sa-update" > > > > Running sa-upda

Re: Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

cted but I'm getting this warning/error > when I do: > > "config: registryboundaries: no tlds defined, need to run sa-update" > > Running sa-update doesn't fix the problem and a search didn't uncover > anything useful. mass-check -c parameter expects t

Getting "config: registryboundaries: no tlds defined, need to run sa-update" message when running mass-check

es: no tlds defined, need to run sa-update" Running sa-update doesn't fix the problem and a search didn't uncover anything useful.

Re: sa-update error 3 no mirrors.sought.rules.yerp.org

--On Sunday, March 14, 2021 1:23 PM +1000 Simon Wilson wrote: You've not stated your OS but on a RHEL/CentOS 7 box the correct way to remove is to go to /etc/mail/spamassassin/channel.d and delete sought.conf. RHEL bugzilla for the issue:

Re: sa-update error 3 no mirrors.sought.rules.yerp.org

- Message from a...@onet.eu - Date: Fri, 12 Mar 2021 13:16:25 +0100 From: a...@onet.eu Subject: sa-update error 3 no mirrors.sought.rules.yerp.org To: users@spamassassin.apache.org Hi, I'm getting this from cron since two days: channel: no 'mirrors.sought.rule

Re: sa-update error 3 no mirrors.sought.rules.yerp.org

r-2021 05:46:59: SpamAssassin: Unknown error code 3 from sa-update ls /var/lib/spamassassin/3.004000/ sought_rules_yerp_org sought_rules_yerp_org.cf updates_spamassassin_org updates_spamassassin_org.cf rm -rf /var/lib/spamassassin/3.004002/ and then sa-update -D gives no errors, but when I try to run cron

sa-update error 3 no mirrors.sought.rules.yerp.org

Hi, I'm getting this from cron since two days: channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed 11-Mar-2021 05:46:59: SpamAssassin: Unknown error code 3 from sa-update ls /var/lib/spamassassin/3.004000/ sought_rules_yerp_org sought_rules_yerp_org.cf updates_s

Re: Fedora sa-update and systemd randomized timer

On Thu, 31 Dec 2020 16:54:15 -0800 Kenneth Porter wrote: > With the discussion of the KAM channel and Fedora's sa-update script > that uses directory-based channel configuration, I went snooping into > their script and systemd units. It looks like sa-update.cron has a > 2-hour ra

Re: Fedora sa-update and systemd randomized timer

Sounds good here. All saupdate does is a very lightweight DNS check. On Thu, Dec 31, 2020, 19:54 Kenneth Porter wrote: > With the discussion of the KAM channel and Fedora's sa-update script that > uses directory-based channel configuration, I went snooping into their > script and

Fedora sa-update and systemd randomized timer

With the discussion of the KAM channel and Fedora's sa-update script that uses directory-based channel configuration, I went snooping into their script and systemd units. It looks like sa-update.cron has a 2-hour random delay before it looks for updates. I'm thinking it would be ni

Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

Kevin A. McGrail skrev den 2020-07-18 23:32: Great, thanks for the update. With this change we also know how to best prevent similar issues. more nutella :=)

Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

Marcus Schopen wrote: > Am Donnerstag, den 16.07.2020, 17:43 -0400 schrieb Kevin A. McGrail: > > Agreed. 1879851 is after I submitted the fix but doesn;t include the > > fix. I will have to check again after the next rule publishing. > > Sorry for the false alarm. > >

Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

Am Donnerstag, den 16.07.2020, 17:43 -0400 schrieb Kevin A. McGrail: > Agreed. 1879851 is after I submitted the fix but doesn;t include the > fix. I will have to check again after the next rule publishing. > Sorry for the false alarm. Feedback: sa-update without errors now. Tha

Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

Agreed. 1879851 is after I submitted the fix but doesn;t include the fix. I will have to check again after the next rule publishing. Sorry for the false alarm. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail -

Re: sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

Am Mittwoch, den 15.07.2020, 08:11 -0400 schrieb Kevin A. McGrail: > Just an update that this is fixed: > > https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7840 > > Should be a rule update published in the next 48 hours with the fix. > Feedback welcome because we are making fixes for older ve

sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail

te, exiting with >> code 4 >> Update failed, exiting with code 4 >> sa-update failed for unknown reasons >> - >> >> I will send you the complete output. >> > Ahh, that is a new problem and only affects old versions 3.4.2 and > before.  Work

Re: sa-update failing

N TXT "1879218" Regards, KAM On 6/26/2020 4:13 AM, Stephan Fourie wrote: > Hi everyone, > > Our SpamAssassin rules have not gotten any recent updates (looks like > past 2 days). When investigating, sa-update tries to connect to: > 2.4.3.updates.spamassassin.org >

Re: sa-update failing

imes. Use "sa-update -D" to debug and post relevant lines if you have an actual problem. On Fri, Jun 26, 2020 at 10:13:00AM +0200, Stephan Fourie wrote: > Hi everyone, > > Our SpamAssassin rules have not gotten any recent updates (looks like past 2 > days). When investigatin

sa-update failing

Hi everyone, Our SpamAssassin rules have not gotten any recent updates (looks like past 2 days). When investigating, sa-update tries to connect to: 2.4.3.updates.spamassassin.org When doing a DNS lookup on this hostname it appears to be a CNAME which points to:  3.3.3

Re: SA-Update cronjob output rejected by ISP for containing spam

word the problem so the subject is > > > > the > > > > best > > > > I can do for now. Whenever a crojob is run a message is sent > > > > out > > > > via > > > > postfix to me with the contents of that cronjob. This mornin

Re: SA-Update cronjob output rejected by ISP for containing spam

word the problem so the subject is > > > > the > > > > best > > > > I can do for now. Whenever a crojob is run a message is sent > > > > out > > > > via > > > > postfix to me with the contents of that cronjob. This mornin

Re: SA-Update cronjob output rejected by ISP for containing spam

to me with the contents of that cronjob. This morning when the SA-Update cronjob was run I didn't receive the output back (this has been going on since 7 June but that's another story). I looked at my syslog and saw this: https://pastebin.com/hHR0Rvii Since I can't see the debug o

Re: SA-Update cronjob output rejected by ISP for containing spam

; > postfix to me with the contents of that cronjob. This morning when > > the > > SA-Update cronjob was run I didn't receive the output back (this > > has > > been going on since 7 June but that's another story). I looked at > > my > > syslog and saw t

Re: SA-Update cronjob output rejected by ISP for containing spam

On Sat, 22 Jun 2019, Chris Pollock wrote: I'm not sure how to exactly word the problem so the subject is the best I can do for now. Whenever a crojob is run a message is sent out via postfix to me with the contents of that cronjob. This morning when the SA-Update cronjob was run I d

Re: SA-Update cronjob output rejected by ISP for containing spam

Chris Pollock skrev den 2019-06-22 19:03: https://pastebin.com/hHR0Rvii accepted and bounced ? if yes fix that

SA-Update cronjob output rejected by ISP for containing spam

I'm not sure how to exactly word the problem so the subject is the best I can do for now. Whenever a crojob is run a message is sent out via postfix to me with the contents of that cronjob. This morning when the SA-Update cronjob was run I didn't receive the output back (this has bee

Re: How add ITA channel to sa-update?

On 3/26/19 9:05 AM, Alessio Cecchi wrote: > Hello, > > I'm interesting into add the italian channel to spamassassin from > https://spamassassin.snb.it/, but what is the right way? > > I download ITA.conf in /etc/spamassassin/channel.d/ and run sa-update but I > don&#

How add ITA channel to sa-update?

Hello, I'm interesting into add the italian channel to spamassassin from https://spamassassin.snb.it/, but what is the right way? I download ITA.conf in /etc/spamassassin/channel.d/ and run sa-update but I don't see any new files in /var/lib/spamassassin/3.004002/. Thanks (to Gi

Re: Problem with spamassassin update at /usr/bin/sa-update line 1603

On 2/22/2019 5:36 AM, mbaldov wrote: > So I ask you if it's possible to intervene on the mirror's list with > some option so that to exclude the bad mirrors. Escalating that issue to our sysadmins list.  Thanks for reporting the problem. -- Kevin A. McGrail Member, Apache Software Foundation Cha

Re: Problem with spamassassin update at /usr/bin/sa-update line 1603

he SA rules are not signatures as such. The core rules tend to be fairly generic, so missing an update here and there isn't that much of a problem - it's not like missing an antivirus update. If you have a problem with reliability there nothing to stop you running sa-update several times

Problem with spamassassin update at /usr/bin/sa-update line 1603

r/lib/spamassassin/3.004002/updates_spamassassin_org/1854020.tar.gz: No such file or directory at /usr/bin/sa-update line 1603." The problem isn't the file that clearly doesn't exist but some mirrors that it seems have problems when they are called. I have seen many post where they sp

Re: sa-update when were last updates made?

thanks for your info, sincerely, most helpful. I will look into my setup over the next week or so, as its clearly a bit weird! a few typos in my message, which I corrected - my old eyes are in need of an update too -- Sent from: http://spamassassin.1065346.n5.nabble.com/SpamAssassin-Users-f

Re: sa-update when were last updates made?

you're one release back. except for a directory sought_rules_yerp_org which is 18/10/2018 You should 'rm -rf sought_rules_yerp_org' because those rules are obsolete and unsafe. The sa-update channel for them will not work with v3.4.2 because the abandoned channel does not in

Re: sa-update when were last updates made?

On 24.01.19 06:44, LegendGamesMaster wrote: The files in /var/lib/spamassassin/3.0014000/ are clearly todays update, except for a directory sought_rules_yerp_org which is 18/10/2018 afaik this project is unfortunately dead I note that I have a load of files in /usr/share/spamassassin that are

Re: sa-update when were last updates made?

Reindl - thanks. just checked and yes, i'm updated. however... i'm confused as to what rules are being used in preference... The files in /var/lib/spamassassin/3.0014000/ are clearly todays update, except for a directory sought_rules_yerp_org which is 18/10/2018 I note that I have a load of fil

sa-update when were last updates made?

Hi Folks newbie here. centos / plesk, postfix, latest SA, run sa-update regularly My files are showing October 2018 as last update date - this seems a bit old to me. can anyone confirm the dates of the last updates? If im not getting them, I can delve deeper thanks in advance. Andy

Re: sa-update --allow-plugins [was: sa-update not properly parsing urls in MIRRORED.BY files?]

On Sat, Jan 12, 2019 at 02:10:37PM -0500, listsb wrote: > > that said, i don't quite follow the second statement, if i'm honest. i > suppose that some people may run sa-update or spamassassin as root, but i > don't, and would be filing bugs against any packagers

sa-update --allow-plugins [was: sa-update not properly parsing urls in MIRRORED.BY files?]

> On Jan 11, 2019, at 10.55, Henrik K wrote: > > On Wed, Jan 09, 2019 at 11:59:36PM -0500, listsb wrote: >> >>> sa-update -vvv --allowplugins ... > > Just a general note, I would never ever use --allowplugins unless it's your > personal channel. There is

Re: sa-update not properly parsing urls in MIRRORED.BY files?

Are you able to test with the 3.4 branch from svn? >> >> thanks. i've done a crude test just grabbing sa-update from svn, with some >> progress: >> >>> sa-update -v --allowplugins --channelfile >>> /etc/spamassassin/sa-update-conf.d/channels

Re: sa-update not properly parsing urls in MIRRORED.BY files?

hasn't been for years. Testing 282 simple but long body rules against every message is not free. The danger in the SOUGHT rules still being a part of SA 'lore' is that they are a bit of abandoned attack surface. It's still possible to download the tarball and forcibly instal

Re: sa-update not properly parsing urls in MIRRORED.BY files?

On Fri, 11 Jan 2019 10:22:13 -0500 Kris Deugau wrote: > Bill Cole wrote: > > On 10 Jan 2019, at 23:15, listsb wrote: > >> Update available for channel sought.rules.yerp.org: -1 -> > >> 3402014020421 > > > And finally: that rule channel has not been updated in almost 4 > > years and almost sur

Re: sa-update not properly parsing urls in MIRRORED.BY files?

On Wed, Jan 09, 2019 at 11:59:36PM -0500, listsb wrote: > > >sa-update -vvv --allowplugins ... Just a general note, I would never ever use --allowplugins unless it's your personal channel. There is no reason why official channels should ever distribute plugins as it would be ba

Re: sa-update not properly parsing urls in MIRRORED.BY files?

Bill Cole wrote: On 10 Jan 2019, at 23:15, listsb wrote: Update available for channel sought.rules.yerp.org: -1 -> 3402014020421 And finally: that rule channel has not been updated in almost 4 years and almost surely will never be updated again. I'm pretty sure it's been longer than that ev

Re: sa-update not properly parsing urls in MIRRORED.BY files?

ng sa-update from svn, with some progress: sa-update -v --allowplugins --channelfile /etc/spamassassin/sa-update-conf.d/channels.txt --gpgkeyfile /etc/spamassassin/sa-update-conf.d/sa-update-keys.txt --gpghomedir /var/lib/spamassassin/sa-update-keys Update available for channel sought.rules.yerp.or

Re: sa-update not properly parsing urls in MIRRORED.BY files?

listsb skrev den 2019-01-11 05:15: sa-update -v --allowplugins --channelfile /etc/spamassassin/sa-update-conf.d/channels.txt --gpgkeyfile /etc/spamassassin/sa-update-conf.d/sa-update-keys.txt --gpghomedir /var/lib/spamassassin/sa-update-keys Update available for channel sought.rules.yerp.org

Re: sa-update not properly parsing urls in MIRRORED.BY files?

On Jan 10, 2019, at 06.05, Kevin A. McGrail wrote: > > I believe this is a known issue fixed in svn. We need to get 3.4.3 out the > door for this. Are you able to test with the 3.4 branch from svn? thanks. i've done a crude test just grabbing sa-update from svn, with some

Re: sa-update not properly parsing urls in MIRRORED.BY files?

W dniu 2019-01-10 o 12:05, Kevin A. McGrail pisze: > I believe this is a known issue fixed in svn.  We need to get 3.4.3 out > the door for this.  Are you able to test with the 3.4 branch from svn? https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7623

Re: sa-update not properly parsing urls in MIRRORED.BY files?

m to have encountered after upgrading to 3.4.2. > > i have an additional channel defined [sought.rules.yerp.org], and updates > of this channel seem to have broken upon updating to 3.4.2: > > >sa-update -vvv --allowplugins --channelfile > /etc/spamassassin/sa-update-conf.d/channels.txt --

sa-update not properly parsing urls in MIRRORED.BY files?

hi- the subject expresses my uneducated hypothesis as to what might be causing a problem i seem to have encountered after upgrading to 3.4.2. i have an additional channel defined [sought.rules.yerp.org], and updates of this channel seem to have broken upon updating to 3.4.2: >sa-update -

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

On 21 Dec 2018, at 15:52, Bill Cole wrote: > cd `mktemp -d -t HappyMichael???` I'd prefer you did cd `mktemp -d -t saupdate` -- I gotta straighten my face This mellow-thighed chick just put my spine out of place

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

On 12/21/18 5:52 PM, Bill Cole wrote: Fine: #!/bin/sh cd `mktemp -d -t HappyMichael???` Yes, Merry Christmas =P

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

.gz curl -O http://sa-update.spamassassin.org/1849156.tar.gz.asc curl -O http://sa-update.spamassassin.org/1849156.tar.gz.sha245 curl -O http://sa-update.spamassassin.org/1849156.tar.gz.sha512 sa-update -D --install 1849156.tar.gz

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

On 12/20/18 7:00 PM, Bill Cole wrote: mkdir /tmp/saupdate-1849156 Never use a fixed path under /tmp =)

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

assassin.org/1849156.tar.gz.sha512 sa-update -D --install 1849156.tar.gz

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

which intentionally (!) masked the lint failure and allowed the broken rules package to be built and distributed. The file shouldn't get installed though because sa-update checks the lint, doesn't it? It depends on why the lint failed in the update process and on the local config. I

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

les package due to an ignored lint failure in a nightly update) over > the past few years. In addition to correcting the problematic rule I > have also fixed the script which intentionally (!) masked the lint > failure and allowed the broken rules package to be built and distributed. >

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

On 20 Dec 2018, at 13:41, Bill Cole wrote: This should now be fixed for the next rules update. And, On 20 Dec 2018, at 17:04, (ignoring an explicit Reply-To header in a direct message to me!) Frank Giesecke wrote: How can I force the rules update? You cannot. The "rules update" I referre

Re: sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

_24 >> >> channel: lint check of update failed, channel failed >> sa-update failed for unknown reasons >> -- > > seems not to be a problem of the EXCUSE_24 rule, but a general problem > with sa-update, as other users do have the same problem since today. This should now be fixed for the next rules update.

sa-update is broken on updates.spamassassin.org channel [was: Re: config: warning: description exists for non-existent rule EXCUSE_24]

Am Donnerstag, den 20.12.2018, 12:35 +0100 schrieb Marcus Schopen: > Hi, > > I get a warning, when updating the channel: > > -- > config: warning: description exists for non-existent rule EXCUSE_24 > > channel: lint check of update failed, channel failed > s

Re: [SA 3.4.2] sa-update doesn't see custom channel

W dniu 19.12.2018 o 16:16, Kris Deugau pisze: > RW wrote: >> It looks like sa-update has lost support for paths in mirror URLs. The >> SA mirrors don't currently have paths, but the commented-out dostech >> entry suggests that they have been supported in the past. >

Re: [SA 3.4.2] sa-update doesn't see custom channel

RW wrote: It looks like sa-update has lost support for paths in mirror URLs. The SA mirrors don't currently have paths, but the commented-out dostech entry suggests that they have been supported in the past. I came across this myself since my local channels also use subdirectories.

Re: [SA 3.4.2] sa-update doesn't see custom channel

On Wed, 19 Dec 2018 11:34:32 +0100 Marcin Mirosław wrote: > W dniu 03.12.2018 o 15:42, Marcin Mirosław pisze: > > Hi! > > I have problem with sa-update and my own channel. sa-update queries > > for A record of strange domain: > > > > # /usr/bin/sa-update -

Re: [SA 3.4.2] sa-update doesn't see custom channel

W dniu 03.12.2018 o 15:42, Marcin Mirosław pisze: > Hi! > I have problem with sa-update and my own channel. sa-update queries for > A record of strange domain: > > # /usr/bin/sa-update --channel sa.mejor.pl --no-gpg -vv > DNS TXT query: 2.4.3.sa.mejor.pl -> 3209 > Upda

Re: repeated sa-update problems

Hello, revoking old thread. I think I have found some of problems: 1. looking at old debug outputs, seems that everytime we've had problem, sa-update first tried to fetch from http://sa-update.spamassassin.org further fetching from other mirrors did not help, due to issues below. I feel

Re: sa-update error - config: invalid expression for rule T_MIXED_ES (fwd)

On 9 Dec 2018, at 12:50, Kevin Walton wrote: Hi I am running: SpamAssassin version 3.3.2 sa-update version svn917659 This is an unsupported obsolete version of SpamAssassin. If you are maintaining your own installation, you should update. If you are using a distribution maintained by

sa-update error - config: invalid expression for rule T_MIXED_ES (fwd)

Hi I am running: SpamAssassin version 3.3.2 sa-update version svn917659 and I have been getting the following error for the last couple of days now when cron runs sa-update: " config: invalid expression for rule T_MIXED_ES: "( __LOWER_E > 20 ) && ( __E_LIKE_LETTE

[SA 3.4.2] sa-update doesn't see custom channel

Hi! I have problem with sa-update and my own channel. sa-update queries for A record of strange domain: # /usr/bin/sa-update --channel sa.mejor.pl --no-gpg -vv DNS TXT query: 2.4.3.sa.mejor.pl -> 3209 Update available for channel sa.mejor.pl: -1 -> 3209 DNS A query update.sa.mejor.pl/sa-u

Re: Error running sa-update - cannot refresh mirrors file

again. I tried running the curl command suggested above, and it appeared to complete successfully. I then ran sa-update, and got the error message. root@mailpi ~ # curl --verbose -L -O --remote-time -g --max-redirs 2 -- connect-timeout 30 --max-time 300 http://spamassassin.

Re: Error running sa-update - cannot refresh mirrors file

On Friday, 2 November 2018 3:45:08 ACDT RW wrote: > On Wed, 31 Oct 2018 22:59:55 +1030 > > Rodney Baker wrote: > > On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote: > > > curl --verbose -L -O --remote-time -g --max-redirs 2 > > > --connect-timeout 30 --max-time 300 > > > http://spamassassin.apa

Re: Error running sa-update - cannot refresh mirrors file

On Wed, 31 Oct 2018 22:59:55 +1030 Rodney Baker wrote: > On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote: > > curl --verbose -L -O --remote-time -g --max-redirs 2 > > --connect-timeout 30 --max-time 300 > > http://spamassassin.apache.org/updates/MIRRORED.BY > > Here's the output from that

Re: Error running sa-update - cannot refresh mirrors file

On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote: > On Mon, 29 Oct 2018 09:07:09 -0400 > > Kevin A. McGrail wrote: > > On 10/29/2018 8:03 AM, Rodney Baker wrote: > > > re: renaming curl and using wget > > > > > > Thanks. Did that - it worked with wget instead of curl, successfully > > > downlo

Re: Error running sa-update - cannot refresh mirrors file

On Wednesday, 31 October 2018 7:29:51 ACDT RW wrote: > On Mon, 29 Oct 2018 09:07:09 -0400 > > Kevin A. McGrail wrote: > > On 10/29/2018 8:03 AM, Rodney Baker wrote: > > > re: renaming curl and using wget > > > > > > Thanks. Did that - it worked with wget instead of curl, successfully > > > downlo

Re: Error running sa-update - cannot refresh mirrors file

On Mon, 29 Oct 2018 09:07:09 -0400 Kevin A. McGrail wrote: > On 10/29/2018 8:03 AM, Rodney Baker wrote: > > re: renaming curl and using wget > > > Thanks. Did that - it worked with wget instead of curl, successfully > > downloading the mirrors file and all updates. The last failure with > > cur

Re: Error running sa-update - cannot refresh mirrors file

On 10/29/2018 8:03 AM, Rodney Baker wrote: > re: renaming curl and using wget > Thanks. Did that - it worked with wget instead of curl, successfully > downloading the mirrors file and all updates. The last failure with > curl was last night. > Then you are likely caught up in the buggy curl we've

Re: Error running sa-update - cannot refresh mirrors file

On 29/10/2018 1:47, RW wrote: On Sun, 28 Oct 2018 21:34:33 +1030 Rodney Baker wrote: On Saturday, 27 October 2018 0:14:32 ACDT Kevin A. McGrail wrote: It does concern me that it can't pull the file. I had added an https redirect which broke a lot of places using a broken version of curl. Ac

Re: Error running sa-update - cannot refresh mirrors file

On Sun, 28 Oct 2018 21:34:33 +1030 Rodney Baker wrote: > On Saturday, 27 October 2018 0:14:32 ACDT Kevin A. McGrail wrote: > > > > It does concern me that it can't pull the file. I had added an > > https redirect which broke a lot of places using a broken version > > of curl. According to bug

Re: Error running sa-update - cannot refresh mirrors file

ould I be concerned about the error updating the mirrors file? > >> > >> No. sa-update tries to update it after a week so you pick-up new > >> servers and spread the load, but the old one will probably still be > >> usable for years. > >> > >>

Re: Error running sa-update - cannot refresh mirrors file

On Friday, 26 October 2018 23:46:18 ACDT RW wrote: > On Fri, 26 Oct 2018 22:40:54 +1030 > > Rodney Baker wrote: > > Should I be concerned about the error updating the mirrors file? > > No. sa-update tries to update it after a week so you pick-up new > servers and spread t

Re: Error running sa-update - cannot refresh mirrors file

On Fri, 26 Oct 2018 22:40:54 +1030 Rodney Baker wrote: > Should I be concerned about the error updating the mirrors file? No. sa-update tries to update it after a week so you pick-up new servers and spread the load, but the old one will probably still be usable for years. The only time

Error running sa-update - cannot refresh mirrors file

Hi all, I'm getting the following error when running sa-update on my Raspberry Pi (running spamc/spamd with compiled rulesets); root@mailpi ~ # sa-update --verbose Update available for channel updates.spamassassin.org: 1844624 -> 1844740 http: (curl) GET http://spamassassin.apache.org

Re: sa-compile after sa-update

An RH bug was opened and closed on this in 2014: https://bugzilla.redhat.com/show_bug.cgi?id=1151565 I attached a patch to the bug for the latest sa-update.cron script from the 3.4.2 RPM to invoke sa-compile if the plugin is enabled and re2c is installed.

sa-compile after sa-update

I'm experimenting with the Rule2XSBody plugin and I've figured out that I have to run sa-compile after sa-update to create the compiled versions of local rules. I don't see anything in either sa-update or the Red Hat-supplied sa-update.cronscript invoked from cron (or a syste

Re: repeated sa-update problems

On 20.09.18 16:05, Matus UHLAR - fantomas wrote: I looked at update times and they are different each day - debian script sleeps random number of seconds (up to one hour) in order to lower the impact at mirror servers. I have removed the "--fail" option from curl and will look at error message i

Re: sa-update and signature verification

wrote: > Hello, > > since updating to 3.4.2 I can't download rules from unofficial > channels. The problem is that in version 3.4.1 sa-update checks the > hash of the downloaded file using file.sha1 , while version 3.4.2 uses > file.sha256 or file.sha512. See the rele

sa-update and signature verification

Hello, since updating to 3.4.2 I can't download rules from unofficial channels. The problem is that in version 3.4.1 sa-update checks the hash of the downloaded file using file.sha1 , while version 3.4.2 uses file.sha256 or file.sha512. See the relevant differences in the following sa-u

Re: repeated sa-update problems

On 9/20/2018 8:59 AM, Dave Jones wrote: I will have to check later if someone else can't check today.  I am at a customer location where I don't have good VPN connection out and will be traveling this evening.  I can check tomorrow if it can wait. On 20.09.18 09:05, Kevin A. McGrail wrote: It

  1   2   3   4   5   6   7   8   9   10   >