You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2018/01/31 14:57:12 UTC

[Bug 7543] New: Can't locate object method "check_for_forged_gmail_received_headers"

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7543

            Bug ID: 7543
           Summary: Can't locate object method
                    "check_for_forged_gmail_received_headers"
           Product: Spamassassin
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sa-update
          Assignee: dev@spamassassin.apache.org
          Reporter: jik@kamens.us
  Target Milestone: Undefined

I'm running spamassassin-3.4.0-2.el7.x86_64 on CentOS 7.

Nightly updates just started failing:

rules: failed to run FORGED_GMAIL_RCVD test, skipping:
        (Can't locate object method "check_for_forged_gmail_received_headers"
via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1322) line 227.
)
channel: lint check of update failed, channel failed
31-Jan-2018 09:53:28: SpamAssassin: Update available, but download or extract
failed

I assume this is because there's something in the nightly update that is
incompatible with the version of spamassassin I'm running?

Is this by design, i.e., was a conscious decision made to no longer support
3.4.0?

If not, can it be fixed? :-/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 7543] Can't locate object method "check_for_forged_gmail_received_headers"

Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7543

Kevin A. McGrail <km...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
                 CC|                            |kmcgrail@apache.org
             Status|NEW                         |RESOLVED

--- Comment #1 from Kevin A. McGrail <km...@apache.org> ---
Please see bz 7540

*** This bug has been marked as a duplicate of bug 7540 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.