The advantage of using sendmail is
[1] a centralised MTA config.
[2] Graceful handling of problems and requeueing of messages if the SMTP
server specified by Net::SMTP would normally be down. eg automatic
resilience based on MX record rerouting can be nice.
Although in a mod_perl situation, I
At 14:02 27/10/1999 -0400, Gunther Birznieks wrote:
The advantage of using sendmail is
[1] a centralised MTA config.
[2] Graceful handling of problems and requeueing of messages if the SMTP
server specified by Net::SMTP would normally be down. eg automatic
resilience based on MX record
On Wed, 27 Oct 1999, Robin Berjon wrote:
At 14:02 27/10/1999 -0400, Gunther Birznieks wrote:
The advantage of using sendmail is
[1] a centralised MTA config.
[2] Graceful handling of problems and requeueing of messages if the SMTP
server specified by Net::SMTP would normally be down. eg
Hello, mod_perloids.
I'm having a gutfull of trouble sending mail under mod_perl. I'm doing
it by the books, to wit, the cookbook and the bigbirdie book, under rh
linux 5.2.
the code is
warn ("MAIL: Opening sendmail... path is \"".$sendmailpath."\"");
open (SENDMAIL, $sendmailpath)
Hello, mod_perloids.
I'm having a gutfull of trouble sending mail under mod_perl. I'm doing
it by the books, to wit, the cookbook and the bigbirdie book, under rh
linux 5.2.
the code is
warn ("MAIL: Opening sendmail... path is \"".$sendmailpath."\"");
open (SENDMAIL,
Dave Mee [EMAIL PROTECTED] writes:
Hello, mod_perloids.
I'm having a gutfull of trouble sending mail under mod_perl. I'm doing
it by the books, to wit, the cookbook and the bigbirdie book, under rh
linux 5.2.
the code is
warn ("MAIL: Opening sendmail... path is
On Tue, 26 Oct 1999, Stas Bekman wrote:
[...]
Other than that, why not to use Net::SMTP, which verifies each command and
you can arrange your code to die or warn on failure to send some field,
since it talks directly to the smtp server... take a look at the simple
send_mail() implemented
