qydlqcwsiacfymissuesapacheorg httpissuesapacheorgspamassassinshow_bugcgiid5821 additional comments wdavhpmqbngbyandexru 20080213 0252 cut messages 500kb size 1024kb way say spamassassin check messages 512kb ideas solve problem receiving mail assignee bug watching assignee gdqoxqxyzzyclaranetde sun feb 24 103036 2008 message 1 date fri 15 feb 2008 010100 0100 frank ellermann subject ietfdkim new issue ssp02 policy scope gfkyhddlmipassocorg messageid contenttype textplain charsetiso88591 douglas otis wrote smtp rfc2821 nntp rfc3977 msrp rfc4975 uucp rfc976 understand meant mentioned gateways example ssmtpuucp would mean domain uses smtp uucp exchange messages policy apply uucp verifier mta irrelevant message might started arrives mail likely smtp mail header field header field without studying fine print rfc 4356 rfcuseforusefor rfc 976 etc rfc 976 status unknown means major trouble read johns appeal first rfc 4356 attempt disaster policystag x73 fws fwsexcludedisavow policystagtype fws ssp02 wsp clear netutf8 sticks disavow ht maybe ssp03 say sp frank udcatmailabuseorg sun feb 24 103036 2008 message 2 date thu 14 feb 2008 172922 0800 douglas otis subject ietfdkim new issue ssp02 policy scope frank ellermann cc gfkyhddlmipassocorg messageid 5e68beb51a61449fb355b189b9f917c4mailabuseorg contenttype textplain charsetusascii formatflowed delspyes feb 14 2008 401 pm frank ellermann wrote douglas otis wrote smtp rfc2821 nntp rfc3977 msrp rfc4975 uucp rfc976 understand meant mentioned gateways may good initial list transport protocols illustrate one public transport affected would incorrect assume dkim policy assertion applies transports receiver may aggregate messages transports mailboxes primarily served smtp regardless transport dkim might used nonetheless transmitting domain implemented dkim specific transport protocol assertion messages signed needs reflect implemented receivers need decide whether wish merge messages one transport mailbox served smtp transport modified stream thirdparty receivers stream likely apply policy pertinent current transport syntax policy record affords enough flexibility transmitter express wish see policy applied example ssmtpuucp would mean domain uses smtp uucp exchange messages policy apply uucp verifier mta irrelevant message might started arrives mail likely smtp mail header field header field without studying fine print rfc 4356 rfcuseforusefor rfc 976 etc rfc 976 status unknown means major trouble read johns appeal first rfc 4356 attempt disaster thanks input would seem moved iana controlled protocol list policystag x73 fws fwsexcludedisavow policystagtype fws ssp02 wsp clear net utf8 sticks disavow ht maybe ssp03 say sp sorry quick cut paste rfc 4871 take 3 policy scope plaintext optional default colon separated list policy scopes specify protocols policy record applies verifiers given protocol must ignore record appropriate protocol listed currently defined protocol types follows matches unlisted transport protocols disavows protocol use excludes protocol policy assertions smtp rfc2821 nntp rfc3977 see iana ssp policy list additional protocols tag able tailor application policy various transport protocols may future implement dkim tag also disavow use specific protocols repudiate references domain gateway converts protocols ahead receiver may change policy applied uniform policy desired possible transports tag necessary default receiver combines messages various transports recommended policy pertaining primary transport protocol applied cases policy would smtp example ssmtpnntp would mean domain uses smtp nntp exchange messages policy apply nntp protocol disavowed dkim related transactions cease abnf policystag x73 wsp wspexcludedisavow policystag type 0 wsp wsp policystagtype disavow exclude policystagtype smtp nntp xpolicystagtype xpolicystagtype hyphenatedword future extension doug wyzclerewmanacuk sun feb 24 103036 2008 message 3 date fri 15 feb 2008 125053 0000 charles lindsey subject ietfdkim new issue ssp02 policy scope dkim messageid contenttype textplain formatflowed delspyes charsetiso88591 thu 14 feb 2008 190841 0000 douglas otis wrote feb 14 2008 326 charles lindsey wrote wed 13 feb 2008 224610 0000 douglas otis 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 default must 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 make clear verifiers discern protocol used originating site carefull examination received headers believable ones still dubious adding feature charleshlindseyathomedoingmyownthing tel441614366131 webhttpwwwcsmanacukchl emailwyzclerewmanacuksnail5clerewoodavecheadlesk83juuk pgp2c15f1a9fingerprint736dc25193a001e765e8647e14a4aba5 udcatmailabuseorg sun feb 24 103036 2008 message 4 date fri 15 feb 2008 112729 0800 douglas otis subject ietfdkim new issue ssp02 policy scope charles lindsey cc dkim messageid 3cf7c83fcd4848409d71c3eed72e4c4fmailabuseorg contenttype textplain charsetusascii formatflowed delspyes feb 15 2008 450 charles lindsey wrote thu 14 feb 2008 190841 0000 douglas otis abuseorg wrote feb 14 2008 326 charles lindsey wrote 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 default must concern regarding defaults addressed take 3 version includes means exclude policy matches unlisted transport protocols disavows protocol use excludes protocol policy assertions suspect default ssmtp would ssmtp domain exchanges communication whatsoever could used smtp messages used ssmtp would make assertion make clear verifiers discern protocol used originating site carefull examination received headers believable ones still dubious adding feature trace headers included within dkim signatures limitation means dkim policy applied messages arriving smtp may affect messages passing though thirdparty protocol gateways bridging protocols smtp messages arrive different protocols within administrative domain authenticationresults headers could used indicate protocol transmitted message administrative domain messages placed common mailbox would wrong assume always case see httpwww3toolsietforghtmldraftkucherawysenderauthheader11 significant value authenticationresults header filtered border mtas adding ptype transport header gateway thereby indicate transport protocol introduced message unless information conveyed recipient mechanism mailbox normally serves repository smtp messages would better apply policy pertains smtp may mean dkim policy may cause thirdparty gateway related messages refused placed within different folder result policy scope mechanism allows transports apply policy accordance domains assertion protocol support whether dkim specific assertion applied dkim smtp policy would affect messages sent nntp policy scope ssmtp example forms message exchange implement dkim scope dkim specific policies assertions becomes critical nttp message translated message carried smtp smtp policy may negatively affect categorization nntp message signed wg largely comprised primarily focused upon smtp dkim policy considered aspect smtp dkim could implemented types x822 message exchange would expect communications simultaneously implement dkim choices resolve potential issue stipulate sp policy record applies messages arriving smtp require different policy domain labels protocol b provide scope parameter within policy record maintenance overhead standpoint option b could best solution take 3 make friendly gateways change protocol disavowed dkim related transactions cease protocols disavowed dkim related transactions cease last statement provides means protect specific domains parent domain inordinate amount dns traffic existing domain spoofed spam campaign policy scope parameter allows types message spoofing mitigated dkim becomes implemented respective transport fact protocol bridged smtp inhibit use smtp protocols assume applies smtp dkim offer greatest protections means scope policy essential pick b doug _______________________________________________ note well list operates according end ietfdkim digest vol 107 issue 10 tue 05 aug 2008 200030 0800 bug 5821 problem bat cut messages