Forums

nuke
nuke
Offline
Resolved
0 votes
As of Thurs. Mar 11, I've been getting the following message from the sa-update job for SpamAssassin

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.
Sunday, March 14 2021, 08:04 PM
Share this post:
Responses (13)
  • Accepted Answer

    Sunday, March 14 2021, 09:19 PM - #Permalink
    Resolved
    0 votes
    There has been no update from us. I know the SA mirrors sometimes have issues and I am hoping this one will pass. I'll ask if the configs come from the clearsdn-antispam updates.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, March 16 2021, 05:50 PM - #Permalink
    Resolved
    0 votes
    I’m having the same message every day since a few days.
    Nothing has been changed in my setup
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, March 16 2021, 08:58 PM - #Permalink
    Resolved
    0 votes
    It is annoying as no package owns the files, so then my suspicion is it is sa-update, but where is it getting its configuration from. We use a vanilla upstream package so don't recompile it or anything.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, March 17 2021, 03:06 PM - #Permalink
    Resolved
    0 votes
    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.

    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.
    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:
    CHANNELURL=sought.rules.yerp.org
    KEYID=6C6191E3
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Georgina
    Georgina
    Offline
    Wednesday, March 17 2021, 10:20 PM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 18 2021, 11:00 AM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 18 2021, 04:11 PM - #Permalink
    Resolved
    -1 votes
    As the package update is low risk, I am releasing it now. I have tested it on a few systems.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 18 2021, 05:55 PM - #Permalink
    Resolved
    0 votes
    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 swift fix.
    The reply is currently minimized Show
  • Accepted Answer

    nuke
    nuke
    Offline
    Friday, March 19 2021, 01:04 AM - #Permalink
    Resolved
    0 votes
    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
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 19 2021, 08:14 AM - #Permalink
    Resolved
    0 votes
    nuke wrote:
    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

    We are. Have a look at /etc/cron.d/sa-update.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 19 2021, 04:02 PM - #Permalink
    Resolved
    0 votes
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 19 2021, 04:07 PM - #Permalink
    Resolved
    0 votes
    Patrick de Brabander wrote:

    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.
    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:
    yum update app-mail-filter-core --enablerepo=clearos-updates
    I'll release it to the paid repos next week.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 19 2021, 04:48 PM - #Permalink
    Resolved
    0 votes
    Thanks. I thought it was still in the testing repos ;)
    The reply is currently minimized Show
Your Reply