Error no mirror data available for channel updates spamassassin org - Исправление ошибок и поиск оптимальных решений проблем

13.09.2013, 15:17

#1

Member

Cron Daemon и spamassassin

Приходит каждый день

channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
channel: no ‘mirrors.updates.spamassassin.org’ record found, channel failed

Как исправить ?

CentOS 6.3

Последний раз редактировалось russists; 13.09.2013 в 18:15.
14.09.2013, 22:13

#2

ISPsystem team

От вас mirrors.sought.rules.yerp.org доступен? В ip адрес разрешается?
14.09.2013, 23:10

#3

Member

Сообщение от Fly

От вас mirrors.sought.rules.yerp.org доступен? В ip адрес разрешается?

Как проверить ?
16.09.2013, 00:53

#4

Member

Неужели не кто не знает ?
16.09.2013, 10:36

#5

ISPsystem team

Зайдите на сервер по ssh и выполните команду:
dig mirrors.sought.rules.yerp.org
16.09.2013, 12:42

#6

Member

Сообщение от Olya

Зайдите на сервер по ssh и выполните команду:
dig mirrors.sought.rules.yerp.org

# dig mirrors.sought.rules.yerp.org

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> mirrors.sought.rules.yerp.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48670
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mirrors.sought.rules.yerp.org. IN A

;; AUTHORITY SECTION:
yerp.org. 300 IN SOA ns.taint.org. jm.jmason.org. 2013091611 3600 3600 604800 300

;; Query time: 255 msec
;; SERVER: 213.85.204.190#53(213.85.204.190)
;; WHEN: Mon Sep 16 07:38:27 2013
;; MSG SIZE rcvd: 102
16.09.2013, 13:33

#7

ISPsystem team

Информация о доменах mirrors.sought.rules.yerp.org и mirrors.updates.spamassassin.org не отдается с серверов имен. Это проблема на стороне spamassassin. Попробуйте обратиться к ним, пожалуйста.

Should I be worried about the below message ?

/etc/cron.daily/sa_update:


channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed

Kindest regards
Taco

Logged

twijtzes

AFAIUI these are temporary «glitches»

Watch for any future messages though.

Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Hi Janet,

These Cron messages appear daily, therefore I tried to find similar issues on the forum or in the bugs list. So far I have not been able to find these messages on the forums, so I think it might be a local thing. If this is an issue with more users, we might need something more drastic.

As my system is updated from version 7, it might have something to do with that. I will set up a fresh SME server to see if the problem persists. If so, I will raise a bug.

Regards,
Taco

« Last Edit: January 07, 2014, 09:06:08 AM by twijtzes »

Logged

twijtzes

A Google search on the second error message found

Bug 7661
&
http://spamassassin.1065346.n5.nabble.com/sought-rules-yerp-org-site-down-td59535.html

As I said these are likely to be temporary problems, DNS related.

Have you specified a particular DNS server or do you have other problems with your ISP ?

I would not waste your time building another server, just change the DNS server you are using (if you can), or delete it from sme server if one is specified, or complain to your ISP

Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

In case it helps, on my system, the files below have the content indicated:

#!/bin/bash # Only restart spamd if sa-update returns 0, meaning it updated the rules export HOME=/var/lib/spamassassin cd $HOME (/usr/bin/sa-update --gpgkeyfile /etc/mail/spamassassin/gpgkeys --channelfile /etc/mail/spamassassin/channels && service spamassassin condrestart > /dev/null) 2>&1 | tee -a /var/log/sa-update.log

updates.spamassassin.org sought.rules.yerp.org

26C900A46DD40CD5AD24F6D7DEE01987265FA05B D8099BC79E17D7E49BC21E31FDE52F40F7D39814 5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 8D25B5E91DAF0F715F60B588DC85341F6C6191E3

And here’s what I get when I run sa-update manually (the bin, not the cronjob):

# HOME=/var/lib/spamassassin # cd $HOME # /usr/bin/sa-update --gpgkeyfile /etc/mail/spamassassin/gpgkeys --channelfile /etc/mail/spamassassin/channels -v Update finished, no fresh updates were available

Logged

Thanks,

If it has to do with DNS, I have a clue where to begin. It will probably have to do with a new network router and double ADSL connection over here, does spam assassin update require additional ports to be opened ?

Logged

recommendation
I think you need to edit this file:
/etc/mail/spamassassin/channels

And make it match mine (see my first post, or take ‘mirrors.’ out of each hostname). There is no associated template, so you need to edit the file directly.

Whether this works or not, there is stil a question of how/why your spamassassin channel file acquired incorrect settings.

background
I re-ran the manual update this morning from my previous post:

HOME=/var/lib/spamassassin cd $HOME /usr/bin/sa-update --gpgkeyfile /etc/mail/spamassassin/gpgkeys --channelfile /etc/mail/spamassassin/channels -v
Today I get this result (convincing me that my system is successfully finding the update channels):

Update available for channel sought.rules.yerp.org
Update was available, and was downloaded and installed successfully

Since I couldn’t find any A record using nslookup for ‘sought.rules.yerp.org’ or ‘updates.spamassassin.org’, I looked up exactly how spamassassin looks for updates:
http://wiki.apache.org/spamassassin/PublishingRuleUpdates

According to that page, sa-update reverses the spamassassin version number and prepends the result to each «channel» supplied when the command is run.

On my system, the channels (from —channelfile /etc/mail/spamassassin/channels) are:

updates.spamassassin.org
sought.rules.yerp.org

…and my spamassassin version (from

spamassassin -V

) is 3.3.2

… so sa-update is looking for the latest rules version using:

# nslookup -type=txt 2.3.3.updates.spamassassin.org
Server:      …
Address:   …#53

Non-authoritative answer:
2.3.3.updates.spamassassin.org   text = «1556147»

# nslookup -type=txt 2.3.3.sought.rules.yerp.org
Server:      …
Address:   …#53

Non-authoritative answer:
2.3.3.sought.rules.yerp.org   text = «3302014010811»

However, when I try to look for versions using the hostnames you seem to have on your system, I get:

# nslookup -type=txt 2.3.3.mirrors.updates.spamassassin.org
Server:      …
Address:   …#53

** server can’t find 2.3.3.mirrors.updates.spamassassin.org: NXDOMAIN

[root@office ~]# nslookup -type=txt 2.3.3.mirrors.sought.rules.yerp.org
Server:      …
Address:   …#53

** server can’t find 2.3.3.mirrors.sought.rules.yerp.org: NXDOMAIN

Logged

twijtzes

As my system is updated from version 7….

I wonder if your system is updating correctly, & whether the repos are set correctly.
Show output of
/sbin/e-smith/audittools/repositories

Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Hi Janet,

below please find the output of /sbin/e-smith/audittools/repositories

addons: disabled
base: enabled
centos-testing: disabled
centosplus: disabled
contrib: disabled
extras: disabled
smeaddons: enabled
smecontribs: disabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: enabled
updates: enabled

« Last Edit: January 19, 2014, 03:14:13 PM by twijtzes »

Logged

twijtzes

smeupdates-testing: enabled

That repo should normally be disabled.
You may have rpms installed that are still under test & not ready for release, & could still be buggy.

The db setting for that repo should be

db yum_repositories show smeupdates-testing

smeupdates-testing=repository
EnableGroups=yes
GPGCheck=yes
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeupdates-testing-8
Name=SME Server — updates testing
Visible=yes
status=disabled

To fix yours do
db yum_repositories setprop smeupdates-testing status disabled
signal-event yum-modify

See
http://wiki.contribs.org/SME_Server:Documentation:FAQ:Section01#Which_repositories_should_be_enabled

Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Источник

Ubuntu 14.04 Spamassassin Issue

Hi

I have a clean install of Ubuntu server 14.04 but get an error when trying to enable spamassassin. I have installed 3 times to make sure its nothing i am doing. I do the install then upgrade and dist-upgrade so i know i have a fully up to date system then install virtualmin. when you install virtualmin you see 1 error :- no mirror data available for channel updates.spamassassin.org channel: MIRRORED.BY file URL was not in DNS, channel failed when you try to start spamassassin from virtualmin you get:-

Starting SpamAssassin server ..
.. failed to start : Starting SpamAssassin Mail Filter Daemon: child process [3828] exited or timed out without signaling production of a PID file: exit 255 at /usr/sbin/spamd line 2960.

I have done a little digging on the net and tried:-

> rpm -qa | grep spam
sh: 1: rpm: not found

> sa-update
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY file URL was not in DNS, channel failed

> /etc/init.d/spamassassin start
Starting SpamAssassin Mail Filter Daemon: child process [4173] exited or timed out without signaling production of a PID file: exit 255 at /usr/sbin/spamd line 2960.

