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 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages damon 2 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis 3 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos 4 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis 5 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos 6 admin mipassocorg dkimorg mailing list host change 21617 16pm pacific tme dave crocker byfzbhmergmailcom sat apr 26 154954 2008 message 1 date fri 15 feb 2008 184938 0500 damon subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos cc dkim list mh michael hammer 5304 messageid 28315622390381732k315i2239qz8v73283h56osfbqmailgmailcom contenttype textplain charsetutf8 case need tie breaker 1 regards damon sauer udcatmailabuseorg sat apr 26 154954 2008 message 2 date fri 15 feb 2008 182805 0800 douglas otis subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages damon cc mh michael hammer 5304 dkim list messageid 67ce94068e3940e4a497203dd6e57ac4mailabuseorg contenttype textplain charsetusascii formatflowed delspyes feb 15 2008 349 pm damon wrote case need tie breaker 1 summarize bunch 1 says little push back generated concept dkim policy applicable transport protocols might bridged smtp protocol bridging could become problematic email supported natively transmitting domain course also creates problems respect dsns well ignoring problem dsns mandating support smtp accepting smtp message bridged different transport would rather problematic smtp also supported however accepting messages smtp represents choice opens avenue likely permit abuse concern seems somewhat ill founded determining support relevant transport protocol could generally stated using absence protocol discovery record mx case smtp conjunction presence dkim policy record offered means indicate support specific protocol supported means truncate policy discovery process subsequent validation transactions would better protected existing domains involved email traffic generated spoofed messages addition would offered extremely strong refutation fraudulent messages made existing domain strong evidence good thing general settle issue protocol covered dkim policy jim suggested policy scope tag instead would permit domains indicate transport protocols implemented dkim signal dkim policy applied gateways smtp means disavow support transport protocol could important means better limit avenues abuse case message bridged smtp likely find smtp policy applied imho cant helped protocol scope parameter dkim policy could im smtp abuse limited smtp ability clearly indicate whether message fraudulent without incurring additional transactions also important general domain protection standpoint jim right policy made include scope also offers flexible workable solution message abuse demand negotiated changes accommodated extent policy assertions keeping lid added overhead represents remaining challenged doug mwbfbflsantronicscom sat apr 26 154954 2008 message 3 date sat 16 feb 2008 020517 0500 hector santos subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis cc dkim list mh michael hammer 5304 messageid 47b68b2d8020705santronicscom contenttype textplain charsetiso88591 formatflowed douglas otis wrote feb 15 2008 349 pm damon wrote case need tie breaker 1 summarize bunch 1 says little know dont hate call follow chieftain syndrome opinion votes came reason explanation position might help sway others push back generated concept dkim policy applicable transport protocols might bridged smtp doug record mx lookup must ssp record discovery setup imo prefer may even historically requirement therefore highly possible mx exist keep mind steps ssp recommendation long end result people dont follow steps possible mx lookup already done places look way way view keep must mx lookup requirement ssp discovery steps 1 would agree also must addinghaving mx record x822from domain used domains new dkim signing mail operations less problem idea general dkim deployment recommendation domains consider even possibly recommendation mx record x822from standpoint dkimssp protocol consistency especially differs return path sender domains ability clearly indicate whether message fraudulent without incurring additional transactions also important general domain protection standpoint jim right policy made include scope also offers flexible workable solution message abuse demand negotiated changes accommodated extent policy assertions keeping lid added overhead represents remaining challenged 1 youre right important part implementation considerations consider mandate x822from mx must also least allow verifier policy based handling removed current emasculated model since policies allowed implementators optimize scale dkim processing removal reduces mda adoption incentive dkim verification thus little payoff resulting additional overhead less reason even bother overhead sincerely hector santos cto httpwwwsantronicscom httpsantronicsblogspotcom wed 06 aug 2008 040757 0800 ietfdkim digest vol 107 issue 11