• my_print() is my "special" debug print statement (only prints if debug enabled)
• $opts is my command line arguments hash $opts{'d'} was for debug :)
• $template was an HTML::Template object
• the script assumes that images to attach are local to its directory

my $msg = MIME::Lite->new(
                From =>     $from_address,
                To =>       $email_address,
                Subject =>  $subject,
                Type =>     'text/html',
                Data =>     $template->output()
        );

#we need to add any images to the mail if they exist
my $parser = HTML::LinkExtor->new();
$parser->parse($template->output());
foreach my $link ($parser->links){
    if ($link->[0] eq 'img'){
        my_print("Image found [".$link->[2]."] ");
        if ($link->[2] =~ /^https?:\/\//){
            my_print("Absolute! Ignored.\n");
        }else{
            my ($imgtype,$junk) = reverse split '\.',$link->[2];
            $imgtype =~ s/^jpg$/jpeg/; #propper mime name?

            if(open(TEST,"<".$link->[2])){
                my_print("Attaching\n");
                close(TEST);
                $msg->attach(Type =>'image/'.$imgtype,
                             Path    =>$link->[2],
                             Filename=>$link->[2],
                             #Disposition => 'inline');
                             Disposition => 'attachment');
            }else{
                my_print("Not found, Skipped!!\n");
            }
        }
    }
}

if($opts{'d'}){
    #debug mode
    my_print($msg->as_string);
}else{
    $msg->send();
}
[download]

Yes, we did look at MIME::Lite, although we didn't do anything as fancy as search the HTML for images. We just had a list of the images necessary, and did something like:


foreach $image (@htmlimages) {
    $msg->attach(
        Type => 'image/gif',
        Id   => $image,
        Path => "./$image"
    );
}
[download]

We had no trouble makeing HTML email with images, or email with attachments, or email with a text alternative, I simply couldn't find a way to combine all three.

The trick is the nesting a multipart/related inside a multipart/alternative inside a multipart/mixed message, while still having content parts outside the innermost section. If I had something like:

$msg->close(Type => multipart/related);
[download]

I could probably do it.

From Mail::Sender pod:

Please keep in mind though that it's not currently possible to create nested parts with Mail::Sender. If you need that level of control you should try MIME::Lite.

But, if you click on the Request Tracker icon, you will note in the correspondence that a function to compose multipart messages with attachments will be added in the future and for now is available in the beta version available (click on the attachment download button).

Hope this helps.