Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 79273 invoked from network); 31 May 2007 15:01:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 May 2007 15:01:31 -0000 Received: (qmail 19257 invoked by uid 500); 31 May 2007 15:01:34 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 19235 invoked by uid 500); 31 May 2007 15:01:34 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 19226 invoked by uid 99); 31 May 2007 15:01:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 May 2007 08:01:34 -0700 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jonesf11@gmail.com designates 209.85.132.249 as permitted sender) Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 May 2007 08:01:29 -0700 Received: by an-out-0708.google.com with SMTP id b15so83314ana for ; Thu, 31 May 2007 08:01:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nchsvToWtFK81Enx5dUgMmNxKH91zT5No/PEcM1AQutBu8l+et7QN2hZOOF/uczgeA2hqc0WQ/mrXdv2MIy7Mc1IPTuUUt/bOTu8Okso0OuIq7Pys7aSHf/Bblhjxvfs91zjIV5FzreSvn1WgI6gya9Wle/HgWq3wp0dkfhhY9k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k+wNLcjezPMHdlqTKTWNhfX8PnpdT6JtmBho8bNEM7Sp14wApGJq6PIkKMWv71DAHCL1mniKATQenttqysm9zeA1Z4IuaemGXNa6f9XFz5GsGVe98m8lQdsDFV4w0rS+LaPcDbXONv+PT+Ptrenlo3umagnrCpOuG/i13/a97Cc= Received: by 10.78.132.2 with SMTP id f2mr481578hud.1180623666041; Thu, 31 May 2007 08:01:06 -0700 (PDT) Received: by 10.78.57.6 with HTTP; Thu, 31 May 2007 08:01:05 -0700 (PDT) Message-ID: Date: Thu, 31 May 2007 10:01:06 -0500 From: "Frank Jones" To: modules-dev@httpd.apache.org Subject: Re: Sending email from an Apache content generator In-Reply-To: <20070531142617.6bd7157c@grimnir> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070531142617.6bd7157c@grimnir> X-Virus-Checked: Checked by ClamAV on apache.org On 5/31/07, Nick Kew wrote: > On Thu, 31 May 2007 08:17:13 -0500 > "Frank Jones" wrote: > > > What's a good way to send an email from a handler module? Is > > system("mail") OK or is there a better way? > > That'll work if you don't care about performance or security. Thanks, Nick. As it happens, I don't much care about performance in my particular case as this email will need to be sent rarely. I don't need to send an email on every request. I do, however, care about security. > To fix the security, hack up a perl/cgi prototype and fix > the issues that perl's taint checking complains of. To fix > performance, drop the fork. I should add some details. First, this is a pre-existing module in C, not new development. I need to look up a value in a database and then send a standard response email. There is no user input in the email so my security concerns are not what they might be otherwise. Second, I don't know anything at all about perl, although I suppose I could learn enough to solve my particular problem pretty easily. Can I chain a perl content generator behind my existing generator? If so, how?