> /etc/init.d/spamd start
sh: 1: /etc/init.d/spamd: not found

> apt-get install —purge spamassassin
Reading package lists…
Building dependency tree…
Reading state information…
spamassassin is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

> apt-get install spamassassin
Reading package lists…
Building dependency tree…
Reading state information…
spamassassin is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

> sa-update —no-gpg
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY file URL was not in DNS, channel failed

> host updates.spamassassin.org
Host updates.spamassassin.org not found: 3(NXDOMAIN)

> cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND — YOUR CHANGES WILL BE OVERWRITTEN
nameserver 8.8.8.8
nameserver 127.0.0.1
search myserver.co.uk
It looks like a permissions issue?? any help would be appresiated

Colin

Источник

Description

Marty Phelan

2014-08-14 17:20:20 UTC

Cannot perform sa-update for system. Noticed because daily cron job sent warning email:

/etc/cron.daily/spamassassin:
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY file contents were missing, channel failed
sa-update failed for unknown reasons

Environment:
Ubuntu 14.04 (up-to-date)
Spamassassin 3.4.0

tried running sa-update as debian-spamd:
debian-spamd@venus:~$ sa-update --gpghomedir /var/lib/spamassassin/sa-update-keys -D
Output (abbrievated):
...
Aug 14 09:09:42.989 [10281] dbg: channel: no mirror file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, will fetch it
Aug 14 09:09:42.989 [10281] dbg: channel: DNS lookup on mirrors.updates.spamassassin.org
Aug 14 09:09:42.990 [10281] dbg: http: url: http://spamassassin.apache.org/updates/MIRRORED.BY
Aug 14 09:09:42.990 [10281] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, new
Aug 14 09:09:42.990 [10281] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:09:42.990 [10281] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY
Aug 14 09:09:42.996 [10281] dbg: http: process [10282], exit status: 13
Aug 14 09:09:42.996 [10281] dbg: channel: no mirror data available for channel updates.spamassassin.org from http://spamassassin.apache.org/updates/MIRRORED.BY
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY file contents were missing, channel failed
Aug 14 09:09:42.996 [10281] dbg: generic: cleaning up temporary directory/files
Aug 14 09:09:42.996 [10281] dbg: generic: cleaning directory /tmp/.spamassassin10281OjrLbxtmp
Aug 14 09:09:42.996 [10281] dbg: diag: updates complete, exiting with code 4

Manually ran curl command successfully:
cd /var/lib/spamassassin/3.004000/updates_spamassassin_org
/usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY

