Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Thursday 11 August 2005 2:29 pm, dan moylan wrote:
> the top header had this:
> ? Content-Transfer-Encoding: binary
> ? Content-Type: multipart/mixed; boundary="_----------=_112377843585800"
> then the body of the message had:
> ? Content-Disposition: inline
> ? Content-Transfer-Encoding: binary
> ? Content-Type: text
> i've changed both these encodings to 7bit, and the
> content-type of the second to text/plain (i think). ?does
> this make it visible to you?
> is there someplace to go to read up on this in some more of
> less succinct fashion?
This is much better. The following content type would be better, and 
eliminate the "multipart/mixed" garbage.  Multipart/mixed is what you want 
to do if you are sending attachments. 
Content-Type: text/plain;

Here are some URLs you can look at for MIME:
The above pages also have reference to the relevant RFCs if you like reading 

Jerry Feldman <gerald.feldman at>
Partner Technology Access Center (contractor) (PTAC-MA)
Hewlett-Packard Co.
550 King Street LKG2a-X2
Littleton, Ma. 01460

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /