qvcimnfiqkwxudxmipassocorg send ietfdkim mailing list submissions gfkyhddlmipassocorg subscribe unsubscribe via world wide web visit httpmipassocorgmailmanlistinfoietfdkim via email send message subject body help qvcimnfiqkwxudxmipassocorg reach person managing list qghtrnrqbhlpvmipassocorg replying please edit subject line specific contents ietfdkim digest todays topics 1 new issue security threat unexpected thirdpartysenders michael thomas 2 new issue security threat unexpected thirdpartysenders hector santos 3 new issue ssp02 policy scope douglas otis 4 new issue ssp02 policy scope douglas otis ysgtmtcccom sun feb 24 103037 2008 message 1 date thu 14 feb 2008 081941 0800 michael thomas subject ietfdkim new issue security threat unexpected thirdpartysenders gfkyhddlmipassocorg messageid 47b46a1d8060106mtcccom contenttype textplain charsetiso88591 formatflowed wietse venema wrote john levine wrote trying forbid random third party signatures expect youd agree silly j falk yet treating random third party signature valid first party signature expect youd agree kind security issue would cause someone stand chair shout dkim never useful anything people suck toads yet another reason leave 3rd party signatures toadsucking scope suppose siegel ellen explicitly scope 3rd party signatures email random number valid use cases include 1 horse dead stays dead like quote think heard attributed usenet stain middle road laid dead horse mike mwbfbflsantronicscom sun feb 24 103037 2008 message 2 date thu 14 feb 2008 130149 0500 hector santos subject ietfdkim new issue security threat unexpected thirdpartysenders siegel ellen cc gfkyhddlmipassocorg messageid 47b4820d3020709santronicscom contenttype textplain charsetiso88591 formatflowed siegel ellen wrote original message lrbigfuhnacdbbdmipassocorg mailtoietfdkim xddnvjgmipassocorg behalf j falk explicitly scope 3rd party signatures email random number valid use cases include hmmmmm sounds like explicit scope statement essentially read correctly want mtas completely ignore messages 3rd party signatures message never signed point stage transport andor delivery process become play according falk read right indicated domain use dkimdiscardable protect unwanted 3rd party signatures agree sincerely hector santos cto httpwwwsantronicscom httpsantronicsblogspotcom udcatmailabuseorg sun feb 24 103037 2008 message 3 date thu 14 feb 2008 110841 0800 douglas otis subject ietfdkim new issue ssp02 policy scope charles lindsey cc dkim list messageid contenttype textplain charsetusascii formatflowed delspyes feb 14 2008 326 charles lindsey wrote wed 13 feb 2008 224610 0000 douglas otis abuseorg wrote agreed dkim employed conjunction _many_ transport protocols domain may assert sign smtp traffic may signing types traffic could potentially use dkim signature headers would domain indicate protocol cover assertion seems logical restrict _ssp policy smtp protocols define relevant policy found could add protocol policy scope record want indicate information propose new tag within ssp record purpose default ssp applies modes transport otherwise bad guys send mail like following received barcom foocom smtp received foocom ebaycom uucp zevuvqaoebaycom dkim signature agreed issue appear entered rt tracking jim suggested alternative solution formalized suggestion tag added policy record policy scope plaintext optional default smtp colon separated list policy scopes specify protocols record applies verifiers given service type must ignore record appropriate type listed currently defined service types follows matches service types disavows protocol use smtp rfc2821 nntp rfc3977 msrp rfc4975 tag intended constrain use policy various transport protocols may implement dkim defined protocols future tag also disavow use specific protocols repudiate references domain abnf policystag x73 fws fws protodisavow policystag type 0 fws fws policystagtype protodisavow policystagtype smtp nntp msrp xpolicys tagtype xpolicystagtype hyphenatedword future extension udcatmailabuseorg sun feb 24 103037 2008 message 4 date thu 14 feb 2008 114054 0800 douglas otis subject ietfdkim new issue ssp02 policy scope dkim list messageid 9e7ea5295dbb4f31bfc27a5e0333429dmailabuseorg contenttype textplain charsetusascii formatflowed delspyes prior syntax seem permit enough flexibility policy scope plaintext optional default colon separated list policy scopes specify protocols record applies verifiers given service type must ignore record appropriate type listed currently defined protocol types follows matches unlisted service types disavows protocol use excludes policy smtp rfc2821 nntp rfc3977 msrp rfc4975 uucp rfc976 tag intended constrain use policy various transport protocols may implement dkim defined protocols future tag also disavow use specific protocols repudiate references domain example ssmtpuucp would mean domain uses smtp uucp exchange messages policy apply uucp abnf policystag x73 fws fwsexcludedisavow policystag type 0 fws fws policystagtype disavow exclude policystagtype smtp nntp msrp uucp xpolicystagtype xpolicystagtype hyphenatedword future extension _______________________________________________ note well list operates according end ietfdkim digest vol 107 issue 9 tue 05 aug 2008 174355 0800 ietfdkim digest vol 107 issue 9