karsten bräckelmann qmitxmehrudersportde mon 20080218 1312 0800 tim alberts wrote thank everyone responding per user settings prompts question dont see answer yet happens command spamassassin removeaddrfromwhitelist per user settings assumed running command root would filter user awl thinking guess stands reason doesnt spamassassin doesnt know users solution log user issue command clear marked address account handled situation yes per user conf awl db user affected must fix awl like removed corrupt awl dbs exactly users could removed email address question note deleted autowhitelist file selected users communicating marked email address unfortunately wont know worked customer emails fortunately true one affected users run mail email address sa spamassassin savedrawmail less check resulting xspam headers instead spamassassin use spamc generally anyway sure affected users correct environment 1 rerun mail spamassassin see sane awl score unless overall score identical previous one guenther 1 su vs su caveat su root char t10pse0r0dtu0ghnox4exc8x79xf4xabx51x8ax10xf4xf4xc4 main char hmhtxt2hcilxs0 i0i1tsh putchartshms0 udcatmailabuseorg sat apr 26 154851 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 thu 07 aug 2008 021315 0100 false positive scoring dont understand