Mark Simpson

Show:

What's happening?

  • Comment: *.jpeg can not parse Successfully

    Looking at the unpacked attachment in a hex editor - it does not appear to be a JPEG file. Quoting wikipedia: JPEG image files begin with FF D8 and end with FF D9. JPEG/JFIF files contain the ASCII code for "JFIF" (4A 46 49 46) as a null terminated string. JPEG/Exif files contain the ASCII code for "Exif" (45 78 69 66) also as a null terminated string, followed by more...

    2012-04-19 04:46:32 PDT in TNEF

  • Comment: *.jpeg can not parse Successfully

    I see the same behavior as reported. The verobse/debug output shows that TNEF is not finding a name of the file other than 'Untitled Attachment' (this is not invented by TNEF - it is in the winmail.dat file itself). If it is possible to get the jpeg that is embedded in the winmail.dat it could be beneficial to my debugging.

    2012-04-17 04:12:49 PDT in TNEF

  • Comment: *.jpeg can not parse Successful

    duplicate of 3518728.

    2012-04-17 03:59:27 PDT in TNEF

  • TNEF

    verdammelt pushed 1 commit(s) to refs/heads/master in the tnef Git repository of the TNEF project.

    2012-02-29 17:38:32 PST in TNEF

  • TNEF

    verdammelt made 2 file-release changes.

    2012-02-29 17:26:03 PST in TNEF

  • TNEF

    verdammelt made 1 file-release changes.

    2012-02-29 17:25:17 PST in TNEF

  • TNEF

    verdammelt pushed 7 commit(s) to refs/heads/master in the tnef Git repository of the TNEF project.

    2012-02-29 17:21:26 PST in TNEF

About Me


Send me a message