qydlqcwsiacfymissuesapacheorg httpsissuesapacheorgspamassassinshow_bugcgiid5842 additional comments wlbpaliggfaddostechca 20080303 2037 reply comment 3 reply comment 2 reply comment 1 need record receivedspf btw meant need mta configurations pick milter milter httpsvnperlorgviewvcqpsmtpdtrunkpluginssender_permitted_fromviewmarkup httpwwwopenspforgimplementations think though dont spf lookups mtas leave spamassassin maybe add support recording isnt header already use header way reuse spf lookups standardscompliant since think dictated std would help generating scores set0 least recommended smtp receivers record result spf processing message header could guess itd give us positive indication spf checks actually done domains dont publish spf records meantime think itd acceptable make special case generate scores set23 simply copy set01 13 02 dont data cant trust ga able trust ratios since domains lookup logic yeah probably going copying im sure whos corpus responsible scores generated 32 however doesnt solve core issue tflags net need keep network lookup code running tflags net necessary reuse support knows set rule score 0 attempting reuse hits really isnt reuse supposed taking care dual dependency reuse tflags net however note means code doesnt run set0 past round_the_world test split two rules round_the_world round_the_world_local latter set0 former set2 spf rules adding duplicate ruleset spf_pass_local spf_neutral_local etc better names welcome course really want avoid different rules like itll confuse people cause arent confused write metas combine two versions could even move current set __spf_pass_local __spf_pass_net combine new spf_pass meta rule would reusecompatible clearly delineate set0 set2 rules might complicate score generation receiving mail assignee bug watching assignee thu 07 aug 2008 234401 0800 bug 5842 spf rules tflags net