[Bug 7084] T_SMF_FM_FORGED_REPLYTO and FREEMAIL_FORGED_REPLYTO seem identical.

[bu...@bugzilla.spamassassin.org]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7084

--- Comment #1 from AXB <ax...@gmail.com> ---
seem but they're not

# Test potential error in base rules
header   __freemail_hdr_replyto  eval:check_freemail_header('Reply-To:addr')
meta     SMF_FM_FORGED_REPLYTO  __freemail_hdr_replyto && !FREEMAIL_FROM &&
!__freemail_safe
describe SMF_FM_FORGED_REPLYTO  Freemail in Reply-To, but not From
score    SMF_FM_FORGED_REPLYTO  0.1


# Idea from John Hardin
header   __freemail_hdr_replyto  eval:check_freemail_header('Reply-To')
meta     FREEMAIL_FORGED_REPLYTO  __freemail_hdr_replyto && !FREEMAIL_FROM &&
!__freemail_safe
describe FREEMAIL_FORGED_REPLYTO  Freemail in Reply-To, but not From
score    FREEMAIL_FORGED_REPLYTO  0.1


Reply-To versus Reply-To:addr

both scored 0.1 so not major issue

I don't see SMF_FM_FORGED_REPLYTO being published in the latest update

wonder how you got the  T_SMF_FM_FORGED_REPLYTO  rule
Have you run sa-update recently?

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