Feature Request: TNEF support
Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s. http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format As much as I personally despise TNEF, I'm getting tired of having to use third-party tools to manually decode winmail.dat files, and I'd rather my favorite mail client handled such decoding automatically. So I'd like to respectfully ask CTM Dev to consider adding support for automatic TNEF decoding to a future version of PowerMail. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down.
Re: Feature Request: TNEF support
I'm afraid it has very little to do with PowerMail or indeed any other email client *other than* Outlook. The problem arises when an Outlook user sends an attachment with an email that has been sent in RTF format. Only users of Outlook will be able to read that email. The TNEF format used by Outlook is not quite the standard that it should be and as a result we get the mess you are experiencing presently. The solution is to get them to resend that message in either Plain Text (preferred) or HTML format. In order to avoid the problem re-occurring, they should change their permanent settings to either Plain Text or HTML. I have had to reset many of my clients' Outlook settings to deal with this issue and no doubt will have to do so in the future. -- Tim Lapin t...@sympatico.ca On 2010-12-24, at 5:50 AM, Marco Piovanelli wrote: Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s. http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format As much as I personally despise TNEF, I'm getting tired of having to use third-party tools to manually decode winmail.dat files, and I'd rather my favorite mail client handled such decoding automatically. So I'd like to respectfully ask CTM Dev to consider adding support for automatic TNEF decoding to a future version of PowerMail. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down.
Re: Feature Request: TNEF support
TNEF is indeed a nightmare. Consider also if your EMail Provider can decode already the TNEF. We have our own MailServer with Communigate Pro Server and a TNEF decoder from Niversoft. Works like a charm. Urs Am 24.12.2010 um 11:50 schrieb Marco Piovanelli: Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s. http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format As much as I personally despise TNEF, I'm getting tired of having to use third-party tools to manually decode winmail.dat files, and I'd rather my favorite mail client handled such decoding automatically. So I'd like to respectfully ask CTM Dev to consider adding support for automatic TNEF decoding to a future version of PowerMail. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down.
Happy Holidays!
Happy Holidays! A few selections from this year's holiday shows: http://www.youtube.com/view_play_list?p=AAC08C3FACC6D0E2 Hope you enjoy :-) -- - Hiro Hiroaki Honshuku, A-NO-NE Music, Greater Boston http://a-no-ne.com http://anonemusic.com
powermail-discuss Digest #2915 - 12/24/10
powermail-discuss Digest #2915 - Friday, December 24, 2010 Feature Request: TNEF support by Marco Piovanelli marco.piovane...@pobox.com Re: Feature Request: TNEF support by Tim Lapin t...@sympatico.ca Re: Feature Request: TNEF support by Gruetzner Urs u...@mac.com Happy Holidays! by A-NO-NE Music anonemu...@mac.com -- Subject: Feature Request: TNEF support From: Marco Piovanelli marco.piovane...@pobox.com Date: Fri, 24 Dec 2010 11:50:53 +0100 Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s. http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format As much as I personally despise TNEF, I'm getting tired of having to use third-party tools to manually decode winmail.dat files, and I'd rather my favorite mail client handled such decoding automatically. So I'd like to respectfully ask CTM Dev to consider adding support for automatic TNEF decoding to a future version of PowerMail. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down. -- Subject: Re: Feature Request: TNEF support From: Tim Lapin t...@sympatico.ca Date: Fri, 24 Dec 2010 11:04:21 -0500 I'm afraid it has very little to do with PowerMail or indeed any other email client *other than* Outlook. The problem arises when an Outlook user sends an attachment with an email that has been sent in RTF format. Only users of Outlook will be able to read that email. The TNEF format used by Outlook is not quite the standard that it should be and as a result we get the mess you are experiencing presently. The solution is to get them to resend that message in either Plain Text (preferred) or HTML format. In order to avoid the problem re-occurring, they should change their permanent settings to either Plain Text or HTML. I have had to reset many of my clients' Outlook settings to deal with this issue and no doubt will have to do so in the future. -- Tim Lapin t...@sympatico.ca On 2010-12-24, at 5:50 AM, Marco Piovanelli wrote: Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s. http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format As much as I personally despise TNEF, I'm getting tired of having to use third-party tools to manually decode winmail.dat files, and I'd rather my favorite mail client handled such decoding automatically. So I'd like to respectfully ask CTM Dev to consider adding support for automatic TNEF decoding to a future version of PowerMail. -- marco -- It's not the data universe only, it's human conversation. They want to turn it into a one-way flow that they have entirely monetized. I look at the collective human mind as a kind of ecosystem. They want to clear cut it. They want to go into the rainforest of human thought and mow the thing down. -- Subject: Re: Feature Request: TNEF support From: Gruetzner Urs u...@mac.com Date: Fri, 24 Dec 2010 17:05:40 +0100 TNEF is indeed a nightmare. Consider also if your EMail Provider can decode already the TNEF. We have our own MailServer with Communigate Pro Server and a TNEF decoder from Niversoft. Works like a charm. Urs Am 24.12.2010 um 11:50 schrieb Marco Piovanelli: Hello, Over the last few years, I've been getting more and more mail with attachments wrapped in winmail.dat files. These are files in a horribly proprietary format misnomered Transport Neutral Encapsulation Format, or TNEF for short, created by Microsoft (who else?) in total disregard for the well-entrenched, very well-documented MIME Internet standard that has been used by the rest of the computing universe since the early '90s.
Re: Happy Holidays!
On 12/24/2010 9:19 AM, A-NO-NE Music wrote: Happy Holidays! A few selections from this year's holiday shows: http://www.youtube.com/view_play_list?p=AAC08C3FACC6D0E2 Hope you enjoy :-) Thank you.. once again!
