Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73432
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: Gary Mort <garyamort@gmail.com>
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, "internals@lists.php.net"
 <internals@lists.php.net>
In-Reply-To: <5331C238.6050409@gmail.com>
References: <5330E319.5060302@gmail.com> <5330F2B2.1030201@sugarcrm.com>
	 <5331C238.6050409@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 25 Mar 2014 21:50:59 +0100
Message-ID: <1395780660.9365.606.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal: Mail Handling, feedback requested
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2014-03-25 at 13:51 -0400, Gary Mort wrote:
> Sending mail is just passing a stream of bytes to a stream.  That stream 
> could be an SMTP server, it can be an executable program, or it can be a 
> file.

Even that is not that easy, as Rasmus wrote.

> Frameworks are encouraged to subclass MailMessage and extend it's 
> functionality to suite their requirements - ie if they to synchronize 
> the header property with the recipients/from/subject properties they are 
> free to do so - there is no rule/standard saying they cannot.

So frameworks should still contain their own mail classes working
differently? So this is neither solving the sending problem nor the
"it's different everywhere" problem.

That aside I repeat my typical statement: This is better done in
userland, i.e. by PHP-FIG. It should only be in core when there are
obvious benefits. Userland gives more contributors, simpler debugging,
less issues for evolving the implementation, ...

johannes