You have to take the place of pine sending your mail to a place that can handle it. The simplest way to do this is to locate the SMTP server on your network. Look in pines configuration it will point to a machine that exposes port 25. This machine will know how to route mail. It will expect connections from a variety of mail clients. You then use a perl module such as net::smtp as shown below.

use Net::SMTP;

my $from='foo@spangle.com';
my $to='someuser@host.com';
my $smtp= Net::SMTP->new('SMTPHOSTNAME',
                Timeout => 180);
$smtp->mail($from);
$smtp->to($to);
$smtp->data();
$smtp->datasend("YOUR MESSAGE");
$smtp->dataend();
$smtp->quit();
[download]

There is no reason to set mail up on the web server, as long as it can see a machine that can route the mail. If the webserver is in your DMZ and cannot see your internal SMTP server speak to your sysadmin and find out where the next hop is. Your local SMTP server will have to route all its mail out to another SMTP server to do the delivery. Unless you work for a v large company it is unlikely you do local mail routing. This second hop SMTP server will most likely be hosted within your ISP. --

Zigster

---

---

• 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.