On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

SpamAssassin fails to update on a Plesk server: no 'mirrors.sought.rules.yerp.org' record found, channel failed

Follow

Comments

13 comments

  • Avatar
    Marco

    commenting

    return 0

    will result in these errors:

    /etc/mail/spamassassin/channel.d/sought.conf: line 7: -----BEGIN: command not found

    /etc/mail/spamassassin/channel.d/sought.conf: line 8: syntax error near unexpected token `('

    /etc/mail/spamassassin/channel.d/sought.conf: line 8: `Version: GnuPG v1.4.1 (GNU/Linux)'

    1
    Comment actions Permalink
  • Avatar
    IWA

    Same errors as Marco after commenting out

    #CHANNELURL=sought.rules.yerp.org
    #KEYID=6C6191E3
    #return 0

     

    /etc/mail/spamassassin/channel.d/sought.conf: line 7: -----BEGIN: command not found

    /etc/mail/spamassassin/channel.d/sought.conf: line 8: syntax error near unexpected token `('

    /etc/mail/spamassassin/channel.d/sought.conf: line 8: `Version: GnuPG v1.4.1 (GNU/Linux)'

     

    0
    Comment actions Permalink
  • Avatar
    pauls (Edited )

    Indeed this is not fixed, still getting cron update with this message, like Marco first posted:

     

    /etc/mail/spamassassin/channel.d/sought.conf: line 7: -----BEGIN: command not found
    /etc/mail/spamassassin/channel.d/sought.conf: line 8: syntax error near unexpected token `('
    /etc/mail/spamassassin/channel.d/sought.conf: line 8: `Version: GnuPG v1.4.1 (GNU/Linux)'

     

    doing

    sa-update -v

    Update available for channel updates.spamassassin.org: 1887567 -> 1887624
    http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, success
    http: (curl) GET http://www.sa-update.pccc.com/1887624.tar.gz, success
    http: (curl) GET http://www.sa-update.pccc.com/1887624.tar.gz.sha512, success
    http: (curl) GET http://www.sa-update.pccc.com/1887624.tar.gz.asc, success
    Update was available, and was downloaded and installed successfully

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    Thanks for your comments, the article has been modified accordingly.

    0
    Comment actions Permalink
  • Avatar
    Spinnerz

    Hello,

    Maybe I'm missing something? But I don't see any changes in the article...

    I did the commenting of the files on my servers (yesterday)  but received the same emails this morning.

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    @Spinnerz
    The 'return 0' line should not be commented out. The 1st and the 4th lines are usually already commented out. If the issue still persists, you can submit a ticket to Plesk Support.

    1
    Comment actions Permalink
  • Avatar
    IWA

    @Leonid Gukhman

    Thank you for your update!

     

    0
    Comment actions Permalink
  • Avatar
    spamfaenger (Edited )

    It seems this article is missing this after the edit to actually activate it.

    service spamassassin restart
    0
    Comment actions Permalink
  • Avatar
    Jeffrey Kastner

    Updated to Plesk Obsidian 18.0.34 Update #2, but this issue persists

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    spamfaenger

    Restarting SpamAssassin is not required after changing channels config.

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    Jeffrey Kastner

    The issue should have been fixed by the update. If it persists, consider contacting Plesk Technical Support for further investigation.

    0
    Comment actions Permalink
  • Avatar
    Jeffrey Kastner

    Leonid Gukhman, unfortunately "the Plesk license was purchased not directly from Plesk but through one of the Plesk Resellers"... so I am reporting the issue here,, as it seams it IS a Plesk issue. 

     

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    Jeffrey Kastner

    You can contact the company you purchased the license from. Plesk Partners (Resellers) are fully trained by Plesk and can assist you with it as well.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request