anders norrbring wluhenorrbringse friday 22 february 2008 0914 brad bourn wrote would upgrade 64bit dvd danger robinson weve told many times including horses mouth work render system inoperable words findings means reinstall reconfigure sigh anders b friday 22 february 2008 95952 anders norrbring wrote decent way migrate fully operational 32bit installation opensuse 103 x86_64 version randall schulz unsubscribe email assipqffnmekprykassopensuseorg additional commands email qybuovjskcmhopensuseorg __________ information eset nod32 antivirus version virus signature database 2896 20080222 __________ message checked eset nod32 antivirus httpwwwesetcom udcatmailabuseorg sat apr 26 154854 2008 message 4 date sat 16 feb 2008 052015 0800 douglas otis 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 contenttype textplain charset feb 15 2008 1105 pm hector santos wrote 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 horse died leaving barn mx mandate discovery record would imposed domains 1 implemented dkim 2 published dkim policy record scheme impact domains publishing dkim policy records correct mx record may never published cases would nice impose simple limitation domain tree walking polices mandating discovery record mx case smtp published along policy records existence two records provides means detect fraudulent use domain without examining record content approach tolerates policy record format changes still safely minimizing impact daily onslaught spoofed references existing domains even handle messages mandate would offered means squelch series policy key transactions cases invalid signature may occur many reasons leaves result category significantly weaker finding domain publishing policy record without also publishing discovery record technically approach creates problem domain uses dkim publishes policy record support smtp messages converted protocol gateway smtp policy discovery record check would detect smtp supported return path instantiated protocol gateway could provide conversion dsns domain return path would unrelated dkim signature yes might seen disadvantage also closes avenue abuse controlled dkim limitation would induce assurance direct return path domain would indicating dont want protocol translation gives originating domain greater control dummy records might published achieve desired effect keep mind steps ssp recommendation long end result people dont follow steps possible mx lookup already done places mx record queried policy record found check existence domain mx record accessed recently could cache mandate publish policy discovery records together would greater advantage checking mx record 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 logic would way around would seem wg wishes keep options open adding scope policy record effect possible somewhat larger policy records 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 represents minority view however 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 pairing policydiscovery records content policy record matter preventing spoofing existent domains support smtp hand term discardable instead strict sole exclusive words effect means transactional domains wishing thwart spoofing instead likely find much communications lost take time signature integrity mature problem due mailinglists discardable term likely ensure needed level integrity never occurs much essential feedback whether domain spoofed whether signature integrity problem likely lost 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 dkim value mua scaling overhead much less problem triage process mta could guided policy assertions dkim validation mta may limited domains history targeted abuse domains unwilling make signature assurances filtering must relaxed reduce rate false positives regard appears agreement ssp01 better respect seem problem signatures added thirdparties however admitting understanding thread thu 07 aug 2008 211035 0100 sv opensuse migrate 32bit 64bit