winmail.dat
Hi. I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why mutt couldn't cope with some mail I got, containing an attachment, named winmail.dat (MS Outlook). Mutt wasn't able to unpack the two JPG files that were packed into that winmail.dat container. I asked the friend to send the same email to another account where I hat thunderbird (5.0) and I was able to see the attachments (JPGs) without seeing something of winmail.dat at all. Also forwarding the mail from mutt to the other account didn't help. I then saw a winmail.dat as an attachment and TB didn't know what to do with it. -- Christoph
Re: winmail.dat
Christoph P.U. Kukulies writes: > Hi. > I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why > mutt couldn't cope with > some mail I got, containing an attachment, named winmail.dat (MS Outlook). Ask the sender to configure their mail tool for plain text or html rather than rich text.
Re: winmail.dat
Am 18.07.2011 11:12, schrieb Lars Hecking: Christoph P.U. Kukulies writes: Hi. I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why mutt couldn't cope with some mail I got, containing an attachment, named winmail.dat (MS Outlook). Ask the sender to configure their mail tool for plain text or html rather than rich text. Wouldn't it be more appropriate to ask why Thunderbird can process said email from that users' settings (outlook) and mutt cannot, rather than asking the sender to change something in his settings? -- Christoph
Re: winmail.dat
On 18.07.11,12:29, Christoph P.U. Kukulies wrote: > Am 18.07.2011 11:12, schrieb Lars Hecking: > >Christoph P.U. Kukulies writes: > >>Hi. > >>I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why > >>mutt couldn't cope with > >>some mail I got, containing an attachment, named winmail.dat (MS Outlook). > > > > Ask the sender to configure their mail tool for plain text or html rather > > than rich text. > > > Wouldn't it be more appropriate to ask why Thunderbird can process > said email from that > users' settings (outlook) and mutt cannot, rather than asking the > sender to change something in his > settings? In mutt you can use tnef to handle these type of attachments: http://linux.die.net/man/1/tnef In Thunderbird you can use ktnef. Jostein
Re: Multi-window Mutt
On 18.07.11,11:01, Cameron Simpson wrote: > On 17Jul2011 11:24, Marcelo Luiz de Laia wrote: > | I am looking for a way to spawn new windows for reading and writing > | e-mails with a mere click using mutt in X environment. > | > | I have googled and found this solution > | http://op-co.de/blog/posts/mulit-window_mutt/ and this question > | (without answer) http://marc.info/?l=mutt-users&m=114347881514912 > | > | This thread was very usefull, too > | http://www.mail-archive.com/screen-users@gnu.org/msg00566.html > | > | But, I ask you: > | > | Have you any suggestion/tips here? > > I spawn detachable screen sessions for mutt email replies. Details here: > > http://www.mail-archive.com/mutt-users@mutt.org/msg40856.html > > It would be pretty easy to adapt it to spawn a new terminal window containing > the screen session I would think. I could put some effort into that if you > have trouble. > > The above scheme has the advantage that one can detach from the screen > session before completing the reply and reattach later. By spawning a > terminal window you could get that (reply session survives window close) > and immediate return to your mutt reading (because the reply is off in > another window). > > Let me know if you'd like me to suggest modifications to the existing > scripts I use. > This looks like a nice way to use screen with mutt for these functionality. Will check out this. Jostein
Re: winmail.dat
> > Wouldn't it be more appropriate to ask why Thunderbird can process said > email from that > users' settings (outlook) and mutt cannot, rather than asking the sender > to change something in his settings? The sender's settings are pre-MIME. MIME is a set of Internet mail standards that has been around in some form for nearly 20 years or so. Look up mailcap settings for application/ms-tnef, but in my personal opinion, this sort of thing should be discouraged.
Re: winmail.dat
Am 18.07.2011 12:20, schrieb Christian Brabandt: On Mon, July 18, 2011 9:45 am, Christoph P.U. Kukulies wrote: Hi. I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why mutt couldn't cope with some mail I got, containing an attachment, named winmail.dat (MS Outlook). Mutt wasn't able to unpack the two JPG files that were packed into that winmail.dat container. I asked the friend to send the same email to another account where I hat thunderbird (5.0) and I was able to see the attachments (JPGs) without seeing something of winmail.dat at all. Also forwarding the mail from mutt to the other account didn't help. I then saw a winmail.dat as an attachment and TB didn't know what to do with it. -> I 1 [text/plain, quoted, iso-8859-1, 0,2K] A 2 winmail.dat[applica/ms-tnef, base64, 5,5M] Thanks, hope you don't mind me sending this back to the list. I got this "tnef"-package. What would now be the steps to make mutt to recognize an attachment named winmail.dat and use"tnef" to unpack it and show me the attachments when I "v" the email. At present it looks like this: -> I 1 [text/plain, quoted, iso-8859-1, 0,2K] A 2 winmail.dat[applica/ms-tnef, base64, 5,5M] I'd rather have it look like showing the IM000xx.JPG files or whatever winmail.dat is hiding to me. -- Christoph
Attachmentmenu file information
I've been using mutt for while (happily), but infer from a discussion that my attachment menu might not provide all the information it should. For example for a plain message, the menu writes: I 1 but another person's menu has: I 1 [text/plain, quoted,iso-8859-1, 0,2K] Perhaps this is set in .muttrc configuration, but if so I had trouble finding it. Haines Brown
Re: winmail.dat
On 18.07.11,13:27, Christoph P.U. Kukulies wrote: > Am 18.07.2011 12:20, schrieb Christian Brabandt: > >On Mon, July 18, 2011 9:45 am, Christoph P.U. Kukulies wrote: > >>Hi. > >>I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why > >>mutt couldn't cope with > >>some mail I got, containing an attachment, named winmail.dat (MS Outlook). > >> > >>Mutt wasn't able to unpack the two JPG files that were packed into that > >>winmail.dat container. > >>I asked the friend to send the same email to another account where I hat > >>thunderbird (5.0) and I was able to > >>see the attachments (JPGs) without seeing something of winmail.dat at all. > >> > >>Also forwarding the mail from mutt to the other account didn't help. I > >>then saw a winmail.dat > >>as an attachment and TB didn't know what to do with it. > >-> I 1 [text/plain, quoted, > >iso-8859-1, 0,2K] > > A 2 winmail.dat[applica/ms-tnef, > >base64, 5,5M] > > > > > Thanks, hope you don't mind me sending this back to the list. > > I got this "tnef"-package. What would now be the steps to make mutt > to recognize an attachment > named winmail.dat and use"tnef" to unpack it and show me the > attachments when I "v" the email. > > At present it looks like this: > -> I 1 [text/plain, quoted, > iso-8859-1, 0,2K] > A 2 winmail.dat[applica/ms-tnef, > base64, 5,5M] > > I'd rather have it look like showing the IM000xx.JPG files or whatever > winmail.dat is hiding to me. > Try the steps listed for mutt and mailcap setup in the manual: http://linux.die.net/man/1/tnef Jostein
Re: winmail.dat
Quoth Christoph P.U. Kukulies on Monday, 18 July 2011: > Am 18.07.2011 12:20, schrieb Christian Brabandt: > >On Mon, July 18, 2011 9:45 am, Christoph P.U. Kukulies wrote: > >>Hi. > >>I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why > >>mutt couldn't cope with > >>some mail I got, containing an attachment, named winmail.dat (MS Outlook). > >> > >>Mutt wasn't able to unpack the two JPG files that were packed into that > >>winmail.dat container. > >>I asked the friend to send the same email to another account where I hat > >>thunderbird (5.0) and I was able to > >>see the attachments (JPGs) without seeing something of winmail.dat at all. > >> > >>Also forwarding the mail from mutt to the other account didn't help. I > >>then saw a winmail.dat > >>as an attachment and TB didn't know what to do with it. > >-> I 1 [text/plain, quoted, > >iso-8859-1, 0,2K] > > A 2 winmail.dat[applica/ms-tnef, > >base64, 5,5M] > > > > > Thanks, hope you don't mind me sending this back to the list. > > I got this "tnef"-package. What would now be the steps to make mutt to > recognize an attachment > named winmail.dat and use"tnef" to unpack it and show me the attachments > when I "v" the email. > > At present it looks like this: > -> I 1 [text/plain, quoted, > iso-8859-1, 0,2K] > A 2 winmail.dat[applica/ms-tnef, > base64, 5,5M] > > I'd rather have it look like showing the IM000xx.JPG files or whatever > winmail.dat is hiding to me. > > -- > Christoph > Personally, I use the 'v' function to view the contents of the tnef file rather than to unpack it. Thusly in .mailcap: application/ms-tnef;tnef -t %s; copiousoutput; needsterminal; Then, in .muttrc I map Ctrl+t in the attachments menu to unpack the attachment into a special folder (~/Mail/attach) so I can then go view the attachments from the shell: macro attach \Ct "|tnef --overwrite -C ~/Mail/attach\n" "Unpack TNEF attachment" I suppose it would be possible to create a macro that does the unpack and view all contents all in one step, but that's going too far down the "automatically trust anything you get in an email" road for my tastes. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpoK1DNRmKeK.pgp Description: PGP signature
Re: Attachmentmenu file information
On Mon, 18 Jul 2011, 10:21-0400, Haines Brown wrote: > I've been using mutt for while (happily), but infer from a discussion > that my attachment menu might not provide all the information it > should. > > For example for a plain message, the menu writes: > > I 1 > > but another person's menu has: > > I 1 [text/plain, quoted,iso-8859-1, 0,2K] > > Perhaps this is set in .muttrc configuration, but if so I had trouble > finding it. See if this helps: http://www.mutt.org/doc/devel/manual.html#attach-format Do a ":set ?attach_format" and compare it to the default value given there. -- Jimmy
