vvrpgsporcupineorg ralf hildebrandt feb 25 213817 fatush milterp0f10502 00007 noqueue src 19317570131 port 0 dst 127011 port 25 need postfix 25 later older versions send 0 client port number wietse mwbfbflsantronicscom sat apr 26 154855 2008 message 5 date sat 16 feb 2008 112406 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 47b70e2610105santronicscom contenttype textplain charsetiso88591 formatflowed douglas otis wrote technically approach creates problem domain uses dkim publishes policy record support smtp well saw thread input since 80s multimail format networkinggateway products served millions course time think pretty good idea practical aspects primarily idea attempting obtain gateway perfection persistent mail integrity dkim transformation processes expecting bit much small part system major framework user option preserve mime yesno preserving mime tells gateway import save mail raw save local proprietary format text separated attachments preserving mime become important years customers users began use offline readers eg pop3 news readers era html mail acceptable another reason users turning option customers security reasons dont even offer option users save users mail native format important comes type mua question keep focus dkim x822 mail system imv regardless x822 mail sent moved gated transformed retransformed still x822 system finally gets ever messages converted protocol gateway smtp policydiscovery record check would detect smtp supported think proposing method domain declare policy says expect mail purported originate qwk fidonet news nntp xyz protocol posted system sounds like good idea think overkill believe benefits using policies restrict 3rd party signatures dkim value mua scaling overhead much less problem depends kind mua referring online offline see vendors deal design implementations many mail reading device methods online offline offline mua different considerations online mua ignore dkim users want pickup mail via pop3 think online users think good reason chaotic discussions subjective product designs imposing feature list everyone else instead focus functional logical points fundamental protocol let implementators decide best fits product lines instead get people mandating cant might ok made sense considerations general case systems really isnt hard either sign dont idea vendor product independent want know domain intended expected asked begin looking new level mail information ok looked see really simple concept always expect 1st signature yeah ok well dont see one reject message sometimes ok fine status quo expect 3rd party signature ok reject dont care ok fine status quo etc etc really dont see matters sent preferred type burglar knocking door sincerely hector santos cto httpwwwsantronicscom httpsantronicsblogspotcom thu 07 aug 2008 195509 0500 milterp0f postfix