On Mon, 23 May 2011 03:50:06 +0100, Hector Santos <hsan...@isdg.net> wrote:
> Case in point. Right now, I am looking at a gmail.com which I am > pretty sure was not in Base64 MIME. However, it was submitted to IETF > DISCUSS group and its showing up as base64 MIME. I don't know if the > list did it one of the hops before the DKIM-Signature. > > But the body hash failed. So I took the message, made a copy and > unbased64 the body, pulled the list footer and poof! - the body hash > was ok again. > > It would of been nice to have some DKIM-Signature flag that might > indicate the Content-Transfer-Encoding, i.e.: > > et="base64" <--- copy of the top level Content-Transfer-Encoding Could you get the effect of this by including the Content-Transfer-Encoding header in the 'h=' and doing some fancy checks involving the 'bh=' (to detect whether it was the body or the headers or both that were broken)? -- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Web: http://www.cs.man.ac.uk/~chl Email: c...@clerew.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5 _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
