Yerase's TNEF Stream Reader

I know it's been a while, but I'm finally back to a point where I have the time & energy to work on ytnef. There's been a few patches submitted regarding issues with the latest versions of Outlook, and I hope to have those integrated in short order.

Also, I plan to do a complete API rewrite on the library. The existing interface is a real nightmare, and for that I apologize. I've been writing another C/C++ Library for work, and I've learned alot of "the right way" for such interfaces. So expect a new libytnef soon with a vastly improved interface!

Also, there's been some interest in ytnef lately in integrating it into some mail scanners and servers. Hopefully I can get a new binary out soon that will help with this alot. So keep checking back and keep letting me know what does & doesn't work! (0 comments)

It's been a while since my last update, but it's been a very busy year for me. New house, new job, new life basically. But things are settling down again, so I'm going to be working on ytnef again. Here's a list of things you can see in the next release:

* Better Outlook integration - there's been a few bug reports filed about new fields that are required for new versions of outlook to properly receive the VCAL attachments.
* TNEF drop-in integration - the next version (3.0 I suppose) of ytnef will support a "tnef replacement" mode, where (I hope) it will emulate tnef behavior, showing the VCAL/VCARD entries as extra attachments.
* Totally new API - I know this doesn't matter to many of you, but i'm going to totally rewrite the API and document it with Robodoc. Hopefully the new version will make alot more sense than the current travesty of byte-swapping and pointer madness.
* GUI Interface - This will be one of the last things i'm going to tackle, and hopefully someone will step up to the plate to help, but I want to write a GTK GUI for ytnef that will run on Windows, Linux, and OSX. This will hopefully integrate nicely with projects like Thunderbird and others.

I've been keeping a close eye on the google ytnef results, and I've seen that it's starting to get some real use in alot of communities. I'm flattered that so many people find it useful, and I hope that I can continue to keep it current & useful. So keep checking back, things are about to get exciting! (1 comments)

This is a minor release compared to previous versions. The only real change is that now the libytnef will compile on older (gcc2.96 etc) compilers. (0 comments)

Big news in this release! Recurring meetings are now supported! I have to thank Viraj Alankar for figuring all this out, and coding up the patches to implement it. I've rolled up new tarballs and RPM's and they're up for download.

One note though, the RPM's do not contain the ytnefprocess.pl script. It's still available in the source tarballs, but in the RPM's it adds alot of unnecessary dependancies so I removed it. (0 comments)

With some help from a few Exchange & Outlook users, I was finally able to get true meeting confirmations to work! Now when you accept a meeting VCF in Evolution (or any other VCF compatible email client) sent by Outlook, the resulting meeting acknowledgement will be interpreted properly by outlook!

This is a big achievement, and I'ld like to thank everyone who helped get this working! So get your ytnef 2.4 and try it out! (0 comments)

Kudos to Duncan Sargeant for pointing out a glitch with the Leap Year code again.. I was making March have 29 days instead of February!

Also, kudos to Dave Kelly for submitting a nice patch to add RPM support to libytnef! So now you can get a nice simple RPM. Be sure to download the new version, & recompile ytnef today! (0 comments)

Congratulations to Viraj Alankar and Baruch Even for finding a problem with my handling of dates in the new Year. Seems the leap year wasn't being computed correctly and the dates were all off by a day. Also, events on January 1st caused an infinite loop!

It's fixed now, just recompile this and your existing ytnef 2.3 release with it, and you're sll set! (2 comments)

New versions all around ! And just in time for Christmas. The big feature this time around is support for Compressed RTF entries. This means that now your calendar entries have a DESCRIPTION tag, and that TNEF forwarded email will show up correctly. The inclusion of the RTF is done rather naively at the moment, but it seems to work just fine on my end with Evolution.

Enjoy! (0 comments)

Ytnef now has beginning support for Compressed RTF Fields! This means that now I can finally get a "Description" field in those calendar entries. It's still buggy, and only in CVS, but the decoding part works great.

Have to thank Jason Bobier for pointing me to the jtnef project (Put a link in the links section) for the info. (0 comments)

I saw someone was advertising a problem with ytnef on their web site today, and after a few emails I figured out what was going on.

It seems that there really are contact cards with no person's name associated with them. The example in case was a card for a company, "American Airlines" in this case. A few modifications later, and now it will extract contact cards regardless of the name.

While I was at it, I also fixed a glitch in the library that occasionally caused a segfault with multi-valued MAPI attributes. But it's all fixed now! (0 comments)