As of Thurs. Mar 11, I've been getting the following message from the sa-update job for SpamAssassin
What I've read in posts from around 2014 is that the fix is to comment out this mirror as it is no longer updated?
If this is the case, then why did this error show up 4 days ago? Was there an update which enabled reading from the dead mirror?
Thanks in advance for the clarification.
channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
11-Mar-2021 05:56:28: SpamAssassin: Unknown error code 3 from sa-update
What I've read in posts from around 2014 is that the fix is to comment out this mirror as it is no longer updated?
If this is the case, then why did this error show up 4 days ago? Was there an update which enabled reading from the dead mirror?
Thanks in advance for the clarification.
Share this post:
Responses (13)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
This is a PITA. Redhat state:
RHEL-7 is already in Maintenance Support 2 phase, which means that only Critical impact Security Advisories and selected Urgent Priority Bug Fix Advisories may be addressed. Please see https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase for further information.
So it is no going to be fixed upstream. I'll see if I can do something with app-mail-antispam to comment out the the two lines:
Since this bug does not meet the criteria, we'll close it as WONTFIX. Feel free to discuss this Bug with (Product Management)/Support Representative, if this is a critical issue for the customer/for you. Please provide business justification in such case.
in /etc/mail/spamassassin/channel.d/sought.conf, or just delete the file. I'll have to have a play before we can release anything.CHANNELURL=sought.rules.yerp.org
KEYID=6C6191E3 -
Accepted Answer
Temporary fix
Edit "/etc/mail/spamassassin/channel.d/sought.conf"
# http://wiki.apache.org/spamassassin/SoughtRules
#CHANNELURL=sought.rules.yerp.org
#KEYID=6C6191E3
# Ignore everything below.
return 0
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
As the package update is low risk, I am releasing it now. I have tested it on a few systems.
Thanks Nick for the quick fix and support!
---edit added---
Shouldn't we be running a cron job daily for spamassassin? I can't see how it would be checking and updating the filter.
sa-update && service spamassassin restart
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
It is currently syncing to the repos, but I have an updated app-mail-filter-core which will comment out the two lines:
yum update app-mail-filter-core --enablerepo=clearos-updates-testing
Nick,
I've not seen the update and when i try to force the update manually in putty with above command I'm not getting the update. -
Accepted Answer
Patrick de Brabander wrote:
You won't see now it with that command as i released it to the community and you don't have the community repos. Try:
Nick Howitt wrote:
It is currently syncing to the repos, but I have an updated app-mail-filter-core which will comment out the two lines:
yum update app-mail-filter-core --enablerepo=clearos-updates-testing
Nick,
I've not seen the update and when i try to force the update manually in putty with above command I'm not getting the update.
I'll release it to the paid repos next week.yum update app-mail-filter-core --enablerepo=clearos-updates
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »