The Type is only a hint to the receiving MUA. You can specify foo/bar and everything is fine, as long as the receiver knows what to do with objects of that type.

You didn't specify your error symptoms beyond (…nothing happens…), but I would guess your MUA does not show you the generated "inline" Word document, which is an understandable decision.

You might try to attach the document by

$msg->attach(Type =>'application/msword', Path =>'test.doc', Disposition => 'attachment', );

instead.

At least the generated mail looks good to my eyes. Though it is a bit weird to send the main text base64-coded (i. e. BINARY). I would rather use Type => 'TEXT' there.


In reply to Re: Problem with Mime::lite and .doc files by pKai
in thread Problem with Mime::lite and .doc files by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.