Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:14221 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39367 invoked by uid 1010); 28 Dec 2004 16:13:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 39268 invoked from network); 28 Dec 2004 16:13:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Dec 2004 16:13:30 -0000 X-Host-Fingerprint: 64.233.170.199 rproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.170.199:52916] helo=rproxy.gmail.com) by pb1.pair.com (ecelerity HEAD (r3992M)) with SMTP id 2F/E7-27805-A2681D14 for ; Tue, 28 Dec 2004 11:13:30 -0500 Received: by rproxy.gmail.com with SMTP id r35so62384rna for ; Tue, 28 Dec 2004 08:13:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=MZpLP4IfuVaOWmDLJJ8oRcoJaX0jerZJ3bbbkoF8/87sC2306hDqYJ9UJgmQMYFjavSaxLkF+pjtVlX9kT/cfuxdTtOmuQFGTdWOxtSbSr1y9y81POWZHPPyH14twknpjzeE+MSpjlXGvcGrl1iRZVxRcyTJ+eiGnb2AZbXVi14= Received: by 10.38.67.76 with SMTP id p76mr188692rna; Tue, 28 Dec 2004 08:13:17 -0800 (PST) Received: by 10.38.81.38 with HTTP; Tue, 28 Dec 2004 08:13:17 -0800 (PST) Message-ID: <65df911e0412280813503bc5cb@mail.gmail.com> Date: Tue, 28 Dec 2004 23:13:17 +0700 Reply-To: Mikael Fern To: Olivier Beyssac Cc: internals@lists.php.net In-Reply-To: <20041228115825.GA25679@h2g2.staff.proxad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041228115825.GA25679@h2g2.staff.proxad.net> Subject: Re: [PHP-DEV] Patch to PHP mail() function From: mikaelf@gmail.com (Mikael Fern) in conjunction with this patch, i find that in ext/standard/mail.c, php_mail function doesn't check whether user supplies To in headers. so, if user uses To in first parameter and another identical To in headers, this leads into double email sending. is this the expected behaviour or some workaround needed on this? regards,