#24841Defining a custom MailTransport which implements SwiftTransport
Description
Hi guys,
Wonderful work on 4.5 so far. I would like to request a feature (or rather behavior change) in the core mailer of TYPO3. I have attached a .diff file which changes the default case in the switch on $GLOBALS[‘TYPO3_CONF_VARS’][‘MAIL’][‘transport’] to detect a user-specified extension class implementing SwiftTransport – which is then able to act as the default mail transport for TYPO3.
The default behavior in this patch is to throw an exception on an unknown transport definition – the default maybe should be to use the default TYPO3 transport as in case “mail”.
This is as far as I can tell the way to go when replacing the basic way emails are sent, for example letting the administrator implement a SOAP-based offsite email sending solution; which is what I’m trying to do.
Patch created on 4.5rc2
(issue imported from #M17345)