Since you already have the headers and the MIME stuff done you don't need the power of Mail::Sender or MIME::Lite, but the low-levelness of Net::SMTP.

You should be able to change the To: address inside the email and then use just

use Net::SMTP;
$smtp = Net::SMTP->new('mailhost', Timeout => 60);
$smtp->mail($from_address);
$smtp->to($to_address);
$smtp->data();
$smtp->datasend($the_email_with_headers);
$smtp->dataend();
$smtp->quit;
[download]

Jenda

Ok, this is my standard rant about sending email from scripts, being a former system administrator of a mail system for 40.000+ users. If you are using this in anything else than a very trivial testing-only environment, 'mailhost' in Jenda's example above should be set to 'localhost' and you should run an SMTP daemon on your localhost. This is for reasons of error handling and redundancy. This is also true if you are running this in a cgi script on a webserver. You want to send the email as quickly as possible to be able continue with the cgi script, and sending the mail to localhost is a lot quicker than over the network.

If you are not able to run an SMTP daemon on localhost, you can use it the way Jenda describes above, if mailhost is close to you, and under your control. This is a riskier solution, and will not take advantage of MX records (think sendmail 'smarterhost' set to an MX record of mailhost1, mailhost2 & mailhost3 (or, as in my case, virusscanner1, virusscanner2, virusscanner3...)).

Anyway, always check that new creates a valid $smtp object. If you get undefined or something, the connection with mailhost could not be established, and you will have to deal with that.

Don't even think about sending the mail directly to the recipient's mailhost. You won't be able to deal with spooling, error handling, DNS resolving and cacheing, MX records etc. as efficiently as sendmail (or other MTA's).

Agreed. Thanks for writing this.

I took the code directly from Net::SMTP's docs and only deleted a few lines and changed it a little.

I think it's all too common that even the most well known modules miss any error checking in the examples included in the docs. :-(
Sorry I did not add it ;-)

Jenda

Thanks! This was exactly what I needed.

/J

still one more thing to experiment in.. the MIME::* family and the lightweight MIME::Lite.

I second that. Need to send mail with attachments? MIME::Lite. It's an automatism with me.

Update: As you don't have to construct a MIME message, but only have to resend the mail to another address, that doesn't really apply to this case, does it? OK, second choice: Net::SMTP. As somebody else already wrote: you don't have to alter anything in the message, not even the To: header. SMTP doesn't parse the message, either. The recipients are set using the to() method, the message itself, headers and body, can be sent using data().

You do need a live connection to an SMTP server, and it requires you to set some custom values, such as the server, your own domain, and so on. Most servers don't accept mail just from anybody or to anybody, so it could be tricky to get it to work. And it might pose some restrictions on the acceptable email address format.

Sending HTML Email is a script that may help. It should at least get you started.

--
hiseldl
What time is it? It's Camel Time!

The Mail::Box set of modules is very nice to do the kind of manipulations you want to perform, i.e. dissecting and reassembling emails.

Hope this helps, -gjb-

Actually Net::SMTP::Server is interesting and with practice on it you will be able to EHLO with the best of 'em.