Then tried sa-update again and got:
...
Aug 14 09:17:03.564 [10396] dbg: channel: file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY is too old, refreshing mirrors file
Aug 14 09:17:03.564 [10396] dbg: channel: DNS lookup on mirrors.updates.spamassassin.org
Aug 14 09:17:03.565 [10396] dbg: http: url: http://spamassassin.apache.org/updates/MIRRORED.BY
Aug 14 09:17:03.565 [10396] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, replace
Aug 14 09:17:03.565 [10396] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:17:03.565 [10396] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY
Aug 14 09:17:03.571 [10396] dbg: http: process [10397], exit status: 13
Aug 14 09:17:03.571 [10396] dbg: channel: no mirror data available for channel updates.spamassassin.org from http://spamassassin.apache.org/updates/MIRRORED.BY
error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
Aug 14 09:17:03.571 [10396] dbg: channel: reading MIRRORED.BY file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY
Aug 14 09:17:03.571 [10396] dbg: channel: parsing MIRRORED.BY file for channel updates.spamassassin.org
Aug 14 09:17:03.571 [10396] dbg: channel: found mirror http://sa-update.dnswl.org/ weight=1
Aug 14 09:17:03.571 [10396] dbg: channel: found mirror http://www.sa-update.pccc.com/ weight=5
Aug 14 09:17:03.572 [10396] dbg: channel: found mirror http://sa-update.secnap.net/ weight=5
Aug 14 09:17:03.572 [10396] dbg: channel: found mirror http://sa-update.space-pro.be/ weight=1
Aug 14 09:17:03.572 [10396] dbg: channel: selected mirror http://sa-update.secnap.net
Aug 14 09:17:03.572 [10396] dbg: http: url: http://sa-update.secnap.net/1613764.tar.gz
Aug 14 09:17:03.572 [10396] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1613764.tar.gz, new
Aug 14 09:17:03.572 [10396] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:17:03.572 [10396] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1613764.tar.gz -- http://sa-update.secnap.net/1613764.tar.gz
Aug 14 09:17:03.578 [10396] dbg: http: process [10398], exit status: 13
Aug 14 09:17:03.578 [10396] dbg: channel: selected mirror http://sa-update.dnswl.org
Aug 14 09:17:03.578 [10396] dbg: http: url: http://sa-update.dnswl.org/1613764.tar.gz
Aug 14 09:17:03.578 [10396] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1613764.tar.gz, new
Aug 14 09:17:03.578 [10396] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:17:03.578 [10396] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1613764.tar.gz -- http://sa-update.dnswl.org/1613764.tar.gz
Aug 14 09:17:03.583 [10396] dbg: http: process [10399], exit status: 13
Aug 14 09:17:03.583 [10396] dbg: channel: selected mirror http://www.sa-update.pccc.com
Aug 14 09:17:03.583 [10396] dbg: http: url: http://www.sa-update.pccc.com/1613764.tar.gz
Aug 14 09:17:03.583 [10396] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1613764.tar.gz, new
Aug 14 09:17:03.584 [10396] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:17:03.584 [10396] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1613764.tar.gz -- http://www.sa-update.pccc.com/1613764.tar.gz
Aug 14 09:17:03.588 [10396] dbg: http: process [10400], exit status: 13
Aug 14 09:17:03.589 [10396] dbg: channel: selected mirror http://sa-update.space-pro.be
Aug 14 09:17:03.589 [10396] dbg: http: url: http://sa-update.space-pro.be/1613764.tar.gz
Aug 14 09:17:03.589 [10396] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1613764.tar.gz, new
Aug 14 09:17:03.589 [10396] dbg: util: executable for curl was found at /usr/bin/curl
Aug 14 09:17:03.589 [10396] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1613764.tar.gz -- http://sa-update.space-pro.be/1613764.tar.gz
Aug 14 09:17:03.595 [10396] dbg: http: process [10401], exit status: 13
channel: could not find working mirror, channel failed
Aug 14 09:17:03.596 [10396] dbg: generic: cleaning up temporary directory/files
Aug 14 09:17:03.596 [10396] dbg: generic: cleaning directory /tmp/.spamassassin10396koqaqjtmp
Aug 14 09:17:03.596 [10396] dbg: diag: updates complete, exiting with code 4

Appears that running curl within sa-update is failing for some reason.

Result is: cannot update spamassassin rules.

Comment 1

Mark Martinec

2014-08-14 17:46:17 UTC

exit status: 13
13) SIGPIPE

Try running the same command manually:

  /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY

It is perhaps writing anything to stdout? (it shouldn't, should just produce
the file MIRRORED.BY in a currect directory).

Does sa-update work correctly when running interactively, but fails in cron?

Comment 2

Karsten Bräckelmann

2014-08-14 21:33:17 UTC

