jdd xyidodinorg joe sloan écrit well figures reading silence wire ready build wooden computer way ot know one time ago school pupils signal processors jdd httpwwwdodinnet udcatmailabuseorg sun feb 24 103010 2008 message 4 date tue 12 feb 2008 103641 0800 douglas otis subject ietfdkim issue ssp02 mx record publishing mandate reduce dns overhead ssp discovery detect fraudulent messages wietse venema cc gfkyhddlmipassocorg messageid contenttype textplain charsetusascii formatflowed delspyes feb 12 2008 723 wietse venema wrote douglas otis better ensure minimum number dns transactions occur processing dns ssp key txt records especially domains implement email ssp draft mandate publishing mx records whenever ssp record also published since ssp discovery process makes use mx record queries determine whether domain exists ssp record returned domain published mx record thereby signals email dkim used email addresses domain strategy affords better cache hit rate ssp discovery process detection fraudulent uses domain means protect second level domains 1 per draft nxdomain reply author domain lookup already terminates ssp algorithm failure good enough disagree dkim ssp appropriate vehicles making records mandatory ssp already suggests querying mx records facilitate discovery even though mx record need published prevents ssp making publication record mandatory valid reason domain implements dkim also publish mx record record _essential_ truncating sorts policy discoveries might become associated introduction dkim domain exist currently means domain owner truncate policy discovery processes walking next domain requesting number key records addition also positive means domain owner disavow messages inducing undesired policy dkim transactions prevent additional transactions without convention two transactions convention could prevent significantly transactions parent domains addition convention also makes explicit message related domain disavowed convention juice worth squeezing ssp record returned without also mx record author domain signature considered fraudulent without dns transactions attempted _1 oppose reintroduction suspicious fraudulent etc overlyspecific interpretations failures often nonmalicious causes agreed however ssp record mx record seems like rare failure mode perhaps message result could called disavowed unsupported important aspect definition avoid implied message handling without knowing reliability convention doug wed 06 aug 2008 201704 0100 opensuse defragging possible necessary