From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: [Q] winmail.dat
Date: Tue, 17 Jan 2012 20:54:22 +0000 [thread overview]
Message-ID: <87d3aixd6p.fsf@ucl.ac.uk> (raw)
In-Reply-To: <871uqynp55.fsf@gmx.ch> (Sven Bretfeld's message of "17 Jan 2012 19:46:14 +0100")
"Sven Bretfeld" <sven.bretfeld@gmx.ch> writes:
> Didier Verna <didier@xemacs.org> writes:
>
>> sometimes I receive attachments named winmail.dat in ms-tnef format.
>> Gnus only show me this, although the gmail interface seems to be able to
>> decypher what's inside (for instance, the last one was actually a pdf
>> file).
>
> Had the same problem just today. I switched to Evolution with
> plugins-experimental for this email. Know of no way that Gnus handles
> these silly things.
>
> Sven
>
I cannot help you figure out how to get gnus to automatically decode a
winmail.dat attachment (I *do* dislike Outlook intensely...) but, at
least on linux, you can install the "tnef" [1] package which allows you
to extract files from a winmail.dat file. Not ideal but at least it
works.
And then follow this up with an email to the offending sender with this
link:
http://www.dwheeler.com/essays/microsoft-outlook-tnef.html
which is an old document but I think probably applies (section 2). I've
done this in the past and it has always worked!
HTH,
eric
Footnotes:
[1] http://tnef.sourceforge.net/
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1 + No Gnus v0.18
next prev parent reply other threads:[~2012-01-17 20:54 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 14:13 Didier Verna
2012-01-17 18:46 ` Sven Bretfeld
2012-01-17 20:54 ` Eric S Fraga [this message]
2012-01-18 0:12 ` Mark Simpson
2012-01-18 8:43 ` Eric S Fraga
2012-01-18 9:15 ` Didier Verna
2012-01-18 10:06 ` Eric S Fraga
2012-01-27 17:33 ` Lars Ingebrigtsen
2012-01-31 13:00 ` Eric S Fraga
2012-01-31 13:49 ` Didier Verna
2012-01-31 17:27 ` Lars Ingebrigtsen
2012-01-31 17:33 ` Lars Ingebrigtsen
2012-01-31 19:04 ` Eric S Fraga
2012-02-01 0:33 ` Lars Ingebrigtsen
2012-02-01 1:18 ` Lars Ingebrigtsen
2012-02-01 8:15 ` winmail.dat Adam Sjøgren
2012-02-01 13:03 ` winmail.dat Lars Ingebrigtsen
2012-02-01 15:13 ` winmail.dat Adam Sjøgren
2012-02-01 16:11 ` [Q] winmail.dat Eric S Fraga
2012-02-02 9:41 ` Lars Ingebrigtsen
2012-02-01 8:58 ` Didier Verna
2012-02-01 13:20 ` Lars Ingebrigtsen
2012-02-03 11:48 ` Mark Simpson
2012-02-06 23:29 ` Lars Ingebrigtsen
2012-02-09 1:22 ` Mark Simpson
2012-02-09 1:30 ` Lars Ingebrigtsen
2012-02-09 1:35 ` Mark Simpson
2012-02-13 17:13 ` Ted Zlatanov
2012-02-14 2:54 ` Mark Simpson
2012-02-14 13:09 ` Ted Zlatanov
2012-02-15 11:57 ` Mark Simpson
2012-02-15 13:37 ` Ted Zlatanov
2012-02-21 1:09 ` Mark Simpson
2012-02-21 20:50 ` Ted Zlatanov
2012-01-31 18:41 ` Lars Ingebrigtsen
2012-01-31 23:05 ` winmail.dat Adam Sjøgren
2012-02-01 16:12 ` winmail.dat Eric S Fraga
2012-02-01 14:32 ` [Q] winmail.dat Didier Verna
2012-02-01 15:20 ` UWE RICHARD OTTO BRAUER
2012-02-01 19:11 ` Lars Ingebrigtsen
2012-02-01 19:36 ` Lars Ingebrigtsen
2012-02-02 9:32 ` Stephen J. Turnbull
2012-02-02 9:35 ` Lars Ingebrigtsen
2012-02-02 10:17 ` Didier Verna
2012-02-02 16:18 ` Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3aixd6p.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).