(In reply to Marty Phelan from comment #0)
> Aug 14 09:09:42.990 [10281] dbg: http: /usr/bin/curl -s -L -O --remote-time
> -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY
> -- http://spamassassin.apache.org/updates/MIRRORED.BY
> Aug 14 09:09:42.996 [10281] dbg: http: process [10282], exit status: 13

(In reply to Mark Martinec from comment #1)
> 13) SIGPIPE

That's the external 'curl' process's exit status, not a signal. From the curl man page, section Exit Codes:

  13  FTP  weird PASV reply, Curl couldn't parse the reply sent to the
      PASV request.

Why does curl return an FTP related exit code for an HTTP request?


(In reply to Marty Phelan from comment #0)
> Manually ran curl command successfully:

What user did you do the manual curl command as?

I note that all 6 curl calls done by sa-update fail. The one manual invocation succeeds.

Comment 3

Mark Martinec

2014-08-14 23:08:36 UTC

> (In reply to Mark Martinec from comment #1)
> > 13) SIGPIPE
> 
> That's the external 'curl' process's exit status, not a signal. From the
> curl man page, section Exit Codes:

Unfortunately not so. The process exit status as reported by sa-update
is sloppy, it shows the complete '$?' which is a complete 16-bit
process exit status (the low byte is a signal, the high byte is a
proper exit status code if process exited and not signalled).
It should have been processed through WTERMSIG by
Mail::SpamAssassin::Util::exit_status_str(), but sa-update hasn't
been converted yet to use that and be more human-friendly.

Comment 4

Karsten Bräckelmann

2014-08-14 23:25:35 UTC

(In reply to Mark Martinec from comment #3)
> Unfortunately not so. The process exit status as reported by sa-update
> is sloppy, it shows the complete '$?' which is a complete 16-bit
> process exit status (the low byte is a signal, the high byte is a
> proper exit status code if process exited and not signalled).

Ugh, I see. Thanks, Mark.

Marty, please disregard the first part of comment 2.

Comment 5

Marty Phelan

2014-08-15 01:56:45 UTC

In reply to Comment #2:

>Try running the same command manually:
>/usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY
>It is perhaps writing anything to stdout? 
NO
 
>(it shouldn't, should just produce the file MIRRORED.BY in a currect directory). 
CORRECT. It did create file MIRRORED.BY

>Does sa-update work correctly when running interactively, 
NO. sa-update does NOT work interactively. With the -D option it produced the output shown in original bug report (line 13 on).

>but fails in cron?
YES. Also fails in cron. Emails error message:
error: no mirror data available for channel updates.spamassassin.org
channel: MIRRORED.BY file contents were missing, channel failed
sa-update failed for unknown reasons

Comment 7

Mark Martinec

2014-09-30 12:23:19 UTC

Bug 7074, sa-update: improved error reporting of a failed spawned process
  Sending sa-update.raw
Committed revision 1628417.


Note that this only improves error reporting.

The original reported problem remains a mystery.
Apparently others are unable to reproduce a SIGPIPE failure in curl.

Comment 8

Mark Martinec

2014-09-30 14:08:37 UTC

Apparently a bug in curl, fixed on 2014-05-05 :

curl-7.38.0 / CHANGES:

Daniel Stenberg (5 May 2014)
- [Jeff King brought this change]

  curl_multi_cleanup: ignore SIGPIPE better

  When looping and closing each individual connection left open, the
  SIGPIPE ignoring was not done and could thus lead to death by signal 13.

  Bug: http://thread.gmane.org/gmane.comp.version-control.git/238242

Comment 9

Kevin A. McGrail

2014-09-30 14:19:46 UTC

Good find!  Marking as invalid since it's a bug in curl.

Источник

Topic: Daily Spamassassin update reports error (Read 7569 times)

0 Members and 1 Guest are viewing this topic.

Hi, seems the spamassassin source in the script is offline.

I see we have Version 3.4.0 but there is already 3.4.4 or 3.4.5 out

i get the daily mails from the update report and it tells me:

channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed 13-M�r-2021 06:08:30: SpamAssassin: Unknown error code 3 from sa-update
Any way to fix this, i know we can play around and manually install and update spamassassin but i don’t think this is what we should do, maybe there is a reason for the old version in the repo.

Maybe this could be fixed/updated in one of the CWP updates we get.

Thanks

Logged

Offline

i have the same issue since 5 days or so

channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
14-Mar-2021 04:52:56: SpamAssassin: Unknown error code 3 from sa-update

running centos 7 with latests updates.

« Last Edit: March 14, 2021, 02:11:22 PM by Dutch_Mike »

Logged

Hi, I would disable the mirror in the config in /etc/mail/spamassassin/

Logged

Ok thanks, i will give it a try.

Logged

Offline

Hi, I would disable the mirror in the config in /etc/mail/spamassassin/

Hello, is that the only fix right now? Would that somehow mess up the spamassassin updates after disabling the mirror?

Logged

The problem has arisen because CWP uses an outdated version of Spamassasin. The Sought server pulled all updates for this old version, as they no longer support it. CWP needs to update to the latest version of SA to correct this error. The only option to disable the errors at this point, is to delete the mirror.

Logged

Offline

Spamassassin in CWP is v3.4.0?
According to this:
https://spamassassin.apache.org/news.html
3.4.0 was released on 2014!!!

Why CWP don’t update this things? I mean, 7 years has passed….
And I can see that Postfix is old, too.

Uh….

Logged

Источник

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" /> Cron Daemon и spamassassin

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon5.png" alt="Question" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ispsystem.ru/images/icons/icon1.png" alt="По умолчанию" />

Ubuntu 14.04 Spamassassin Issue

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.centos-webpanel.com/Themes/cwp2/images/topic/normal_post.gif" alt /> Topic: Daily Spamassassin update reports error (Read 7569 times)

Cron Daemon и spamassassin

Topic: Daily Spamassassin update reports error (Read 7569 times)