If you've ever opened an email from a university faculty member in a email client like Gmail, you probably noticed a weird "winmail.dat" file attached below. This file is generated when an email is sent from a Microsoft Outlook/Exchange account to a non-outlook recipient, and is encoded in Microsoft's "TNEF" format which isn't normally readable.
When an email is sent to a non-outlook recipient, most formatting data is stripped away and encoded in this file. In the best case, some simple styling and font information might be lost. In the worst case, entire things like tables might be lost, making the email possibly unreadable.
What it does
Our chrome extension will run in the background when you are accessing your Gmail inbox. It checks the email you are currently looking at, and if it detects a TNEF encoded attachment it extracts the relevant formatting information from the file and automatically displays it as the message body.
How we built it
Once we have the attachment, we send the attachment to our Google Cloud server, which is running a web server using Python and Flask. Here, we used the open source Python library tnefparse to extract the HTML data from the attachment. That HTML is then sent back to the extension, where it is then added to the web page to give a seamless viewing experience.
Challenges we ran into
We ran into a lot of challenges working with the Chrome Extension and Gmail APIs. Documentation around the web was confusing and hard to come by, and we struggled a lot with getting stuff to work in the way we expected it to.
Accomplishments that we're proud of
We're proud of how well and how quickly our script automatically detects and replaces TNEF formatted emails. Other than our extension, the only way to parse a TNEF file outside of Outlook is to use some type of converter (either online of as a desktop program) that requires you to manually parse a file. Our extension is not only automatic, but returns the parsed contents in a much more convenient and readable way.
What we learned
We learned a lot about how to build Chrome Extensions, how to make Google API requests and how Google's OAuth authorization works. We also learned how to setup a Google Cloud server and how to communicate between it and our extension.
What's next for WinMail Helper Chrome extension
We still have a lot of things we'd like to do:
- Improve UI and give user customization options
- Add support for other TNEF encoded objects like RTF and image files
- Improve Google Cloud performance/availability
- Improve Security if needed
Some other longer term goals include:
- Porting the extension to other browsers (Safari, Firefox)
- Expanding support for other web-based email services (Yahoo, etc.)