So it's Saturday, not Monday yet, but nothing has changed... has a "fix" been published yet?  Maybe the fix doesn't work?

]$ sudo /usr/bin/sa-update -vvvv
Update available for channel updates.spamassassin.org
rules: failed to run URI_HOST_IN_BLOCKLIST test, skipping:
        (Can't locate object method "check_uri_host_in_blacklist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 394.
)
rules: failed to run URI_HOST_IN_WELCOMELIST test, skipping:
        (Can't locate object method "check_uri_host_in_whitelist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 1489.
)
channel: lint check of update failed, channel failed
Update failed, exiting with code 4

-Alan

On 7/29/2021 1:36 PM, Kevin A. McGrail wrote:
Fixes are likely done and just waiting on masscheck, etc. to publish rules.  If it isn't fixed by Monday, please let us know.
P.S. 3.3.1 is very old.  Can you upgrade?
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail <https://www.linkedin.com/in/kmcgrail> - 703.798.0171


On Thu, Jul 29, 2021 at 11:21 AM Alan Sparks <aspa...@doublesparks.net <mailto:aspa...@doublesparks.net>> wrote:

    Starting yesterday, my SA 3.3.1 running on CentOS started throwing
    lint
    errors, as below.  Is there a fix for this?

    Thanks in advance.

    -Alan

    $ sudo /usr/bin/sa-update -vvv
    Update available for channel updates.spamassassin.org
    <http://updates.spamassassin.org>
    rules: failed to run URI_HOST_IN_BLOCKLIST test, skipping:
             (Can't locate object method "check_uri_host_in_blacklist"
    via
    package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 394.
    )
    rules: failed to run URI_HOST_IN_WELCOMELIST test, skipping:
             (Can't locate object method "check_uri_host_in_whitelist"
    via
    package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 1489.
    )
    channel: lint check of update failed, channel failed
    Update failed, exiting with code 4



Reply via email to