On 30.10.2012, at 15.28, Christian Rößner wrote: > msg.ext-ref = 83713 1282212 B76 > 6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a0400002cb72ff6
> But I did not understand the base64 explanation. Sorry :) For me it seems all > "options" are B-prefixed. So they are all base64? But which value is now the > size and how do I create the missing files now? Using dd? Can you give me an > example from the output above? That would help me. They are all base64 yes, the B76 means that all the encoded lines will be 76 chars long. So the file size above needs to be 1282212, divided by 77 (76+LF) = 16652 full lines and 8 bytes over. Base64 encodes 3 byte blocks into 4 byte chars, so the original data has (16652*76+8)/4*3 = 949170 bytes (or 1-2 bytes less, but that makes no difference because it's padded anyway). So if you create /attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a0400002cb72ff6 that is 949170 bytes long, and do the same for the rest of the attachments, you should be able to read this mail without errors. You can easily create the files without wasting space with: dd if=/dev/zero of=foo bs=1 seek=949169 count=1
