I am sure that I either do not understand something in setting up a mutt
configuration, or maybe I'm having a very bad day (Monday), but I am having
trouble with attachments sent from mutt, as follows:


When mutt reads an email from another MIME source, exchange in this case,
the message looks like this:

X-Mailer: Internet Mail Service (5.5.2650.21)

[-- Attachment #1 --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.1K --]

Let's see what exchange sends out.
 <<Timesheet 01-14-00.xls>>


[-- Attachment #2: Timesheet 01-14-00.xls --]
[-- Type: application/vnd.ms-excel, Encoding: base64, Size: 27K --]

[-- application/vnd.ms-excel is unsupported (use 'v' to view this part) --]

This is good on inbound mail.  I can save this attached file, and Star
Office can use this file as an Excel spreadsheet.  No problem.

I would like for mutt to do the same for outgoing mail, but when mutt sends
out an email with an attachment, let's say the same spreadsheet file, I get:

--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
     
Let mutt try sending out an attachment
 
--EVF5PPMfhYS0aIcm
Content-Type: application/excel
Content-Disposition: attachment; filename="Timesheet-01-14-00.xls"
Content-Transfer-Encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAJgAAAAAA
AAAAEAAA/v///wAAAAD+////AAAAACUAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
 
...

This is not good because I cannot extract this attached file back into its
original form. 

How do I configure mutt to send out email attachments the way Exchange,
Netscape, Eudora, and countless other MUA's do?

I thank you in advance for any push you can give me in the right direction.

-Mike Brolley

Reply via email to