Re: Problems with attachments sent elsewhere from mutt

2000-01-24 Thread Mikko Hänninen
Brolley, Michael <[EMAIL PROTECTED]> wrote on Mon, 24 Jan 2000: > [-- Type: application/vnd.ms-excel, Encoding: base64, Size: 27K --] So the incoming type is "application/vnd.ms-excel". > Content-Type: application/excel The outgoing MIME type is "application/excel". This is governed by the MIM

Re: Problems with attachments sent elsewhere from mutt

2000-01-24 Thread Byrial Jensen
On Mon, Jan 24, 2000 at 10:32:18 -0800, Duncan Watson wrote: > > The only current workaround for mutt users is to upgrade to version 1.1.1 or > 1.1.2 from the development branch which deliberately constructs quoted > boundaries. Also the latest stable versions of Mutt (1.0 and 1.0.1) always quot

Re: Problems with attachments sent elsewhere from mutt

2000-01-24 Thread Byrial Jensen
On Mon, Jan 24, 2000 at 12:18:50 -0500, Brolley, Michael wrote: > 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.1

Re: Problems with attachments sent elsewhere from mutt

2000-01-24 Thread Duncan Watson
On Mon, Jan 24, 2000 at 12:18:50PM -0500, Brolley, Michael wrote: > > 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 >