[TYPO3-core] RFC #15998: Create a new API based on SwiftMailer to replace t3lib_htmlmail

[Ernesto Baschny [cron IT]]

Am 17.10.2010 11:00, schrieb Martin Kutschker:
> Am 16.10.2010 21:46, schrieb Ernesto Baschny [cron IT]:
>>
>> This is also meant to replace all direct calls to "mail()" and also "t3lib_utility_Mail" in future,
>> because of its flexibilty in sending mails.
>
> I would split the composition of mails and the sending of mails. Both tasks are related, but
> distinct. IMHO it makes sense to have a MIME composition class that let's you create a message,
> which - tata - is then passed to a news gateway. The point is that the "mail" class has no send()
> method, because it should not be concerned with sending of mails.

Exactly: the "send()" in our message class is just a helper because this 
is what "most folks" usually want to do with your created mail. This 
just creates a Mailer using the configured Transport.

But calling send() is optional, and you can also handle the created 
"message" your own way, or we might create other TYPO3 specific transports.

I will create a transport called "debug" which will just write all 
created mails to a certain text file, that might be useful when 
debugging mail sending routines.

Cheers,
Ernesto