comment on

You arent passing parameters around so its hard to see the actual code flow. Im betting its because $tmp2 isnt assigned a variable when &email is called. (Although the error message is on the face of it a bit confusing.) Ill look at making MIME::Lite a little more intelligent in this regard. But you might consider turning on strict and warnings. By the time you have cleaned up your code enough to make Perl stop whining I suspect this matter will be resolved. :-)

---
demerphq

_{Everybody remember the Gandhi quote?

First they ignore you, then they laugh at you, then they fight you, then you win.

Gentlemen and ladies, this newest leaked memo from Microsoft confirms that we are advancing through GandhiCon Three.}

In reply to Re: email attachments using multipart MIME format by demerphq
in thread email attachments using multipart MIME format by waiterm

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks