[TASK] Load swiftmailer via composer 57/38057/2
authorBenjamin Mack <benni@typo3.org>
Mon, 23 Mar 2015 18:30:32 +0000 (19:30 +0100)
committerHelmut Hummel <helmut.hummel@typo3.org>
Mon, 23 Mar 2015 19:56:13 +0000 (20:56 +0100)
Instead of manually requiring the necessary
swiftmailer information, composer can be
utilized to be included in the regular autoloading
process.

At the same time, typo3/contrib/swiftmailer
is moved into typo3/contrib/vendor which is
maintained by composer.

TYPO3 Instances maintained with composer
will put the swiftmailer library into
Packages/Libraries/.

Resolves: #65950
Releases: master
Change-Id: Ibd57dddf74ed6643fd1f0816517e6bb36d22c3eb
Reviewed-on: http://review.typo3.org/38057
Reviewed-by: Helmut Hummel <helmut.hummel@typo3.org>
Tested-by: Helmut Hummel <helmut.hummel@typo3.org>
742 files changed:
composer.json
typo3/contrib/swiftmailer/CHANGES [deleted file]
typo3/contrib/swiftmailer/LICENSE [deleted file]
typo3/contrib/swiftmailer/README [deleted file]
typo3/contrib/swiftmailer/VERSION [deleted file]
typo3/contrib/swiftmailer/composer.json [deleted file]
typo3/contrib/swiftmailer/doc/headers.rst [deleted file]
typo3/contrib/swiftmailer/doc/help-resources.rst [deleted file]
typo3/contrib/swiftmailer/doc/including-the-files.rst [deleted file]
typo3/contrib/swiftmailer/doc/index.rst [deleted file]
typo3/contrib/swiftmailer/doc/installing.rst [deleted file]
typo3/contrib/swiftmailer/doc/introduction.rst [deleted file]
typo3/contrib/swiftmailer/doc/japanese.rst [deleted file]
typo3/contrib/swiftmailer/doc/messages.rst [deleted file]
typo3/contrib/swiftmailer/doc/overview.rst [deleted file]
typo3/contrib/swiftmailer/doc/plugins.rst [deleted file]
typo3/contrib/swiftmailer/doc/sending.rst [deleted file]
typo3/contrib/swiftmailer/doc/uml/Encoders.graffle [deleted file]
typo3/contrib/swiftmailer/doc/uml/Mime.graffle [deleted file]
typo3/contrib/swiftmailer/doc/uml/Transports.graffle [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Attachment.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/ArrayByteStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/FileByteStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/TemporaryFileByteStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/GenericFixedWidthReader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/UsAsciiReader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/Utf8Reader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReaderFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReaderFactory/SimpleCharacterReaderFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterStream/ArrayCharacterStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/CharacterStream/NgCharacterStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ConfigurableSpool.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/DependencyContainer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/DependencyException.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/EmbeddedFile.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Encoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Encoder/Base64Encoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Encoder/QpEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Encoder/Rfc2231Encoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Encoding.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/CommandEvent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/CommandListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/Event.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/EventDispatcher.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/EventListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/EventObject.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/ResponseEvent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/ResponseListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/SendEvent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/SendListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/SimpleEventDispatcher.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/TransportChangeEvent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/TransportChangeListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/TransportExceptionEvent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Events/TransportExceptionListener.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/FailoverTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/FileSpool.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/FileStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Filterable.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Image.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/InputByteStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/IoException.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache/ArrayKeyCache.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache/DiskKeyCache.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache/KeyCacheInputStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache/NullKeyCache.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/KeyCache/SimpleKeyCacheInputStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/LoadBalancedTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/MailTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mailer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mailer/ArrayRecipientIterator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mailer/RecipientIterator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/MemorySpool.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Message.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Attachment.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/CharsetObserver.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/Base64ContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/NativeQpContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/PlainContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/QpContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/QpContentEncoderProxy.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/RawContentEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/EmbeddedFile.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/EncodingObserver.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Grammar.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Header.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder/Base64HeaderEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder/QpHeaderEncoder.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/HeaderFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/HeaderSet.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/AbstractHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/DateHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/IdentificationHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/OpenDKIMHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/ParameterizedHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/PathHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Headers/UnstructuredHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/Message.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/MimeEntity.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/MimePart.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/ParameterizedHeader.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/SimpleHeaderFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/SimpleHeaderSet.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Mime/SimpleMimeEntity.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/MimePart.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/NullTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/OutputByteStream.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/AntiFloodPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/BandwidthMonitorPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Decorator/Replacements.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/DecoratorPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/ImpersonatePlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Logger.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/LoggerPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Loggers/ArrayLogger.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Loggers/EchoLogger.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/MessageLogger.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Pop/Pop3Connection.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Pop/Pop3Exception.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/PopBeforeSmtpPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/RedirectingPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Reporter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/ReporterPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Reporters/HitReporter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Reporters/HtmlReporter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Sleeper.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/ThrottlerPlugin.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Plugins/Timer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Preferences.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/ReplacementFilterFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/RfcComplianceException.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/SendmailTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/SignedMessage.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/BodySigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/DKIMSigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/DomainKeySigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/HeaderSigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/OpenDKIMSigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Signers/SMimeSigner.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/SmtpTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Spool.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/SpoolTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/StreamFilter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/StreamFilters/ByteArrayReplacementFilter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/StreamFilters/StringReplacementFilter.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/StreamFilters/StringReplacementFilterFactory.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/SwiftException.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/LoginAuthenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/PlainAuthenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/XOAuth2Authenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/AuthHandler.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/Esmtp/Authenticator.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/EsmtpHandler.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/FailoverTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/IoBuffer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/LoadBalancedTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/MailInvoker.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/MailTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/NullTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/SendmailTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/SimpleMailInvoker.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/SmtpAgent.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/SpoolTransport.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/TransportException.php [deleted file]
typo3/contrib/swiftmailer/lib/classes/Swift/Validate.php [deleted file]
typo3/contrib/swiftmailer/lib/dependency_maps/cache_deps.php [deleted file]
typo3/contrib/swiftmailer/lib/dependency_maps/message_deps.php [deleted file]
typo3/contrib/swiftmailer/lib/dependency_maps/mime_deps.php [deleted file]
typo3/contrib/swiftmailer/lib/dependency_maps/transport_deps.php [deleted file]
typo3/contrib/swiftmailer/lib/mime_types.php [deleted file]
typo3/contrib/swiftmailer/lib/preferences.php [deleted file]
typo3/contrib/swiftmailer/lib/swift_init.php [deleted file]
typo3/contrib/swiftmailer/lib/swift_required.php [deleted file]
typo3/contrib/swiftmailer/lib/swift_required_pear.php [deleted file]
typo3/contrib/swiftmailer/lib/swiftmailer_generate_mimes_config.php [deleted file]
typo3/contrib/swiftmailer/notes/APPS [deleted file]
typo3/contrib/swiftmailer/notes/CHARSETS [deleted file]
typo3/contrib/swiftmailer/notes/message.xml [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc0821.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc0822.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc1341.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc1521.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc1854.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2015.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2045.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2046.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2047.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2048.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2049.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2183.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2222.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2231.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2234.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2440.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2487.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2554.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2821.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc2822.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc3156.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc3676.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4505.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4616.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4870.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4871.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4880.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc4954.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/rfc5751.txt [deleted file]
typo3/contrib/swiftmailer/notes/rfc/whats_where.txt [deleted file]
typo3/contrib/swiftmailer/notes/smtp.txt [deleted file]
typo3/contrib/swiftmailer/phpunit.xml.dist [deleted file]
typo3/contrib/swiftmailer/tests/IdenticalBinaryConstraint.php [deleted file]
typo3/contrib/swiftmailer/tests/StreamCollector.php [deleted file]
typo3/contrib/swiftmailer/tests/SwiftMailerSmokeTestCase.php [deleted file]
typo3/contrib/swiftmailer/tests/SwiftMailerTestCase.php [deleted file]
typo3/contrib/swiftmailer/tests/_samples/charsets/iso-2022-jp/one.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/charsets/iso-8859-1/one.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/charsets/utf-8/one.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/charsets/utf-8/three.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/charsets/utf-8/two.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/dkim/dkim.test.priv [deleted file]
typo3/contrib/swiftmailer/tests/_samples/dkim/dkim.test.pub [deleted file]
typo3/contrib/swiftmailer/tests/_samples/files/data.txt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/files/textfile.zip [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/CA.srl [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/ca.crt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/ca.key [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/create-cert.sh [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/encrypt.crt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/encrypt.key [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/encrypt2.crt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/encrypt2.key [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/sign.crt [deleted file]
typo3/contrib/swiftmailer/tests/_samples/smime/sign.key [deleted file]
typo3/contrib/swiftmailer/tests/acceptance.conf.php.default [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/AttachmentAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/ByteStream/FileByteStreamAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/CharacterReaderFactory/SimpleCharacterReaderFactoryAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/DependencyContainerAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/EmbeddedFileAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Encoder/Base64EncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Encoder/QpEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Encoder/Rfc2231EncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/EncodingAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/KeyCache/ArrayKeyCacheAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/KeyCache/DiskKeyCacheAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/MessageAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/AttachmentAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/Base64ContentEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/NativeQpContentEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/PlainContentEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/QpContentEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/EmbeddedFileAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/HeaderEncoder/Base64HeaderEncoderAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/MimePartAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Mime/SimpleMessageAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/MimePartAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/AbstractStreamBufferAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/BasicSocketAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/ProcessAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/SocketTimeoutTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/SslSocketAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/TlsSocketAcceptanceTest.php [deleted file]
typo3/contrib/swiftmailer/tests/bootstrap.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug111Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug118Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug206Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug274Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug34Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug35Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug38Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug51Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug71Test.php [deleted file]
typo3/contrib/swiftmailer/tests/bug/Swift/Bug76Test.php [deleted file]
typo3/contrib/swiftmailer/tests/fixtures/EsmtpTransportFixture.php [deleted file]
typo3/contrib/swiftmailer/tests/fixtures/MimeEntityFixture.php [deleted file]
typo3/contrib/swiftmailer/tests/smoke.conf.php.default [deleted file]
typo3/contrib/swiftmailer/tests/smoke/Swift/Smoke/AttachmentSmokeTest.php [deleted file]
typo3/contrib/swiftmailer/tests/smoke/Swift/Smoke/BasicSmokeTest.php [deleted file]
typo3/contrib/swiftmailer/tests/smoke/Swift/Smoke/HtmlWithAttachmentSmokeTest.php [deleted file]
typo3/contrib/swiftmailer/tests/smoke/Swift/Smoke/InternationalSmokeTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/ByteStream/ArrayByteStreamTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/CharacterReader/GenericFixedWidthReaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/CharacterReader/UsAsciiReaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/CharacterReader/Utf8ReaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/CharacterStream/ArrayCharacterStreamTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/DependencyContainerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Encoder/Base64EncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Encoder/QpEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Encoder/Rfc2231EncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/CommandEventTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/EventObjectTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/ResponseEventTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/SendEventTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/SimpleEventDispatcherTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/TransportChangeEventTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Events/TransportExceptionEventTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/KeyCache/ArrayKeyCacheTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/KeyCache/SimpleKeyCacheInputStreamTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mailer/ArrayRecipientIteratorTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/MailerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/AbstractMimeEntityTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/AttachmentTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/Base64ContentEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/PlainContentEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/QpContentEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/EmbeddedFileTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/HeaderEncoder/Base64HeaderEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/HeaderEncoder/QpHeaderEncoderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/DateHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/IdentificationHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/MailboxHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/ParameterizedHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/PathHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/Headers/UnstructuredHeaderTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/MimePartTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/SimpleHeaderFactoryTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/SimpleHeaderSetTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/SimpleMessageTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Mime/SimpleMimeEntityTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/AntiFloodPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/BandwidthMonitorPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/DecoratorPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/LoggerPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/Loggers/ArrayLoggerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/Loggers/EchoLoggerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/PopBeforeSmtpPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/RedirectingPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/ReporterPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/Reporters/HitReporterTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/Reporters/HtmlReporterTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Plugins/ThrottlerPluginTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Signers/DKIMSignerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Signers/OpenDKIMSignerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Signers/SMimeSignerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/StreamFilters/ByteArrayReplacementFilterTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/StreamFilters/StringReplacementFilterFactoryTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/StreamFilters/StringReplacementFilterTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/AbstractSmtpEventSupportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/AbstractSmtpTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/CramMd5AuthenticatorTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/LoginAuthenticatorTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/NTLMAuthenticatorTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/PlainAuthenticatorTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/Esmtp/AuthHandlerTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/EsmtpTransport/ExtensionSupportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/EsmtpTransportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/FailoverTransportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/LoadBalancedTransportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/MailTransportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/SendmailTransportTest.php [deleted file]
typo3/contrib/swiftmailer/tests/unit/Swift/Transport/StreamBufferTest.php [deleted file]
typo3/contrib/vendor/autoload.php
typo3/contrib/vendor/composer/autoload_files.php [new file with mode: 0644]
typo3/contrib/vendor/composer/autoload_real.php
typo3/contrib/vendor/helhum/class-alias-loader/composer.json
typo3/contrib/vendor/swiftmailer/swiftmailer/.gitattributes [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/.gitignore [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/.travis.yml [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/CHANGES [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/LICENSE [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/README [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/VERSION [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/composer.json [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/headers.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/help-resources.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/including-the-files.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/index.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/installing.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/introduction.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/japanese.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/messages.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/overview.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/plugins.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/sending.rst [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/uml/Encoders.graffle [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/uml/Mime.graffle [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/doc/uml/Transports.graffle [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Attachment.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/ArrayByteStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/FileByteStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ByteStream/TemporaryFileByteStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReader/GenericFixedWidthReader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReader/UsAsciiReader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReader/Utf8Reader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReaderFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterReaderFactory/SimpleCharacterReaderFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterStream/ArrayCharacterStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/CharacterStream/NgCharacterStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ConfigurableSpool.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/DependencyContainer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/DependencyException.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/EmbeddedFile.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Encoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Encoder/Base64Encoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Encoder/QpEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Encoder/Rfc2231Encoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Encoding.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/CommandEvent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/CommandListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/Event.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/EventDispatcher.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/EventListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/EventObject.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/ResponseEvent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/ResponseListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/SendEvent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/SendListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/SimpleEventDispatcher.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/TransportChangeEvent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/TransportChangeListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/TransportExceptionEvent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Events/TransportExceptionListener.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/FailoverTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/FileSpool.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/FileStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Filterable.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Image.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/InputByteStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/IoException.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache/ArrayKeyCache.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache/DiskKeyCache.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache/KeyCacheInputStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache/NullKeyCache.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/KeyCache/SimpleKeyCacheInputStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/LoadBalancedTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/MailTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer/ArrayRecipientIterator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer/RecipientIterator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/MemorySpool.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Message.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Attachment.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/CharsetObserver.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/Base64ContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/NativeQpContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/PlainContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/QpContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/QpContentEncoderProxy.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ContentEncoder/RawContentEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/EmbeddedFile.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/EncodingObserver.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Grammar.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Header.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder/Base64HeaderEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/HeaderEncoder/QpHeaderEncoder.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/HeaderFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/HeaderSet.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/AbstractHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/DateHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/IdentificationHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/OpenDKIMHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/ParameterizedHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/PathHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/UnstructuredHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Message.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/MimeEntity.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/MimePart.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/ParameterizedHeader.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleHeaderFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleHeaderSet.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMessage.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/SimpleMimeEntity.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/MimePart.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/NullTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/OutputByteStream.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/AntiFloodPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/BandwidthMonitorPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Decorator/Replacements.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/DecoratorPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/ImpersonatePlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Logger.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/LoggerPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Loggers/ArrayLogger.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Loggers/EchoLogger.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/MessageLogger.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Pop/Pop3Connection.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Pop/Pop3Exception.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/PopBeforeSmtpPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/RedirectingPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Reporter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/ReporterPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Reporters/HitReporter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Reporters/HtmlReporter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Sleeper.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/ThrottlerPlugin.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Plugins/Timer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Preferences.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/ReplacementFilterFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/RfcComplianceException.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/SendmailTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/SignedMessage.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/BodySigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/DKIMSigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/DomainKeySigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/HeaderSigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/OpenDKIMSigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Signers/SMimeSigner.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/SmtpTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Spool.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/SpoolTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/StreamFilter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/StreamFilters/ByteArrayReplacementFilter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/StreamFilters/StringReplacementFilter.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/StreamFilters/StringReplacementFilterFactory.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/SwiftException.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/LoginAuthenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/NTLMAuthenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/PlainAuthenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/XOAuth2Authenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/AuthHandler.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Authenticator.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpHandler.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/FailoverTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/IoBuffer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/LoadBalancedTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/MailInvoker.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/MailTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/NullTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SendmailTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SimpleMailInvoker.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SmtpAgent.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SpoolTransport.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/TransportException.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Validate.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/dependency_maps/cache_deps.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/dependency_maps/message_deps.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/dependency_maps/mime_deps.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/dependency_maps/transport_deps.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/mime_types.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/preferences.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/swift_init.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/swift_required.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/swift_required_pear.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/lib/swiftmailer_generate_mimes_config.php [new file with mode: 0755]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/APPS [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/CHARSETS [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/message.xml [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc0821.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc0822.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc1341.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc1521.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc1854.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2015.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2045.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2046.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2047.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2048.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2049.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2183.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2222.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2231.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2234.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2440.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2487.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2554.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2821.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc2822.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc3156.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc3676.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4505.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4616.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4870.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4871.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4880.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc4954.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/rfc5751.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/rfc/whats_where.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/notes/smtp.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/phpunit.xml.dist [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/IdenticalBinaryConstraint.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/StreamCollector.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/SwiftMailerSmokeTestCase.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/SwiftMailerTestCase.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/charsets/iso-2022-jp/one.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/charsets/iso-8859-1/one.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/charsets/utf-8/one.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/charsets/utf-8/three.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/charsets/utf-8/two.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/dkim/dkim.test.priv [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/dkim/dkim.test.pub [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/files/data.txt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/files/textfile.zip [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/CA.srl [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/ca.crt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/ca.key [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/create-cert.sh [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/encrypt.crt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/encrypt.key [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/encrypt2.crt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/encrypt2.key [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/sign.crt [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/_samples/smime/sign.key [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance.conf.php.default [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/AttachmentAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/ByteStream/FileByteStreamAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/CharacterReaderFactory/SimpleCharacterReaderFactoryAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/DependencyContainerAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/EmbeddedFileAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Encoder/Base64EncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Encoder/QpEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Encoder/Rfc2231EncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/EncodingAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/KeyCache/ArrayKeyCacheAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/KeyCache/DiskKeyCacheAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/MessageAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/AttachmentAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/Base64ContentEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/NativeQpContentEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/PlainContentEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/ContentEncoder/QpContentEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/EmbeddedFileAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/HeaderEncoder/Base64HeaderEncoderAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/MimePartAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Mime/SimpleMessageAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/MimePartAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/AbstractStreamBufferAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/BasicSocketAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/ProcessAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/SocketTimeoutTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/SslSocketAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/acceptance/Swift/Transport/StreamBuffer/TlsSocketAcceptanceTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bootstrap.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug111Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug118Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug206Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug274Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug34Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug35Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug38Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug51Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug71Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/bug/Swift/Bug76Test.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/fixtures/EsmtpTransportFixture.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/fixtures/MimeEntityFixture.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/smoke.conf.php.default [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/smoke/Swift/Smoke/AttachmentSmokeTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/smoke/Swift/Smoke/BasicSmokeTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/smoke/Swift/Smoke/HtmlWithAttachmentSmokeTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/smoke/Swift/Smoke/InternationalSmokeTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/ByteStream/ArrayByteStreamTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/CharacterReader/GenericFixedWidthReaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/CharacterReader/UsAsciiReaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/CharacterReader/Utf8ReaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/CharacterStream/ArrayCharacterStreamTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/DependencyContainerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Encoder/Base64EncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Encoder/QpEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Encoder/Rfc2231EncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/CommandEventTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/EventObjectTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/ResponseEventTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/SendEventTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/SimpleEventDispatcherTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/TransportChangeEventTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Events/TransportExceptionEventTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/KeyCache/ArrayKeyCacheTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/KeyCache/SimpleKeyCacheInputStreamTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mailer/ArrayRecipientIteratorTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/MailerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/AbstractMimeEntityTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/AttachmentTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/Base64ContentEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/PlainContentEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/ContentEncoder/QpContentEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/EmbeddedFileTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/HeaderEncoder/Base64HeaderEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/HeaderEncoder/QpHeaderEncoderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/DateHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/IdentificationHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/MailboxHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/ParameterizedHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/PathHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/Headers/UnstructuredHeaderTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/MimePartTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/SimpleHeaderFactoryTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/SimpleHeaderSetTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/SimpleMessageTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Mime/SimpleMimeEntityTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/AntiFloodPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/BandwidthMonitorPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/DecoratorPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/LoggerPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/Loggers/ArrayLoggerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/Loggers/EchoLoggerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/PopBeforeSmtpPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/RedirectingPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/ReporterPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/Reporters/HitReporterTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/Reporters/HtmlReporterTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Plugins/ThrottlerPluginTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Signers/DKIMSignerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Signers/OpenDKIMSignerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Signers/SMimeSignerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/StreamFilters/ByteArrayReplacementFilterTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/StreamFilters/StringReplacementFilterFactoryTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/StreamFilters/StringReplacementFilterTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/AbstractSmtpEventSupportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/AbstractSmtpTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/CramMd5AuthenticatorTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/LoginAuthenticatorTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/NTLMAuthenticatorTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/Esmtp/Auth/PlainAuthenticatorTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/Esmtp/AuthHandlerTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/EsmtpTransport/ExtensionSupportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/EsmtpTransportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/FailoverTransportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/LoadBalancedTransportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/MailTransportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/SendmailTransportTest.php [new file with mode: 0644]
typo3/contrib/vendor/swiftmailer/swiftmailer/tests/unit/Swift/Transport/StreamBufferTest.php [new file with mode: 0644]
typo3/sysext/core/Classes/Mail/MailMessage.php
typo3/sysext/core/Classes/Mail/Mailer.php

index 6310f91..13e68be 100644 (file)
@@ -36,6 +36,7 @@
                "ext-pcre": "*",
                "ext-session": "*",
                "ext-xml": "*",
+               "swiftmailer/swiftmailer": "5.2.1",
                "helhum/class-alias-loader": "1.1.*@dev",
                "typo3/cms-composer-installers": "1.1.*@dev"
        },
diff --git a/typo3/contrib/swiftmailer/CHANGES b/typo3/contrib/swiftmailer/CHANGES
deleted file mode 100644 (file)
index c78c463..0000000
+++ /dev/null
@@ -1,170 +0,0 @@
-Changelog
-=========
-
-5.2.1 (2014-06-13)
-------------------
-
- * SECURITY FIX: fixed CLI escaping when using sendmail as a transport
-
-   Prior to 5.2.1, the sendmail transport (Swift_Transport_SendmailTransport)
-   was vulnerable to an arbitrary shell execution if the "From" header came
-   from a non-trusted source and no "Return-Path" is configured.
-
- * fixed parameter in DKIMSigner
- * fixed compatibility with PHP < 5.4
-
-5.2.0 (2014-05-08)
-------------------
-
- * fixed Swift_ByteStream_FileByteStream::read() to match to the specification
- * fixed from-charset and to-charset arguments in mbstring_convert_encoding() usages
- * fixed infinite loop in StreamBuffer
- * fixed NullTransport to return the number of ignored emails instead of 0
- * Use phpunit and mockery for unit testing (realityking)
-
-5.1.0 (2014-03-18)
-------------------
-
- * fixed data writing to stream when sending large messages
- * added support for libopendkim (https://github.com/xdecock/php-opendkim)
- * merged SignedMessage and Message
- * added Gmail XOAuth2 authentication
- * updated the list of known mime types
- * added NTLM authentication
-
-5.0.3 (2013-12-03)
-------------------
-
- * fixed double-dot bug
- * fixed DKIM signer
-
-5.0.2 (2013-08-30)
-------------------
-
- * handled correct exception type while reading IoBuffer output
-
-5.0.1 (2013-06-17)
-------------------
-
- * changed the spool to only start the transport when a mail has to be sent
- * fixed compatibility with PHP 5.2
- * fixed LICENSE file
-
-5.0.0 (2013-04-30)
-------------------
-
- * changed the license from LGPL to MIT
-
-4.3.1 (2013-04-11)
-------------------
-
- * removed usage of the native QP encoder when the charset is not UTF-8
- * fixed usage of uniqid to avoid collisions
- * made a performance improvement when tokenizing large headers
- * fixed usage of the PHP native QP encoder on PHP 5.4.7+
-
-4.3.0 (2013-01-08)
-------------------
-
- * made the temporary directory configurable via the TMPDIR env variable
- * added S/MIME signer and encryption support
-
-4.2.2 (2012-10-25)
-------------------
-
- * added the possibility to throttle messages per second in ThrottlerPlugin (mostly for Amazon SES)
- * switched mime.qpcontentencoder to automatically use the PHP native encoder on PHP 5.4.7+
- * allowed specifying a whitelist with regular expressions in RedirectingPlugin
-
-4.2.1 (2012-07-13)
-------------------
-
- * changed the coding standards to PSR-1/2
- * fixed issue with autoloading
- * added NativeQpContentEncoder to enhance performance (for PHP 5.3+)
-
-4.2.0 (2012-06-29)
-------------------
-
- * added documentation about how to use the Japanese support introduced in 4.1.8
- * added a way to override the default configuration in a lazy way
- * changed the PEAR init script to lazy-load the initialization
- * fixed a bug when calling Swift_Preferences before anything else (regression introduced in 4.1.8)
-
-4.1.8 (2012-06-17)
-------------------
-
- * added Japanese iso-2022-jp support
- * changed the init script to lazy-load the initialization
- * fixed docblocks (@id) which caused some problems with libraries parsing the dobclocks
- * fixed Swift_Mime_Headers_IdentificationHeader::setId() when passed an array of ids
- * fixed encoding of email addresses in headers
- * added replacements setter to the Decorator plugin
-
-4.1.7 (2012-04-26)
-------------------
-
- * fixed QpEncoder safeMapShareId property
-
-4.1.6 (2012-03-23)
-------------------
-
- * reduced the size of serialized Messages
-
-4.1.5 (2012-01-04)
-------------------
-
- * enforced Swift_Spool::queueMessage() to return a Boolean
- * made an optimization to the memory spool: start the transport only when required
- * prevented stream_socket_client() from generating an error and throw a Swift_TransportException instead
- * fixed a PHP warning when calling to mail() when safe_mode is off
- * many doc tweaks
-
-4.1.4 (2011-12-16)
-------------------
-
- * added a memory spool (Swift_MemorySpool)
- * fixed too many opened files when sending emails with attachments
-
-4.1.3 (2011-10-27)
-------------------
-
- * added STARTTLS support
- * added missing @return tags on fluent methods
- * added a MessageLogger plugin that logs all sent messages
- * added composer.json
-
-4.1.2 (2011-09-13)
-------------------
-
- * fixed wrong detection of magic_quotes_runtime
- * fixed fatal errors when no To or Subject header has been set
- * fixed charset on parameter header continuations
- * added documentation about how to install Swiftmailer from the PEAR channel
- * fixed various typos and markup problem in the documentation
- * fixed warning when cache directory does not exist
- * fixed "slashes are escaped" bug
- * changed require_once() to require() in autoload
-
-4.1.1 (2011-07-04)
-------------------
-
- * added missing file in PEAR package
-
-4.1.0 (2011-06-30)
-------------------
-
- * documentation has been converted to ReST
-
-4.1.0 RC1 (2011-06-17)
-----------------------
-
-New features:
-
- * changed the Decorator Plugin to allow replacements in all headers
- * added Swift_Mime_Grammar and Swift_Validate to validate an email address
- * modified the autoloader to lazy-initialize Swiftmailer
- * removed Swift_Mailer::batchSend()
- * added NullTransport
- * added new plugins: RedirectingPlugin and ImpersonatePlugin
- * added a way to send messages asynchronously (Spool)
diff --git a/typo3/contrib/swiftmailer/LICENSE b/typo3/contrib/swiftmailer/LICENSE
deleted file mode 100644 (file)
index 674bb2a..0000000
+++ /dev/null
@@ -1,19 +0,0 @@
-Copyright (c) 2013 Fabien Potencier
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is furnished
-to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
diff --git a/typo3/contrib/swiftmailer/README b/typo3/contrib/swiftmailer/README
deleted file mode 100644 (file)
index eb5f8bc..0000000
+++ /dev/null
@@ -1,16 +0,0 @@
-Swift Mailer
-------------
-
-Swift Mailer is a component based mailing solution for PHP 5.
-It is released under the MIT license.
-
-Homepage:      http://swiftmailer.org
-Documentation: http://swiftmailer.org/docs
-Mailing List:  http://groups.google.com/group/swiftmailer
-Bugs:          https://github.com/swiftmailer/swiftmailer/issues
-Repository:    https://github.com/swiftmailer/swiftmailer
-
-Swift Mailer is highly object-oriented by design and lends itself
-to use in complex web application with a great deal of flexibility.
-
-For full details on usage, see the documentation.
diff --git a/typo3/contrib/swiftmailer/VERSION b/typo3/contrib/swiftmailer/VERSION
deleted file mode 100644 (file)
index 064e3a3..0000000
+++ /dev/null
@@ -1 +0,0 @@
-Swift-5.2.1
diff --git a/typo3/contrib/swiftmailer/composer.json b/typo3/contrib/swiftmailer/composer.json
deleted file mode 100644 (file)
index b76b7a8..0000000
+++ /dev/null
@@ -1,31 +0,0 @@
-{
-    "name": "swiftmailer/swiftmailer",
-    "type": "library",
-    "description": "Swiftmailer, free feature-rich PHP mailer",
-    "keywords": ["mail","mailer"],
-    "homepage": "http://swiftmailer.org",
-    "license": "MIT",
-    "authors": [
-        {
-            "name": "Chris Corbyn"
-        },
-        {
-            "name": "Fabien Potencier",
-            "email": "fabien@symfony.com"
-        }
-    ],
-    "require": {
-        "php": ">=5.2.4"
-    },
-    "require-dev": {
-        "mockery/mockery": "~0.9.1"
-    },
-    "autoload": {
-        "files": ["lib/swift_required.php"]
-    },
-    "extra": {
-        "branch-alias": {
-            "dev-master": "5.2-dev"
-        }
-    }
-}
diff --git a/typo3/contrib/swiftmailer/doc/headers.rst b/typo3/contrib/swiftmailer/doc/headers.rst
deleted file mode 100644 (file)
index 6aec23f..0000000
+++ /dev/null
@@ -1,742 +0,0 @@
-Message Headers
-===============
-
-Sometimes you'll want to add your own headers to a message or modify/remove
-headers that are already present. You work with the message's HeaderSet to do
-this.
-
-Header Basics
--------------
-
-All MIME entities in Swift Mailer -- including the message itself --
-store their headers in a single object called a HeaderSet. This HeaderSet is
-retrieved with the ``getHeaders()`` method.
-
-As mentioned in the previous chapter, everything that forms a part of a message
-in Swift Mailer is a MIME entity that is represented by an instance of
-``Swift_Mime_MimeEntity``. This includes -- most notably -- the message object
-itself, attachments, MIME parts and embedded images. Each of these MIME entities
-consists of a body and a set of headers that describe the body.
-
-For all of the "standard" headers in these MIME entities, such as the
-``Content-Type``, there are named methods for working with them, such as
-``setContentType()`` and ``getContentType()``. This is because headers are a
-moderately complex area of the library. Each header has a slightly different
-required structure that it must meet in order to comply with the standards that
-govern email (and that are checked by spam blockers etc).
-
-You fetch the HeaderSet from a MIME entity like so:
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    // Fetch the HeaderSet from a Message object
-    $headers = $message->getHeaders();
-
-    $attachment = Swift_Attachment::fromPath('document.pdf');
-
-    // Fetch the HeaderSet from an attachment object
-    $headers = $attachment->getHeaders();
-
-The job of the HeaderSet is to contain and manage instances of Header objects.
-Depending upon the MIME entity the HeaderSet came from, the contents of the
-HeaderSet will be different, since an attachment for example has a different
-set of headers to those in a message.
-
-You can find out what the HeaderSet contains with a quick loop, dumping out
-the names of the headers:
-
-.. code-block:: php
-
-    foreach ($headers->getAll() as $header) {
-      printf("%s<br />\n", $header->getFieldName());
-    }
-
-    /*
-    Content-Transfer-Encoding
-    Content-Type
-    MIME-Version
-    Date
-    Message-ID
-    From
-    Subject
-    To
-    */
-
-You can also dump out the rendered HeaderSet by calling its ``toString()``
-method:
-
-.. code-block:: php
-
-    echo $headers->toString();
-
-    /*
-    Message-ID: <1234869991.499a9ee7f1d5e@swift.generated>
-    Date: Tue, 17 Feb 2009 22:26:31 +1100
-    Subject: Awesome subject!
-    From: sender@example.org
-    To: recipient@example.org
-    MIME-Version: 1.0
-    Content-Type: text/plain; charset=utf-8
-    Content-Transfer-Encoding: quoted-printable
-    */
-
-Where the complexity comes in is when you want to modify an existing header.
-This complexity comes from the fact that each header can be of a slightly
-different type (such as a Date header, or a header that contains email
-addresses, or a header that has key-value parameters on it!). Each header in the
-HeaderSet is an instance of ``Swift_Mime_Header``. They all have common
-functionality, but knowing exactly what type of header you're working with will
-allow you a little more control.
-
-You can determine the type of header by comparing the return value of its
-``getFieldType()`` method with the constants ``TYPE_TEXT``,
-``TYPE_PARAMETERIZED``, ``TYPE_DATE``, ``TYPE_MAILBOX``, ``TYPE_ID`` and
-``TYPE_PATH`` which are defined in ``Swift_Mime_Header``.
-
-
-.. code-block:: php
-
-    foreach ($headers->getAll() as $header) {
-      switch ($header->getFieldType()) {
-        case Swift_Mime_Header::TYPE_TEXT: $type = 'text';
-          break;
-        case Swift_Mime_Header::TYPE_PARAMETERIZED: $type = 'parameterized';
-          break;
-        case Swift_Mime_Header::TYPE_MAILBOX: $type = 'mailbox';
-          break;
-        case Swift_Mime_Header::TYPE_DATE: $type = 'date';
-          break;
-        case Swift_Mime_Header::TYPE_ID: $type = 'ID';
-          break;
-        case Swift_Mime_Header::TYPE_PATH: $type = 'path';
-          break;
-      }
-      printf("%s: is a %s header<br />\n", $header->getFieldName(), $type);
-    }
-
-    /*
-    Content-Transfer-Encoding: is a text header
-    Content-Type: is a parameterized header
-    MIME-Version: is a text header
-    Date: is a date header
-    Message-ID: is a ID header
-    From: is a mailbox header
-    Subject: is a text header
-    To: is a mailbox header
-    */
-
-Headers can be removed from the set, modified within the set, or added to the
-set.
-
-The following sections show you how to work with the HeaderSet and explain the
-details of each implementation of ``Swift_Mime_Header`` that may
-exist within the HeaderSet.
-
-Header Types
-------------
-
-Because all headers are modeled on different data (dates, addresses, text!)
-there are different types of Header in Swift Mailer. Swift Mailer attempts to
-categorize all possible MIME headers into more general groups, defined by a
-small number of classes.
-
-Text Headers
-~~~~~~~~~~~~
-
-Text headers are the simplest type of Header. They contain textual information
-with no special information included within it -- for example the Subject
-header in a message.
-
-There's nothing particularly interesting about a text header, though it is
-probably the one you'd opt to use if you need to add a custom header to a
-message. It represents text just like you'd think it does. If the text
-contains characters that are not permitted in a message header (such as new
-lines, or non-ascii characters) then the header takes care of encoding the
-text so that it can be used.
-
-No header -- including text headers -- in Swift Mailer is vulnerable to
-header-injection attacks. Swift Mailer breaks any attempt at header injection by
-encoding the dangerous data into a non-dangerous form.
-
-It's easy to add a new text header to a HeaderSet. You do this by calling the
-HeaderSet's ``addTextHeader()`` method.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addTextHeader('Your-Header-Name', 'the header value');
-
-Changing the value of an existing text header is done by calling it's
-``setValue()`` method.
-
-.. code-block:: php
-
-    $subject = $message->getHeaders()->get('Subject');
-
-    $subject->setValue('new subject');
-
-When output via ``toString()``, a text header produces something like the
-following:
-
-.. code-block:: php
-
-    $subject = $message->getHeaders()->get('Subject');
-
-    $subject->setValue('amazing subject line');
-
-    echo $subject->toString();
-
-    /*
-
-    Subject: amazing subject line
-
-    */
-
-If the header contains any characters that are outside of the US-ASCII range
-however, they will be encoded. This is nothing to be concerned about since
-mail clients will decode them back.
-
-.. code-block:: php
-
-    $subject = $message->getHeaders()->get('Subject');
-
-    $subject->setValue('contains – dash');
-
-    echo $subject->toString();
-
-    /*
-
-    Subject: contains =?utf-8?Q?=E2=80=93?= dash
-
-    */
-
-Parameterized Headers
-~~~~~~~~~~~~~~~~~~~~~
-
-Parameterized headers are text headers that contain key-value parameters
-following the textual content. The Content-Type header of a message is a
-parameterized header since it contains charset information after the content
-type.
-
-The parameterized header type is a special type of text header. It extends the
-text header by allowing additional information to follow it. All of the methods
-from text headers are available in addition to the methods described here.
-
-Adding a parameterized header to a HeaderSet is done by using the
-``addParameterizedHeader()`` method which takes a text value like
-``addTextHeader()`` but it also accepts an associative array of
-key-value parameters.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addParameterizedHeader(
-      'Header-Name', 'header value',
-      array('foo' => 'bar')
-      );
-
-To change the text value of the header, call it's ``setValue()`` method just as
-you do with text headers.
-
-To change the parameters in the header, call the header's ``setParameters()``
-method or the ``setParameter()`` method (note the pluralization).
-
-.. code-block:: php
-
-    $type = $message->getHeaders()->get('Content-Type');
-
-    // setParameters() takes an associative array
-    $type->setParameters(array(
-      'name' => 'file.txt',
-      'charset' => 'iso-8859-1'
-      ));
-
-    // setParameter() takes two args for $key and $value
-    $type->setParameter('charset', 'iso-8859-1');
-
-When output via ``toString()``, a parameterized header produces something like
-the following:
-
-.. code-block:: php
-
-    $type = $message->getHeaders()->get('Content-Type');
-
-    $type->setValue('text/html');
-    $type->setParameter('charset', 'utf-8');
-
-    echo $type->toString();
-
-    /*
-
-    Content-Type: text/html; charset=utf-8
-
-    */
-
-If the header contains any characters that are outside of the US-ASCII range
-however, they will be encoded, just like they are for text headers. This is
-nothing to be concerned about since mail clients will decode them back.
-Likewise, if the parameters contain any non-ascii characters they will be
-encoded so that they can be transmitted safely.
-
-.. code-block:: php
-
-    $attachment = Swift_Attachment::newInstance();
-
-    $disp = $attachment->getHeaders()->get('Content-Disposition');
-
-    $disp->setValue('attachment');
-    $disp->setParameter('filename', 'report–may.pdf');
-
-    echo $disp->toString();
-
-    /*
-
-    Content-Disposition: attachment; filename*=utf-8''report%E2%80%93may.pdf
-
-    */
-
-Date Headers
-~~~~~~~~~~~~
-
-Date headers contains an RFC 2822 formatted date (i.e. what PHP's ``date('r')``
-returns). They are used anywhere a date or time is needed to be presented as a
-message header.
-
-The data on which a date header is modeled is simply a UNIX timestamp such as
-that returned by ``time()`` or ``strtotime()``.  The timestamp is used to create
-a correctly structured RFC 2822 formatted date such as
-``Tue, 17 Feb 2009 22:26:31 +1100``.
-
-The obvious place this header type is used is in the ``Date:`` header of the
-message itself.
-
-It's easy to add a new date header to a HeaderSet.  You do this by calling
-the HeaderSet's ``addDateHeader()`` method.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addDateHeader('Your-Header-Name', strtotime('3 days ago'));
-
-Changing the value of an existing date header is done by calling it's
-``setTimestamp()`` method.
-
-.. code-block:: php
-
-    $date = $message->getHeaders()->get('Date');
-
-    $date->setTimestamp(time());
-
-When output via ``toString()``, a date header produces something like the
-following:
-
-.. code-block:: php
-
-    $date = $message->getHeaders()->get('Date');
-
-    echo $date->toString();
-
-    /*
-
-    Date: Wed, 18 Feb 2009 13:35:02 +1100
-
-    */
-
-Mailbox (e-mail address) Headers
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Mailbox headers contain one or more email addresses, possibly with
-personalized names attached to them. The data on which they are modeled is
-represented by an associative array of email addresses and names.
-
-Mailbox headers are probably the most complex header type to understand in
-Swift Mailer because they accept their input as an array which can take various
-forms, as described in the previous chapter.
-
-All of the headers that contain e-mail addresses in a message -- with the
-exception of ``Return-Path:`` which has a stricter syntax -- use this header
-type. That is, ``To:``, ``From:`` etc.
-
-You add a new mailbox header to a HeaderSet by calling the HeaderSet's
-``addMailboxHeader()`` method.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addMailboxHeader('Your-Header-Name', array(
-      'person1@example.org' => 'Person Name One',
-      'person2@example.org',
-      'person3@example.org',
-      'person4@example.org' => 'Another named person'
-      ));
-
-Changing the value of an existing mailbox header is done by calling it's
-``setNameAddresses()`` method.
-
-.. code-block:: php
-
-    $to = $message->getHeaders()->get('To');
-
-    $to->setNameAddresses(array(
-      'joe@example.org' => 'Joe Bloggs',
-      'john@example.org' => 'John Doe',
-      'no-name@example.org'
-      ));
-
-If you don't wish to concern yourself with the complicated accepted input
-formats accepted by ``setNameAddresses()`` as described in the previous chapter
-and you only want to set one or more addresses (not names) then you can just
-use the ``setAddresses()`` method instead.
-
-.. code-block:: php
-
-    $to = $message->getHeaders()->get('To');
-
-    $to->setAddresses(array(
-      'joe@example.org',
-      'john@example.org',
-      'no-name@example.org'
-      ));
-
-.. note::
-
-    Both methods will accept the above input format in practice.
-
-If all you want to do is set a single address in the header, you can use a
-string as the input parameter to ``setAddresses()`` and/or
-``setNameAddresses()``.
-
-.. code-block:: php
-
-    $to = $message->getHeaders()->get('To');
-
-    $to->setAddresses('joe-bloggs@example.org');
-
-When output via ``toString()``, a mailbox header produces something like the
-following:
-
-.. code-block:: php
-
-    $to = $message->getHeaders()->get('To');
-
-    $to->setNameAddresses(array(
-      'person1@example.org' => 'Name of Person',
-      'person2@example.org',
-      'person3@example.org' => 'Another Person'
-    ));
-
-    echo $to->toString();
-
-    /*
-
-    To: Name of Person <person1@example.org>, person2@example.org, Another Person
-     <person3@example.org>
-
-    */
-
-ID Headers
-~~~~~~~~~~
-
-ID headers contain identifiers for the entity (or the message). The most
-notable ID header is the Message-ID header on the message itself.
-
-An ID that exists inside an ID header looks more-or-less less like an email
-address.  For example, ``<1234955437.499becad62ec2@example.org>``.
-The part to the left of the @ sign is usually unique, based on the current time
-and some random factor. The part on the right is usually a domain name.
-
-Any ID passed to the header's ``setId()`` method absolutely MUST conform to
-this structure, otherwise you'll get an Exception thrown at you by Swift Mailer
-(a ``Swift_RfcComplianceException``).  This is to ensure that the generated
-email complies with relevant RFC documents and therefore is less likely to be
-blocked as spam.
-
-It's easy to add a new ID header to a HeaderSet.  You do this by calling
-the HeaderSet's ``addIdHeader()`` method.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addIdHeader('Your-Header-Name', '123456.unqiue@example.org');
-
-Changing the value of an existing date header is done by calling its
-``setId()`` method.
-
-.. code-block:: php
-
-    $msgId = $message->getHeaders()->get('Message-ID');
-
-    $msgId->setId(time() . '.' . uniqid('thing') . '@example.org');
-
-When output via ``toString()``, an ID header produces something like the
-following:
-
-.. code-block:: php
-
-    $msgId = $message->getHeaders()->get('Message-ID');
-
-    echo $msgId->toString();
-
-    /*
-
-    Message-ID: <1234955437.499becad62ec2@example.org>
-
-    */
-
-Path Headers
-~~~~~~~~~~~~
-
-Path headers are like very-restricted mailbox headers. They contain a single
-email address with no associated name. The Return-Path header of a message is
-a path header.
-
-You add a new path header to a HeaderSet by calling the HeaderSet's
-``addPathHeader()`` method.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $headers = $message->getHeaders();
-
-    $headers->addPathHeader('Your-Header-Name', 'person@example.org');
-
-
-Changing the value of an existing path header is done by calling its
-``setAddress()`` method.
-
-.. code-block:: php
-
-    $return = $message->getHeaders()->get('Return-Path');
-
-    $return->setAddress('my-address@example.org');
-
-When output via ``toString()``, a path header produces something like the
-following:
-
-.. code-block:: php
-
-    $return = $message->getHeaders()->get('Return-Path');
-
-    $return->setAddress('person@example.org');
-
-    echo $return->toString();
-
-    /*
-
-    Return-Path: <person@example.org>
-
-    */
-
-Header Operations
------------------
-
-Working with the headers in a message involves knowing how to use the methods
-on the HeaderSet and on the individual Headers within the HeaderSet.
-
-Adding new Headers
-~~~~~~~~~~~~~~~~~~
-
-New headers can be added to the HeaderSet by using one of the provided
-``add..Header()`` methods.
-
-To add a header to a MIME entity (such as the message):
-
-Get the HeaderSet from the entity by via its ``getHeaders()`` method.
-
-* Add the header to the HeaderSet by calling one of the ``add..Header()``
-  methods.
-
-The added header will appear in the message when it is sent.
-
-.. code-block:: php
-
-    // Adding a custom header to a message
-    $message = Swift_Message::newInstance();
-    $headers = $message->getHeaders();
-    $headers->addTextHeader('X-Mine', 'something here');
-
-    // Adding a custom header to an attachment
-    $attachment = Swift_Attachment::fromPath('/path/to/doc.pdf');
-    $attachment->getHeaders()->addDateHeader('X-Created-Time', time());
-
-Retrieving Headers
-~~~~~~~~~~~~~~~~~~
-
-Headers are retrieved through the HeaderSet's ``get()`` and ``getAll()``
-methods.
-
-To get a header, or several headers from a MIME entity:
-
-* Get the HeaderSet from the entity by via its ``getHeaders()`` method.
-
-* Get the header(s) from the HeaderSet by calling either ``get()`` or
-  ``getAll()``.
-
-When using ``get()`` a single header is returned that matches the name (case
-insensitive) that is passed to it. When using ``getAll()`` with a header name,
-an array of headers with that name are returned. Calling ``getAll()`` with no
-arguments returns an array of all headers present in the entity.
-
-.. note::
-
-    It's valid for some headers to appear more than once in a message (e.g.
-    the Received header). For this reason ``getAll()`` exists to fetch all
-    headers with a specified name. In addition, ``get()`` accepts an optional
-    numerical index, starting from zero to specify which header you want more
-    specifically.
-
-.. note::
-
-    If you want to modify the contents of the header and you don't know for
-    sure what type of header it is then you may need to check the type by
-    calling its ``getFieldType()`` method.
-
-    .. code-block:: php
-
-        $headers = $message->getHeaders();
-
-        // Get the To: header
-        $toHeader = $headers->get('To');
-
-        // Get all headers named "X-Foo"
-        $fooHeaders = $headers->getAll('X-Foo');
-
-        // Get the second header named "X-Foo"
-        $foo = $headers->get('X-Foo', 1);
-
-        // Get all headers that are present
-        $all = $headers->getAll();
-
-Check if a Header Exists
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-You can check if a named header is present in a HeaderSet by calling its
-``has()`` method.
-
-To check if a header exists:
-
-* Get the HeaderSet from the entity by via its ``getHeaders()`` method.
-
-* Call the HeaderSet's ``has()`` method specifying the header you're looking
-  for.
-
-If the header exists, ``true`` will be returned or ``false`` if not.
-
-.. note::
-
-    It's valid for some headers to appear more than once in a message (e.g.
-    the Received header). For this reason ``has()`` accepts an optional
-    numerical index, starting from zero to specify which header you want to
-    check more specifically.
-
-    .. code-block:: php
-
-        $headers = $message->getHeaders();
-
-        // Check if the To: header exists
-        if ($headers->has('To')) {
-          echo 'To: exists';
-        }
-
-        // Check if an X-Foo header exists twice (i.e. check for the 2nd one)
-        if ($headers->has('X-Foo', 1)) {
-          echo 'Second X-Foo header exists';
-        }
-
-Removing Headers
-~~~~~~~~~~~~~~~~
-
-Removing a Header from the HeaderSet is done by calling the HeaderSet's
-``remove()`` or ``removeAll()`` methods.
-
-To remove an existing header:
-
-* Get the HeaderSet from the entity by via its ``getHeaders()`` method.
-
-* Call the HeaderSet's ``remove()`` or ``removeAll()`` methods specifying the
-  header you want to remove.
-
-When calling ``remove()`` a single header will be removed. When calling
-``removeAll()`` all headers with the given name will be removed. If no headers
-exist with the given name, no errors will occur.
-
-.. note::
-
-    It's valid for some headers to appear more than once in a message (e.g.
-    the Received header). For this reason ``remove()`` accepts an optional
-    numerical index, starting from zero to specify which header you want to
-    check more specifically. For the same reason, ``removeAll()`` exists to
-    remove all headers that have the given name.
-
-    .. code-block:: php
-
-        $headers = $message->getHeaders();
-
-        // Remove the Subject: header
-        $headers->remove('Subject');
-
-        // Remove all X-Foo headers
-        $headers->removeAll('X-Foo');
-
-        // Remove only the second X-Foo header
-        $headers->remove('X-Foo', 1);
-
-Modifying a Header's Content
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To change a Header's content you should know what type of header it is and then
-call it's appropriate setter method. All headers also have a
-``setFieldBodyModel()`` method that accepts a mixed parameter and delegates to
-the correct setter.
-
-To modify an existing header:
-
-* Get the HeaderSet from the entity by via its ``getHeaders()`` method.
-
-* Get the Header by using the HeaderSet's ``get()``.
-
-* Call the Header's appropriate setter method or call the header's
-  ``setFieldBodyModel()`` method.
-
-The header will be updated inside the HeaderSet and the changes will be seen
-when the message is sent.
-
-.. code-block:: php
-
-    $headers = $message->getHeaders();
-
-    // Change the Subject: header
-    $subj = $headers->get('Subject');
-    $subj->setValue('new subject here');
-
-    // Change the To: header
-    $to = $headers->get('To');
-    $to->setNameAddresses(array(
-      'person@example.org' => 'Person',
-      'thing@example.org'
-    ));
-
-    // Using the setFieldBodyModel() just delegates to the correct method
-    // So here to calls setNameAddresses()
-    $to->setFieldBodyModel(array(
-      'person@example.org' => 'Person',
-      'thing@example.org'
-    ));
diff --git a/typo3/contrib/swiftmailer/doc/help-resources.rst b/typo3/contrib/swiftmailer/doc/help-resources.rst
deleted file mode 100644 (file)
index 4208935..0000000
+++ /dev/null
@@ -1,44 +0,0 @@
-Getting Help
-============
-
-There are a number of ways you can get help when using Swift Mailer, depending
-upon the nature of your problem. For bug reports and feature requests create a
-new ticket in GitHub. For general advice ask on the Google Group
-(swiftmailer).
-
-Submitting Bugs & Feature Requests
-----------------------------------
-
-Bugs and feature requests should be posted on GitHub.
-
-If you post a bug or request a feature in the forum, or on the Google Group
-you will most likely be asked to create a ticket in `GitHub`_ since it is
-simply not feasible to manage such requests from a number of a different
-sources.
-
-When you go to GitHub you will be asked to create a username and password
-before you can create a ticket. This is free and takes very little time.
-
-When you create your ticket, do not assign it to any milestones. A developer
-will assess your ticket and re-assign it as needed.
-
-If your ticket is reporting a bug present in the current version, which was
-not present in the previous version please include the tag "regression" in
-your ticket.
-
-GitHub will update you when work is performed on your ticket.
-
-Ask on the Google Group
------------------------
-
-You can seek advice at Google Groups, within the "swiftmailer" `group`_.
-
-You can post messages to this group if you want help, or there's something you
-wish to discuss with the developers and with other users.
-
-This is probably the fastest way to get help since it is primarily email-based
-for most users, though bug reports should not be posted here since they may
-not be resolved.
-
-.. _`GitHub`: https://github.com/swiftmailer/swiftmailer/issues
-.. _`group`:  http://groups.google.com/group/swiftmailer
diff --git a/typo3/contrib/swiftmailer/doc/including-the-files.rst b/typo3/contrib/swiftmailer/doc/including-the-files.rst
deleted file mode 100644 (file)
index 978dca2..0000000
+++ /dev/null
@@ -1,46 +0,0 @@
-Including Swift Mailer (Autoloading)
-====================================
-
-If you are using Composer, Swift Mailer will be automatically autoloaded.
-
-If not, you can use the built-in autoloader by requiring the
-``swift_required.php`` file::
-
-    require_once '/path/to/swift-mailer/lib/swift_required.php';
-
-    /* rest of code goes here */
-
-If you want to override the default Swift Mailer configuration, call the
-``init()`` method on the ``Swift`` class and pass it a valid PHP callable (a
-PHP function name, a PHP 5.3 anonymous function, ...)::
-
-    require_once '/path/to/swift-mailer/lib/swift_required.php';
-
-    function swiftmailer_configurator() {
-        // configure Swift Mailer
-
-        Swift_DependencyContainer::getInstance()->...
-        Swift_Preferences::getInstance()->...
-    }
-
-    Swift::init('swiftmailer_configurator');
-
-    /* rest of code goes here */
-
-The advantage of using the ``init()`` method is that your code will be
-executed only if you use Swift Mailer in your script.
-
-.. note::
-
-    While Swift Mailer's autoloader is designed to play nicely with other
-    autoloaders, sometimes you may have a need to avoid using Swift Mailer's
-    autoloader and use your own instead. Include the ``swift_init.php``
-    instead of the ``swift_required.php`` if you need to do this. The very
-    minimum include is the ``swift_init.php`` file since Swift Mailer will not
-    work without the dependency injection this file sets up:
-
-    .. code-block:: php
-
-        require_once '/path/to/swift-mailer/lib/swift_init.php';
-
-        /* rest of code goes here */
diff --git a/typo3/contrib/swiftmailer/doc/index.rst b/typo3/contrib/swiftmailer/doc/index.rst
deleted file mode 100644 (file)
index a1a0a92..0000000
+++ /dev/null
@@ -1,16 +0,0 @@
-Swiftmailer
-===========
-
-.. toctree::
-    :maxdepth: 2
-
-    introduction
-    overview
-    installing
-    help-resources
-    including-the-files
-    messages
-    headers
-    sending
-    plugins
-    japanese
diff --git a/typo3/contrib/swiftmailer/doc/installing.rst b/typo3/contrib/swiftmailer/doc/installing.rst
deleted file mode 100644 (file)
index 24aeaec..0000000
+++ /dev/null
@@ -1,215 +0,0 @@
-Installing the Library
-======================
-
-Installing Swift Mailer is trivial. Usually it's just a case of uploading the
-extracted source files to your web server.
-
-Installing with Composer
-------------------------
-
-If you use Composer to manage your project dependencies, you can install
-Swiftmailer like this:
-
-.. code-block:: bash
-
-    $ php composer.phar require swiftmailer/swiftmailer @stable
-
-Installing from a Package
--------------------------
-
-Most users will download a package from the Swift Mailer website and install
-Swift Mailer using this.
-
-If you downloaded Swift Mailer as a ``.tar.gz`` or
-``.zip`` file installation is as simple as extracting the archive
-and uploading it to your web server.
-
-Extracting the Library
-~~~~~~~~~~~~~~~~~~~~~~
-
-You extract the archive by using your favorite unarchiving tool such as
-``tar`` or 7-Zip.
-
-You will need to have access to a program that can open uncompress the
-archive. On Windows computers, 7-Zip will work. On Mac and Linux systems you
-can use ``tar`` on the command line.
-
-To extract your downloaded package:
-
-* Use the "extract" facility of your archiving software.
-
-The source code will be placed into a directory with the same name as the
-archive (e.g. Swift-4.0.0-b1).
-
-The following example shows the process on Mac OS X and Linux systems using
-the ``tar`` command.
-
-.. code-block:: bash
-
-    $ ls
-    Swift-4.0.0-dev.tar.gz
-    $ tar xvzf Swift-4.0.0-dev.tar.gz
-    Swift-4.0.0-dev/
-    Swift-4.0.0-dev/lib/
-    Swift-4.0.0-dev/lib/classes/
-    Swift-4.0.0-dev/lib/classes/Swift/
-    Swift-4.0.0-dev/lib/classes/Swift/ByteStream/
-    Swift-4.0.0-dev/lib/classes/Swift/CharacterReader/
-    Swift-4.0.0-dev/lib/classes/Swift/CharacterReaderFactory/
-    Swift-4.0.0-dev/lib/classes/Swift/CharacterStream/
-    Swift-4.0.0-dev/lib/classes/Swift/Encoder/
-
-      ... etc etc ...
-
-    Swift-4.0.0-dev/tests/unit/Swift/Transport/LoadBalancedTransportTest.php
-    Swift-4.0.0-dev/tests/unit/Swift/Transport/SendmailTransportTest.php
-    Swift-4.0.0-dev/tests/unit/Swift/Transport/StreamBufferTest.php
-    $ cd Swift-4.0.0-dev
-    $ ls
-    CHANGES LICENSE ...
-    $
-
-Installing from Git
--------------------
-
-It's possible to download and install Swift Mailer directly from github.com if
-you want to keep up-to-date with ease.
-
-Swift Mailer's source code is kept in a git repository at github.com so you
-can get the source directly from the repository.
-
-.. note::
-
-    You do not need to have git installed to use Swift Mailer from GitHub. If
-    you don't have git installed, go to `GitHub`_ and click the "Download"
-    button.
-
-Cloning the Repository
-~~~~~~~~~~~~~~~~~~~~~~
-
-The repository can be cloned from git://github.com/swiftmailer/swiftmailer.git
-using the ``git clone`` command.
-
-You will need to have ``git`` installed before you can use the
-``git clone`` command.
-
-To clone the repository:
-
-* Open your favorite terminal environment (command line).
-
-* Move to the directory you want to clone to.
-
-* Run the command ``git clone git://github.com/swiftmailer/swiftmailer.git
-  swiftmailer``.
-
-The source code will be downloaded into a directory called "swiftmailer".
-
-The example shows the process on a UNIX-like system such as Linux, BSD or Mac
-OS X.
-
-.. code-block:: bash
-
-    $ cd source_code/
-    $ git clone git://github.com/swiftmailer/swiftmailer.git swiftmailer
-    Initialized empty Git repository in /Users/chris/source_code/swiftmailer/.git/
-    remote: Counting objects: 6815, done.
-    remote: Compressing objects: 100% (2761/2761), done.
-    remote: Total 6815 (delta 3641), reused 6326 (delta 3286)
-    Receiving objects: 100% (6815/6815), 4.35 MiB | 162 KiB/s, done.
-    Resolving deltas: 100% (3641/3641), done.
-    Checking out files: 100% (1847/1847), done.
-    $ cd swiftmailer/
-    $ ls
-    CHANGES LICENSE ...
-    $
-
-Installing from PEAR
---------------------
-
-.. note::
-
-    Using PEAR for installing Swiftmailer is deprecated and Swiftmailer 5.1.0
-    was the last version published on the PEAR channel; use Composer instead.
-
-If you want to install Swift Mailer globally on your machine, the easiest
-installation method is using the PEAR channel.
-
-To install the Swift Mailer PEAR package:
-
-* Run the command ``pear channel-discover pear.swiftmailer.org``.
-
-* Then, run the command ``pear install swift/swift``.
-
-Uploading to your Host
-----------------------
-
-You only need to upload the "lib/" directory to your web host for production
-use. All other files and directories are support files not needed in
-production.
-
-You will need FTP, ``rsync`` or similar software installed in order to upload
-the "lib/" directory to your web host.
-
-To upload Swift Mailer:
-
-* Open your FTP program, or a command line if you prefer rsync/scp.
-
-* Upload the "lib/" directory to your hosting account.
-
-The files needed to use Swift Mailer should now be accessible to PHP on your
-host.
-
-The following example shows show you can upload the files using
-``rsync`` on Linux or OS X.
-
-.. note::
-
-    You do not need to place the files inside your web root. They only need to
-    be in a place where your PHP scripts can "include" them.
-
-    .. code-block:: bash
-
-        $ rsync -rvz lib d11wtq@swiftmailer.org:swiftmailer
-        building file list ... done
-        created directory swiftmailer
-        lib/
-        lib/mime_types.php
-        lib/preferences.php
-        lib/swift_required.php
-        lib/classes/
-        lib/classes/Swift/
-        lib/classes/Swift/Attachment.php
-        lib/classes/Swift/CharacterReader.php
-          ... etc etc ...
-        lib/dependency_maps/
-        lib/dependency_maps/cache_deps.php
-        lib/dependency_maps/mime_deps.php
-        lib/dependency_maps/transport_deps.php
-
-        sent 151692 bytes  received 2974 bytes  5836.45 bytes/sec
-        total size is 401405  speedup is 2.60
-        $
-
-.. _`GitHub`: http://github.com/swiftmailer/swiftmailer
-
-Troubleshooting
----------------
-
-Swift Mailer does not work when used with function overloading as implemented
-by ``mbstring`` (``mbstring.func_overload`` set to ``2``). A workaround is to
-temporarily change the internal encoding to ``ASCII`` when sending an email:
-
-.. code-block:: php
-
-    if (function_exists('mb_internal_encoding') && ((int) ini_get('mbstring.func_overload')) & 2)
-    {
-      $mbEncoding = mb_internal_encoding();
-      mb_internal_encoding('ASCII');
-    }
-
-    // Create your message and send it with Swift Mailer
-
-    if (isset($mbEncoding))
-    {
-      mb_internal_encoding($mbEncoding);
-    }
diff --git a/typo3/contrib/swiftmailer/doc/introduction.rst b/typo3/contrib/swiftmailer/doc/introduction.rst
deleted file mode 100644 (file)
index a85336b..0000000
+++ /dev/null
@@ -1,135 +0,0 @@
-Introduction
-============
-
-Swift Mailer is a component-based library for sending e-mails from PHP
-applications.
-
-Organization of this Book
--------------------------
-
-This book has been written so that those who need information quickly are able
-to find what they need, and those who wish to learn more advanced topics can
-read deeper into each chapter.
-
-The book begins with an overview of Swift Mailer, discussing what's included
-in the package and preparing you for the remainder of the book.
-
-It is possible to read this user guide just like any other book (from
-beginning to end). Each chapter begins with a discussion of the contents it
-contains, followed by a short code sample designed to give you a head start.
-As you get further into a chapter you will learn more about Swift Mailer's
-capabilities, but often you will be able to head directly to the topic you
-wish to learn about.
-
-Throughout this book you will be presented with code samples, which most
-people should find ample to implement Swift Mailer appropriately in their own
-projects. We will also use diagrams where appropriate, and where we believe
-readers may find it helpful we will discuss some related theory, including
-reference to certain documents you are able to find online.
-
-Code Samples
-------------
-
-Code samples presented in this book will be displayed on a different colored
-background in a monospaced font. Samples are not to be taken as copy & paste
-code snippets.
-
-Code examples are used through the book to clarify what is written in text.
-They will sometimes be usable as-is, but they should always be taken as
-outline/pseudo code only.
-
-A code sample will look like this::
-
-    class AClass
-    {
-      ...
-    }
-
-    // A Comment
-    $obj = new AClass($arg1, $arg2, ... );
-
-    /* A note about another way of doing something
-    $obj = AClass::newInstance($arg1, $arg2, ... );
-
-    */
-
-The presence of 3 dots ``...`` in a code sample indicates that we have left
-out a chunk of the code for brevity, they are not actually part of the code.
-
-We will often place multi-line comments ``/* ... */`` in the code so that we
-can show alternative ways of achieving the same result.
-
-You should read the code examples given and try to understand them. They are
-kept concise so that you are not overwhelmed with information.
-
-History of Swift Mailer
------------------------
-
-Swift Mailer began back in 2005 as a one-class project for sending mail over
-SMTP. It has since grown into the flexible component-based library that is in
-development today.
-
-Chris Corbyn first posted Swift Mailer on a web forum asking for comments from
-other developers. It was never intended as a fully supported open source
-project, but members of the forum began to adopt it and make use of it.
-
-Very quickly feature requests were coming for the ability to add attachments
-and use SMTP authentication, along with a number of other "obvious" missing
-features. Considering the only alternative was PHPMailer it seemed like a good
-time to bring some fresh tools to the table. Chris began working towards a
-more component based, PHP5-like approach unlike the existing single-class,
-legacy PHP4 approach taken by PHPMailer.
-
-Members of the forum offered a lot of advice and critique on the code as he
-worked through this project and released versions 2 and 3 of the library in
-2005 and 2006, which by then had been broken down into smaller classes
-offering more flexibility and supporting plugins. To this day the Swift Mailer
-team still receive a lot of feature requests from users both on the forum and
-in by email.
-
-Until 2008 Chris was the sole developer of Swift Mailer, but entering 2009 he
-gained the support of two experienced developers well-known to him: Paul
-Annesley and Christopher Thompson. This has been an extremely welcome change.
-
-As of September 2009, Chris handed over the maintenance of Swift Mailer to
-Fabien Potencier.
-
-Now 2009 and in its fourth major version Swift Mailer is more object-oriented
-and flexible than ever, both from a usability standpoint and from a
-development standpoint.
-
-By no means is Swift Mailer ready to call "finished". There are still many
-features that can be added to the library along with the constant refactoring
-that happens behind the scenes.
-
-It's a Library!
----------------
-
-Swift Mailer is not an application - it's a library.
-
-To most experienced developers this is probably an obvious point to make, but
-it's certainly worth mentioning. Many people often contact us having gotten
-the completely wrong end of the stick in terms of what Swift Mailer is
-actually for.
-
-It's not an application. It does not have a graphical user interface. It
-cannot be opened in your web browser directly.
-
-It's a library (or a framework if you like). It provides a whole lot of
-classes that do some very complicated things, so that you don't have to. You
-"use" Swift Mailer within an application so that your application can have the
-ability to send emails.
-
-The component-based structure of the library means that you are free to
-implement it in a number of different ways and that you can pick and choose
-what you want to use.
-
-An application on the other hand (such as a blog or a forum) is already "put
-together" in a particular way, (usually) provides a graphical user interface
-and most likely doesn't offer a great deal of integration with your own
-application.
-
-Embrace the structure of the library and use the components it offers to your
-advantage. Learning what the components do, rather than blindly copying and
-pasting existing code will put you in a great position to build a powerful
-application!
diff --git a/typo3/contrib/swiftmailer/doc/japanese.rst b/typo3/contrib/swiftmailer/doc/japanese.rst
deleted file mode 100644 (file)
index 34afa7b..0000000
+++ /dev/null
@@ -1,22 +0,0 @@
-Using Swift Mailer for Japanese Emails
-======================================
-
-To send emails in Japanese, you need to tweak the default configuration.
-
-After requiring the Swift Mailer autoloader (by including the
-``swift_required.php`` file), call the ``Swift::init()`` method with the
-following code::
-
-    require_once '/path/to/swift-mailer/lib/swift_required.php';
-
-    Swift::init(function () {
-        Swift_DependencyContainer::getInstance()
-            ->register('mime.qpheaderencoder')
-            ->asAliasOf('mime.base64headerencoder');
-
-        Swift_Preferences::getInstance()->setCharset('iso-2022-jp');
-    });
-
-    /* rest of code goes here */
-
-That's all!
diff --git a/typo3/contrib/swiftmailer/doc/messages.rst b/typo3/contrib/swiftmailer/doc/messages.rst
deleted file mode 100644 (file)
index 7a19253..0000000
+++ /dev/null
@@ -1,1057 +0,0 @@
-Creating Messages
-=================
-
-Creating messages in Swift Mailer is done by making use of the various MIME
-entities provided with the library.  Complex messages can be quickly created
-with very little effort.
-
-Quick Reference for Creating a Message
----------------------------------------
-
-You can think of creating a Message as being similar to the steps you perform
-when you click the Compose button in your mail client.  You give it a subject,
-specify some recipients, add any attachments and write your message.
-
-To create a Message:
-
-* Call the ``newInstance()`` method of ``Swift_Message``.
-
-* Set your sender address (``From:``) with ``setFrom()`` or ``setSender()``.
-
-* Set a subject line with ``setSubject()``.
-
-* Set recipients with ``setTo()``, ``setCc()`` and/or ``setBcc()``.
-
-* Set a body with ``setBody()``.
-
-* Add attachments with ``attach()``.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the message
-    $message = Swift_Message::newInstance()
-
-      // Give the message a subject
-      ->setSubject('Your subject')
-
-      // Set the From address with an associative array
-      ->setFrom(array('john@doe.com' => 'John Doe'))
-
-      // Set the To addresses with an associative array
-      ->setTo(array('receiver@domain.org', 'other@domain.org' => 'A name'))
-
-      // Give it a body
-      ->setBody('Here is the message itself')
-
-      // And optionally an alternative body
-      ->addPart('<q>Here is the message itself</q>', 'text/html')
-
-      // Optionally add any attachments
-      ->attach(Swift_Attachment::fromPath('my-document.pdf'))
-      ;
-
-Message Basics
---------------
-
-A message is a container for anything you want to send to somebody else. There
-are several basic aspects of a message that you should know.
-
-An e-mail message is made up of several relatively simple entities that are
-combined in different ways to achieve different results. All of these entities
-have the same fundamental outline but serve a different purpose. The Message
-itself can be defined as a MIME entity, an Attachment is a MIME entity, all
-MIME parts are MIME entities -- and so on!
-
-The basic units of each MIME entity -- be it the Message itself, or an
-Attachment -- are its Headers and its body:
-
-.. code-block:: text
-
-    Header-Name: A header value
-    Other-Header: Another value
-
-    The body content itself
-
-The Headers of a MIME entity, and its body must conform to some strict
-standards defined by various RFC documents. Swift Mailer ensures that these
-specifications are followed by using various types of object, including
-Encoders and different Header types to generate the entity.
-
-The Structure of a Message
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Of all of the MIME entities, a message -- ``Swift_Message``
-is the largest and most complex. It has many properties that can be updated
-and it can contain other MIME entities -- attachments for example --
-nested inside it.
-
-A Message has a lot of different Headers which are there to present
-information about the message to the recipients' mail client. Most of these
-headers will be familiar to the majority of users, but we'll list the basic
-ones. Although it's possible to work directly with the Headers of a Message
-(or other MIME entity), the standard Headers have accessor methods provided to
-abstract away the complex details for you. For example, although the Date on a
-message is written with a strict format, you only need to pass a UNIX
-timestamp to ``setDate()``.
-
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| Header                        | Description                                                                                                                        | Accessors                                   |
-+===============================+====================================================================================================================================+=============================================+
-| ``Message-ID``                | Identifies this message with a unique ID, usually containing the domain name and time generated                                    | ``getId()`` / ``setId()``                   |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Return-Path``               | Specifies where bounces should go (Swift Mailer reads this for other uses)                                                         | ``getReturnPath()`` / ``setReturnPath()``   |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``From``                      | Specifies the address of the person who the message is from. This can be multiple addresses if multiple people wrote the message.  | ``getFrom()`` / ``setFrom()``               |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Sender``                    | Specifies the address of the person who physically sent the message (higher precedence than ``From:``)                             | ``getSender()`` / ``setSender()``           |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``To``                        | Specifies the addresses of the intended recipients                                                                                 | ``getTo()`` / ``setTo()``                   |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Cc``                        | Specifies the addresses of recipients who will be copied in on the message                                                         | ``getCc()`` / ``setCc()``                   |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Bcc``                       | Specifies the addresses of recipients who the message will be blind-copied to. Other recipients will not be aware of these copies. | ``getBcc()`` / ``setBcc()``                 |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Reply-To``                  | Specifies the address where replies are sent to                                                                                    | ``getReplyTo()`` / ``setReplyTo()``         |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Subject``                   | Specifies the subject line that is displayed in the recipients' mail client                                                        | ``getSubject()`` / ``setSubject()``         |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Date``                      | Specifies the date at which the message was sent                                                                                   | ``getDate()`` / ``setDate()``               |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Content-Type``              | Specifies the format of the message (usually text/plain or text/html)                                                              | ``getContentType()`` / ``setContentType()`` |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-| ``Content-Transfer-Encoding`` | Specifies the encoding scheme in the message                                                                                       | ``getEncoder()`` / ``setEncoder()``         |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------+
-
-Working with a Message Object
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Although there are a lot of available methods on a message object, you only
-need to make use of a small subset of them. Usually you'll use
-``setSubject()``, ``setTo()`` and
-``setFrom()`` before setting the body of your message with
-``setBody()``.
-
-Calling methods is simple. You just call them like functions, but using the
-object operator "``->``" to do so. If you've created
-a message object and called it ``$message`` then you'd set a
-subject on it like so:
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    $message = Swift_Message::newInstance();
-    $message->setSubject('My subject');
-
-All MIME entities (including a message) have a ``toString()``
-method that you can call if you want to take a look at what is going to be
-sent. For example, if you ``echo
-$message->toString();`` you would see something like this:
-
-.. code-block:: bash
-
-    Message-ID: <1230173678.4952f5eeb1432@swift.generated>
-    Date: Thu, 25 Dec 2008 13:54:38 +1100
-    Subject: Example subject
-    From: Chris Corbyn <chris@w3style.co.uk>
-    To: Receiver Name <recipient@example.org>
-    MIME-Version: 1.0
-    Content-Type: text/plain; charset=utf-8
-    Content-Transfer-Encoding: quoted-printable
-
-    Here is the message
-
-We'll take a closer look at the methods you use to create your message in the
-following sections.
-
-Adding Content to Your Message
-------------------------------
-
-Rich content can be added to messages in Swift Mailer with relative ease by
-calling methods such as ``setSubject()``, ``setBody()``, ``addPart()`` and
-``attach()``.
-
-Setting the Subject Line
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-The subject line, displayed in the recipients' mail client can be set with the
-``setSubject()`` method, or as a parameter to ``Swift_Message::newInstance()``.
-
-To set the subject of your Message:
-
-* Call the ``setSubject()`` method of the Message, or specify it at the time
-  you create the message.
-
-  .. code-block:: php
-
-    // Pass it as a parameter when you create the message
-    $message = Swift_Message::newInstance('My amazing subject');
-
-    // Or set it after like this
-    $message->setSubject('My amazing subject');
-
-Setting the Body Content
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-The body of the message -- seen when the user opens the message --
-is specified by calling the ``setBody()`` method. If an alternative body is to
-be included ``addPart()`` can be used.
-
-The body of a message is the main part that is read by the user. Often people
-want to send a message in HTML format (``text/html``), other
-times people want to send in plain text (``text/plain``), or
-sometimes people want to send both versions and allow the recipient to choose
-how they view the message.
-
-As a rule of thumb, if you're going to send a HTML email, always include a
-plain-text equivalent of the same content so that users who prefer to read
-plain text can do so.
-
-To set the body of your Message:
-
-* Call the ``setBody()`` method of the Message, or specify it at the time you
-  create the message.
-
-* Add any alternative bodies with ``addPart()``.
-
-If the recipient's mail client offers preferences for displaying text vs. HTML
-then the mail client will present that part to the user where available.  In
-other cases the mail client will display the "best" part it can - usually HTML
-if you've included HTML.
-
-.. code-block:: php
-
-    // Pass it as a parameter when you create the message
-    $message = Swift_Message::newInstance('Subject here', 'My amazing body');
-
-    // Or set it after like this
-    $message->setBody('My <em>amazing</em> body', 'text/html');
-
-    // Add alternative parts with addPart()
-    $message->addPart('My amazing body in plain text', 'text/plain');
-
-Attaching Files
----------------
-
-Attachments are downloadable parts of a message and can be added by calling
-the ``attach()`` method on the message. You can add attachments that exist on
-disk, or you can create attachments on-the-fly.
-
-Attachments are actually an interesting area of Swift Mailer and something
-that could put a lot of power at your fingertips if you grasp the concept
-behind the way a message is held together.
-
-Although we refer to files sent over e-mails as "attachments" -- because
-they're attached to the message -- lots of other parts of the message are
-actually "attached" even if we don't refer to these parts as attachments.
-
-File attachments are created by the ``Swift_Attachment`` class
-and then attached to the message via the ``attach()`` method on
-it. For all of the "every day" MIME types such as all image formats, word
-documents, PDFs and spreadsheets you don't need to explicitly set the
-content-type of the attachment, though it would do no harm to do so. For less
-common formats you should set the content-type -- which we'll cover in a
-moment.
-
-Attaching Existing Files
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-Files that already exist, either on disk or at a URL can be attached to a
-message with just one line of code, using ``Swift_Attachment::fromPath()``.
-
-You can attach files that exist locally, or if your PHP installation has
-``allow_url_fopen`` turned on you can attach files from other
-websites.
-
-To attach an existing file:
-
-* Create an attachment with ``Swift_Attachment::fromPath()``.
-
-* Add the attachment to the message with ``attach()``.
-
-The attachment will be presented to the recipient as a downloadable file with
-the same filename as the one you attached.
-
-.. code-block:: php
-
-    // Create the attachment
-    // * Note that you can technically leave the content-type parameter out
-    $attachment = Swift_Attachment::fromPath('/path/to/image.jpg', 'image/jpeg');
-
-    // Attach it to the message
-    $message->attach($attachment);
-
-
-    // The two statements above could be written in one line instead
-    $message->attach(Swift_Attachment::fromPath('/path/to/image.jpg'));
-
-
-    // You can attach files from a URL if allow_url_fopen is on in php.ini
-    $message->attach(Swift_Attachment::fromPath('http://site.tld/logo.png'));
-
-Setting the Filename
-~~~~~~~~~~~~~~~~~~~~
-
-Usually you don't need to explicitly set the filename of an attachment because
-the name of the attached file will be used by default, but if you want to set
-the filename you use the ``setFilename()`` method of the Attachment.
-
-To change the filename of an attachment:
-
-* Call its ``setFilename()`` method.
-
-The attachment will be attached in the normal way, but meta-data sent inside
-the email will rename the file to something else.
-
-.. code-block:: php
-
-    // Create the attachment and call its setFilename() method
-    $attachment = Swift_Attachment::fromPath('/path/to/image.jpg')
-      ->setFilename('cool.jpg');
-
-
-    // Because there's a fluid interface, you can do this in one statement
-    $message->attach(
-      Swift_Attachment::fromPath('/path/to/image.jpg')->setFilename('cool.jpg')
-    );
-
-Attaching Dynamic Content
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Files that are generated at runtime, such as PDF documents or images created
-via GD can be attached directly to a message without writing them out to disk.
-Use the standard ``Swift_Attachment::newInstance()`` method.
-
-To attach dynamically created content:
-
-* Create your content as you normally would.
-
-* Create an attachment with ``Swift_Attachment::newInstance()``, specifying
-  the source data of your content along with a name and the content-type.
-
-* Add the attachment to the message with ``attach()``.
-
-The attachment will be presented to the recipient as a downloadable file
-with the filename and content-type you specify.
-
-.. note::
-
-    If you would usually write the file to disk anyway you should just attach
-    it with ``Swift_Attachment::fromPath()`` since this will use less memory:
-
-    .. code-block:: php
-
-        // Create your file contents in the normal way, but don't write them to disk
-        $data = create_my_pdf_data();
-
-        // Create the attachment with your data
-        $attachment = Swift_Attachment::newInstance($data, 'my-file.pdf', 'application/pdf');
-
-        // Attach it to the message
-        $message->attach($attachment);
-
-
-        // You can alternatively use method chaining to build the attachment
-        $attachment = Swift_Attachment::newInstance()
-          ->setFilename('my-file.pdf')
-          ->setContentType('application/pdf')
-          ->setBody($data)
-          ;
-
-Changing the Disposition
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-Attachments just appear as files that can be saved to the Desktop if desired.
-You can make attachment appear inline where possible by using the
-``setDisposition()`` method of an attachment.
-
-To make an attachment appear inline:
-
-* Call its ``setDisposition()`` method.
-
-The attachment will be displayed within the email viewing window if the mail
-client knows how to display it.
-
-.. note::
-
-    If you try to create an inline attachment for a non-displayable file type
-    such as a ZIP file, the mail client should just present the attachment as
-    normal:
-
-    .. code-block:: php
-
-        // Create the attachment and call its setDisposition() method
-        $attachment = Swift_Attachment::fromPath('/path/to/image.jpg')
-          ->setDisposition('inline');
-
-
-        // Because there's a fluid interface, you can do this in one statement
-        $message->attach(
-          Swift_Attachment::fromPath('/path/to/image.jpg')->setDisposition('inline')
-        );
-
-Embedding Inline Media Files
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Often people want to include an image or other content inline with a HTML
-message. It's easy to do this with HTML linking to remote resources, but this
-approach is usually blocked by mail clients. Swift Mailer allows you to embed
-your media directly into the message.
-
-Mail clients usually block downloads from remote resources because this
-technique was often abused as a mean of tracking who opened an email. If
-you're sending a HTML email and you want to include an image in the message
-another approach you can take is to embed the image directly.
-
-Swift Mailer makes embedding files into messages extremely streamlined. You
-embed a file by calling the ``embed()`` method of the message,
-which returns a value you can use in a ``src`` or
-``href`` attribute in your HTML.
-
-Just like with attachments, it's possible to embed dynamically generated
-content without having an existing file available.
-
-The embedded files are sent in the email as a special type of attachment that
-has a unique ID used to reference them within your HTML attributes. On mail
-clients that do not support embedded files they may appear as attachments.
-
-Although this is commonly done for images, in theory it will work for any
-displayable (or playable) media type. Support for other media types (such as
-video) is dependent on the mail client however.
-
-Embedding Existing Files
-........................
-
-Files that already exist, either on disk or at a URL can be embedded in a
-message with just one line of code, using ``Swift_EmbeddedFile::fromPath()``.
-
-You can embed files that exist locally, or if your PHP installation has
-``allow_url_fopen`` turned on you can embed files from other websites.
-
-To embed an existing file:
-
-* Create a message object with ``Swift_Message::newInstance()``.
-
-* Set the body as HTML, and embed a file at the correct point in the message with ``embed()``.
-
-The file will be displayed with the message inline with the HTML wherever its ID
-is used as a ``src`` attribute.
-
-.. note::
-
-    ``Swift_Image`` and ``Swift_EmbeddedFile`` are just aliases of one
-    another. ``Swift_Image`` exists for semantic purposes.
-
-.. note::
-
-    You can embed files in two stages if you prefer. Just capture the return
-    value of ``embed()`` in a variable and use that as the ``src`` attribute.
-
-    .. code-block:: php
-
-        // Create the message
-        $message = Swift_Message::newInstance('My subject');
-
-        // Set the body
-        $message->setBody(
-        '<html>' .
-        ' <head></head>' .
-        ' <body>' .
-        '  Here is an image <img src="' . // Embed the file
-             $message->embed(Swift_Image::fromPath('image.png')) .
-           '" alt="Image" />' .
-        '  Rest of message' .
-        ' </body>' .
-        '</html>',
-          'text/html' // Mark the content-type as HTML
-        );
-
-        // You can embed files from a URL if allow_url_fopen is on in php.ini
-        $message->setBody(
-        '<html>' .
-        ' <head></head>' .
-        ' <body>' .
-        '  Here is an image <img src="' .
-             $message->embed(Swift_Image::fromPath('http://site.tld/logo.png')) .
-           '" alt="Image" />' .
-        '  Rest of message' .
-        ' </body>' .
-        '</html>',
-          'text/html'
-        );
-
-
-        // If placing the embed() code inline becomes cumbersome
-        // it's easy to do this in two steps
-        $cid = $message->embed(Swift_Image::fromPath('image.png'));
-
-        $message->setBody(
-        '<html>' .
-        ' <head></head>' .
-        ' <body>' .
-        '  Here is an image <img src="' . $cid . '" alt="Image" />' .
-        '  Rest of message' .
-        ' </body>' .
-        '</html>',
-          'text/html' // Mark the content-type as HTML
-        );
-
-Embedding Dynamic Content
-.........................
-
-Images that are generated at runtime, such as images created via GD can be
-embedded directly to a message without writing them out to disk. Use the
-standard ``Swift_Image::newInstance()`` method.
-
-To embed dynamically created content:
-
-* Create a message object with ``Swift_Message::newInstance()``.
-
-* Set the body as HTML, and embed a file at the correct point in the message
-  with ``embed()``. You will need to specify a filename and a content-type.
-
-The file will be displayed with the message inline with the HTML wherever its ID
-is used as a ``src`` attribute.
-
-.. note::
-
-    ``Swift_Image`` and ``Swift_EmbeddedFile`` are just aliases of one
-    another. ``Swift_Image`` exists for semantic purposes.
-
-.. note::
-
-    You can embed files in two stages if you prefer. Just capture the return
-    value of ``embed()`` in a variable and use that as the ``src`` attribute.
-
-    .. code-block:: php
-
-        // Create your file contents in the normal way, but don't write them to disk
-        $img_data = create_my_image_data();
-
-        // Create the message
-        $message = Swift_Message::newInstance('My subject');
-
-        // Set the body
-        $message->setBody(
-        '<html>' .
-        ' <head></head>' .
-        ' <body>' .
-        '  Here is an image <img src="' . // Embed the file
-             $message->embed(Swift_Image::newInstance($img_data, 'image.jpg', 'image/jpeg')) .
-           '" alt="Image" />' .
-        '  Rest of message' .
-        ' </body>' .
-        '</html>',
-          'text/html' // Mark the content-type as HTML
-        );
-
-
-        // If placing the embed() code inline becomes cumbersome
-        // it's easy to do this in two steps
-        $cid = $message->embed(Swift_Image::newInstance($img_data, 'image.jpg', 'image/jpeg'));
-
-        $message->setBody(
-        '<html>' .
-        ' <head></head>' .
-        ' <body>' .
-        '  Here is an image <img src="' . $cid . '" alt="Image" />' .
-        '  Rest of message' .
-        ' </body>' .
-        '</html>',
-          'text/html' // Mark the content-type as HTML
-        );
-
-Adding Recipients to Your Message
----------------------------------
-
-Recipients are specified within the message itself via ``setTo()``, ``setCc()``
-and ``setBcc()``. Swift Mailer reads these recipients from the message when it
-gets sent so that it knows where to send the message to.
-
-Message recipients are one of three types:
-
-* ``To:`` recipients -- the primary recipients (required)
-
-* ``Cc:`` recipients -- receive a copy of the message (optional)
-
-* ``Bcc:`` recipients -- hidden from other recipients (optional)
-
-Each type can contain one, or several addresses. It's possible to list only
-the addresses of the recipients, or you can personalize the address by
-providing the real name of the recipient.
-
-Make sure to add only valid email addresses as recipients. If you try to add an
-invalid email address with ``setTo()``, ``setCc()`` or ``setBcc()``, Swift
-Mailer will throw a ``Swift_RfcComplianceException``.
-
-If you add recipients automatically based on a data source that may contain
-invalid email addresses, you can prevent possible exceptions by validating the
-addresses using ``Swift_Validate::email($email)`` and only adding addresses
-that validate. Another way would be to wrap your ``setTo()``, ``setCc()`` and
-``setBcc()`` calls in a try-catch block and handle the
-``Swift_RfcComplianceException`` in the catch block.
-
-.. sidebar:: Syntax for Addresses
-
-    If you only wish to refer to a single email address (for example your
-    ``From:`` address) then you can just use a string.
-
-    .. code-block:: php
-
-          $message->setFrom('some@address.tld');
-
-    If you want to include a name then you must use an associative array.
-
-    .. code-block:: php
-
-         $message->setFrom(array('some@address.tld' => 'The Name'));
-
-    If you want to include multiple addresses then you must use an array.
-
-    .. code-block:: php
-
-         $message->setTo(array('some@address.tld', 'other@address.tld'));
-
-    You can mix personalized (addresses with a name) and non-personalized
-    addresses in the same list by mixing the use of associative and
-    non-associative array syntax.
-
-    .. code-block:: php
-
-         $message->setTo(array(
-           'recipient-with-name@example.org' => 'Recipient Name One',
-           'no-name@example.org', // Note that this is not a key-value pair
-           'named-recipient@example.org' => 'Recipient Name Two'
-         ));
-
-Setting ``To:`` Recipients
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-``To:`` recipients are required in a message and are set with the
-``setTo()`` or ``addTo()`` methods of the message.
-
-To set ``To:`` recipients, create the message object using either
-``new Swift_Message( ... )`` or ``Swift_Message::newInstance( ... )``,
-then call the ``setTo()`` method with a complete array of addresses, or use the
-``addTo()`` method to iteratively add recipients.
-
-The ``setTo()`` method accepts input in various formats as described earlier in
-this chapter. The ``addTo()`` method takes either one or two parameters. The
-first being the email address and the second optional parameter being the name
-of the recipient.
-
-``To:`` recipients are visible in the message headers and will be
-seen by the other recipients.
-
-.. note::
-
-    Multiple calls to ``setTo()`` will not add new recipients -- each
-    call overrides the previous calls. If you want to iteratively add
-    recipients, use the ``addTo()`` method.
-
-    .. code-block:: php
-
-        // Using setTo() to set all recipients in one go
-        $message->setTo(array(
-          'person1@example.org',
-          'person2@otherdomain.org' => 'Person 2 Name',
-          'person3@example.org',
-          'person4@example.org',
-          'person5@example.org' => 'Person 5 Name'
-        ));
-
-        // Using addTo() to add recipients iteratively
-        $message->addTo('person1@example.org');
-        $message->addTo('person2@example.org', 'Person 2 Name');
-
-Setting ``Cc:`` Recipients
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-``Cc:`` recipients are set with the ``setCc()`` or ``addCc()`` methods of the
-message.
-
-To set ``Cc:`` recipients, create the message object using either
-``new Swift_Message( ... )`` or ``Swift_Message::newInstance( ... )``, then call
-the ``setCc()`` method with a complete array of addresses, or use the
-``addCc()`` method to iteratively add recipients.
-
-The ``setCc()`` method accepts input in various formats as described earlier in
-this chapter. The ``addCc()`` method takes either one or two parameters. The
-first being the email address and the second optional parameter being the name
-of the recipient.
-
-``Cc:`` recipients are visible in the message headers and will be
-seen by the other recipients.
-
-.. note::
-
-    Multiple calls to ``setCc()`` will not add new recipients -- each
-    call overrides the previous calls. If you want to iteratively add Cc:
-    recipients, use the ``addCc()`` method.
-
-    .. code-block:: php
-
-        // Using setCc() to set all recipients in one go
-        $message->setCc(array(
-          'person1@example.org',
-          'person2@otherdomain.org' => 'Person 2 Name',
-          'person3@example.org',
-          'person4@example.org',
-          'person5@example.org' => 'Person 5 Name'
-        ));
-
-        // Using addCc() to add recipients iteratively
-        $message->addCc('person1@example.org');
-        $message->addCc('person2@example.org', 'Person 2 Name');
-
-Setting ``Bcc:`` Recipients
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-``Bcc:`` recipients receive a copy of the message without anybody else knowing
-it, and are set with the ``setBcc()`` or ``addBcc()`` methods of the message.
-
-To set ``Bcc:`` recipients, create the message object using either ``new
-Swift_Message( ... )`` or ``Swift_Message::newInstance( ... )``, then call the
-``setBcc()`` method with a complete array of addresses, or use
-the ``addBcc()`` method to iteratively add recipients.
-
-The ``setBcc()`` method accepts input in various formats as described earlier in
-this chapter. The ``addBcc()`` method takes either one or two parameters. The
-first being the email address and the second optional parameter being the name
-of the recipient.
-
-Only the individual ``Bcc:`` recipient will see their address in the message
-headers. Other recipients (including other ``Bcc:`` recipients) will not see the
-address.
-
-.. note::
-
-    Multiple calls to ``setBcc()`` will not add new recipients -- each
-    call overrides the previous calls. If you want to iteratively add Bcc:
-    recipients, use the ``addBcc()`` method.
-
-    .. code-block:: php
-
-        // Using setBcc() to set all recipients in one go
-        $message->setBcc(array(
-          'person1@example.org',
-          'person2@otherdomain.org' => 'Person 2 Name',
-          'person3@example.org',
-          'person4@example.org',
-          'person5@example.org' => 'Person 5 Name'
-        ));
-
-        // Using addBcc() to add recipients iteratively
-        $message->addBcc('person1@example.org');
-        $message->addBcc('person2@example.org', 'Person 2 Name');
-
-Specifying Sender Details
--------------------------
-
-An email must include information about who sent it. Usually this is managed
-by the ``From:`` address, however there are other options.
-
-The sender information is contained in three possible places:
-
-* ``From:`` -- the address(es) of who wrote the message (required)
-
-* ``Sender:`` -- the address of the single person who sent the message
-  (optional)
-
-* ``Return-Path:`` -- the address where bounces should go to (optional)
-
-You must always include a ``From:`` address by using ``setFrom()`` on the
-message. Swift Mailer will use this as the default ``Return-Path:`` unless
-otherwise specified.
-
-The ``Sender:`` address exists because the person who actually sent the email
-may not be the person who wrote the email. It has a higher precedence than the
-``From:`` address and will be used as the ``Return-Path:`` unless otherwise
-specified.
-
-Setting the ``From:`` Address
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-A ``From:`` address is required and is set with the ``setFrom()`` method of the
-message. ``From:`` addresses specify who actually wrote the email, and usually who sent it.
-
-What most people probably don't realise is that you can have more than one
-``From:`` address if more than one person wrote the email -- for example if an
-email was put together by a committee.
-
-To set the ``From:`` address(es):
-
-* Call the ``setFrom()`` method on the Message.
-
-The ``From:`` address(es) are visible in the message headers and
-will be seen by the recipients.
-
-.. note::
-
-    If you set multiple ``From:`` addresses then you absolutely must set a
-    ``Sender:`` address to indicate who physically sent the message.
-
-    .. code-block:: php
-
-        // Set a single From: address
-        $message->setFrom('your@address.tld');
-
-        // Set a From: address including a name
-        $message->setFrom(array('your@address.tld' => 'Your Name'));
-
-        // Set multiple From: addresses if multiple people wrote the email
-        $message->setFrom(array(
-          'person1@example.org' => 'Sender One',
-          'person2@example.org' => 'Sender Two'
-        ));
-
-Setting the ``Sender:`` Address
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-A ``Sender:`` address specifies who sent the message and is set with the
-``setSender()`` method of the message.
-
-To set the ``Sender:`` address:
-
-* Call the ``setSender()`` method on the Message.
-
-The ``Sender:`` address is visible in the message headers and will be seen by
-the recipients.
-
-This address will be used as the ``Return-Path:`` unless otherwise specified.
-
-.. note::
-
-    If you set multiple ``From:`` addresses then you absolutely must set a
-    ``Sender:`` address to indicate who physically sent the message.
-
-You must not set more than one sender address on a message because it's not
-possible for more than one person to send a single message.
-
-.. code-block:: php
-
-    $message->setSender('your@address.tld');
-
-Setting the ``Return-Path:`` (Bounce) Address
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The ``Return-Path:`` address specifies where bounce notifications should
-be sent and is set with the ``setReturnPath()`` method of the message.
-
-You can only have one ``Return-Path:`` and it must not include
-a personal name.
-
-To set the ``Return-Path:`` address:
-
-* Call the ``setReturnPath()`` method on the Message.
-
-Bounce notifications will be sent to this address.
-
-.. code-block:: php
-
-    $message->setReturnPath('bounces@address.tld');
-
-
-Signed/Encrypted Message
-------------------------
-
-To increase the integrity/security of a message it is possible to sign and/or
-encrypt an message using one or multiple signers.
-
-S/MIME
-~~~~~~
-
-S/MIME can sign and/or encrypt a message using the OpenSSL extension.
-
-When signing a message, the signer creates a signature of the entire content of the message (including attachments).
-
-The certificate and private key must be PEM encoded, and can be either created using for example OpenSSL or
-obtained at an official Certificate Authority (CA).
-
-**The recipient must have the CA certificate in the list of trusted issuers in order to verify the signature.**
-
-**Make sure the certificate supports emailProtection.**
-
-When using OpenSSL this can done by the including the *-addtrust emailProtection* parameter when creating the certificate.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $smimeSigner = Swift_Signers_SMimeSigner::newInstance();
-    $smimeSigner->setSignCertificate('/path/to/certificate.pem', '/path/to/private-key.pem');
-    $message->attachSigner($smimeSigner);
-
-When the private key is secured using a passphrase use the following instead.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $smimeSigner = Swift_Signers_SMimeSigner::newInstance();
-    $smimeSigner->setSignCertificate('/path/to/certificate.pem', array('/path/to/private-key.pem', 'passphrase'));
-    $message->attachSigner($smimeSigner);
-
-By default the signature is added as attachment,
-making the message still readable for mailing agents not supporting signed messages.
-
-Storing the message as binary is also possible but not recommended.
-
-.. code-block:: php
-
-    $smimeSigner->setSignCertificate('/path/to/certificate.pem', '/path/to/private-key.pem', PKCS7_BINARY);
-
-When encrypting the message (also known as enveloping), the entire message (including attachments)
-is encrypted using a certificate, and the recipient can then decrypt the message using corresponding private key.
-
-Encrypting ensures nobody can read the contents of the message without the private key.
-
-Normally the recipient provides a certificate for encrypting and keeping the decryption key private.
-
-Using both signing and encrypting is also possible.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance();
-
-    $smimeSigner = Swift_Signers_SMimeSigner::newInstance();
-    $smimeSigner->setSignCertificate('/path/to/sign-certificate.pem', '/path/to/private-key.pem');
-    $smimeSigner->setEncryptCertificate('/path/to/encrypt-certificate.pem');
-    $message->attachSigner($smimeSigner);
-
-The used encryption cipher can be set as the second parameter of setEncryptCertificate()
-
-See http://php.net/manual/openssl.ciphers for a list of supported ciphers.
-
-By default the message is first signed and then encrypted, this can be changed by adding.
-
-.. code-block:: php
-
-    $smimeSigner->setSignThenEncrypt(false);
-
-**Changing this is not recommended as most mail agents don't support this none-standard way.**
-
-Only when having trouble with sign then encrypt method, this should be changed.
-
-Requesting a Read Receipt
--------------------------
-
-It is possible to request a read-receipt to be sent to an address when the
-email is opened. To request a read receipt set the address with
-``setReadReceiptTo()``.
-
-To request a read receipt:
-
-* Set the address you want the receipt to be sent to with the
-  ``setReadReceiptTo()`` method on the Message.
-
-When the email is opened, if the mail client supports it a notification will be sent to this address.
-
-.. note::
-
-    Read receipts won't work for the majority of recipients since many mail
-    clients auto-disable them. Those clients that will send a read receipt
-    will make the user aware that one has been requested.
-
-    .. code-block:: php
-
-        $message->setReadReceiptTo('your@address.tld');
-
-Setting the Character Set
--------------------------
-
-The character set of the message (and it's MIME parts) is set with the
-``setCharset()`` method. You can also change the global default of UTF-8 by
-working with the ``Swift_Preferences`` class.
-
-Swift Mailer will default to the UTF-8 character set unless otherwise
-overridden. UTF-8 will work in most instances since it includes all of the
-standard US keyboard characters in addition to most international characters.
-
-It is absolutely vital however that you know what character set your message
-(or it's MIME parts) are written in otherwise your message may be received
-completely garbled.
-
-There are two places in Swift Mailer where you can change the character set:
-
-* In the ``Swift_Preferences`` class
-
-* On each individual message and/or MIME part
-
-To set the character set of your Message:
-
-* Change the global UTF-8 setting by calling
-  ``Swift_Preferences::setCharset()``; or
-
-* Call the ``setCharset()`` method on the message or the MIME part.
-
-   .. code-block:: php
-
-    // Approach 1: Change the global setting (suggested)
-    Swift_Preferences::getInstance()->setCharset('iso-8859-2');
-
-    // Approach 2: Call the setCharset() method of the message
-    $message = Swift_Message::newInstance()
-      ->setCharset('iso-8859-2');
-
-    // Approach 3: Specify the charset when setting the body
-    $message->setBody('My body', 'text/html', 'iso-8859-2');
-
-    // Approach 4: Specify the charset for each part added
-    $message->addPart('My part', 'text/plain', 'iso-8859-2');
-
-Setting the Line Length
------------------------
-
-The length of lines in a message can be changed by using the ``setMaxLineLength()`` method on the message. It should be kept to less than
-1000 characters.
-
-Swift Mailer defaults to using 78 characters per line in a message. This is
-done for historical reasons and so that the message can be easily viewed in
-plain-text terminals.
-
-To change the maximum length of lines in your Message:
-
-* Call the ``setMaxLineLength()`` method on the Message.
-
-Lines that are longer than the line length specified will be wrapped between
-words.
-
-.. note::
-
-    You should never set a maximum length longer than 1000 characters
-    according to RFC 2822. Doing so could have unspecified side-effects such
-    as truncating parts of your message when it is transported between SMTP
-    servers.
-
-    .. code-block:: php
-
-        $message->setMaxLineLength(1000);
-
-Setting the Message Priority
-----------------------------
-
-You can change the priority of the message with ``setPriority()``. Setting the
-priority will not change the way your email is sent -- it is purely an
-indicative setting for the recipient.
-
-The priority of a message is an indication to the recipient what significance
-it has. Swift Mailer allows you to set the priority by calling the ``setPriority`` method. This method takes an integer value between 1 and 5:
-
-* Highest
-* High
-* Normal
-* Low
-* Lowest
-
-To set the message priority:
-
-* Set the priority as an integer between 1 and 5 with the ``setPriority()``
-  method on the Message.
-
-.. code-block:: php
-
-    // Indicate "High" priority
-    $message->setPriority(2);
diff --git a/typo3/contrib/swiftmailer/doc/overview.rst b/typo3/contrib/swiftmailer/doc/overview.rst
deleted file mode 100644 (file)
index c912617..0000000
+++ /dev/null
@@ -1,161 +0,0 @@
-Library Overview
-================
-
-Most features (and more) of your every day mail client software are provided
-by Swift Mailer, using object-oriented PHP code as the interface.
-
-In this chapter we will take a short tour of the various components, which put
-together form the Swift Mailer library as a whole. You will learn key
-terminology used throughout the rest of this book and you will gain a little
-understanding of the classes you will work with as you integrate Swift Mailer
-into your application.
-
-This chapter is intended to prepare you for the information contained in the
-subsequent chapters of this book. You may choose to skip this chapter if you
-are fairly technically minded, though it is likely to save you some time in
-the long run if you at least read between the lines here.
-
-System Requirements
--------------------
-
-The basic requirements to operate Swift Mailer are extremely minimal and
-easily achieved. Historically, Swift Mailer has supported both PHP 4 and PHP 5
-by following a parallel development workflow. Now in it's fourth major
-version, and Swift Mailer operates on servers running PHP 5.2 or higher.
-
-The library aims to work with as many PHP 5 projects as possible:
-
-* PHP 5.2 or higher, with the SPL extension (standard)
-
-* Limited network access to connect to remote SMTP servers
-
-* 8 MB or more memory limit (Swift Mailer uses around 2 MB)
-
-Component Breakdown
--------------------
-
-Swift Mailer is made up of many classes. Each of these classes can be grouped
-into a general "component" group which describes the task it is designed to
-perform.
-
-We'll take a brief look at the components which form Swift Mailer in this
-section of the book.
-
-The Mailer
-~~~~~~~~~~
-
-The mailer class, ``Swift_Mailer`` is the central class in the library where
-all of the other components meet one another. ``Swift_Mailer`` acts as a sort
-of message dispatcher, communicating with the underlying Transport to deliver
-your Message to all intended recipients.
-
-If you were to dig around in the source code for Swift Mailer you'd notice
-that ``Swift_Mailer`` itself is pretty bare. It delegates to other objects for
-most tasks and in theory, if you knew the internals of Swift Mailer well you
-could by-pass this class entirely. We wouldn't advise doing such a thing
-however -- there are reasons this class exists:
-
-* for consistency, regardless of the Transport used
-
-* to provide abstraction from the internals in the event internal API changes
-  are made
-
-* to provide convenience wrappers around aspects of the internal API
-
-An instance of ``Swift_Mailer`` is created by the developer before sending any
-Messages.
-
-Transports
-~~~~~~~~~~
-
-Transports are the classes in Swift Mailer that are responsible for
-communicating with a service in order to deliver a Message. There are several
-types of Transport in Swift Mailer, all of which implement the Swift_Transport
-interface and offer underlying start(), stop() and send() methods.
-
-Typically you will not need to know how a Transport works under-the-surface,
-you will only need to know how to create an instance of one, and which one to
-use for your environment.
-
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-| Class                           | Features                                                                                    | Pros/cons                                                                                                                                     |
-+=================================+=============================================================================================+===============================================================================================================================================+
-| ``Swift_SmtpTransport``         | Sends messages over SMTP; Supports Authentication; Supports Encryption                      | Very portable; Pleasingly predictable results; Provides good feedback                                                                         |
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-| ``Swift_SendmailTransport``     | Communicates with a locally installed ``sendmail`` executable (Linux/UNIX)                  | Quick time-to-run;  Provides less-accurate feedback than SMTP; Requires ``sendmail`` installation                                             |
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-| ``Swift_MailTransport``         | Uses PHP's built-in ``mail()`` function                                                     | Very portable; Potentially unpredictable results; Provides extremely weak feedback                                                            |
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-| ``Swift_LoadBalancedTransport`` | Cycles through a collection of the other Transports to manage load-reduction                | Provides graceful fallback if one Transport fails (e.g. an SMTP server is down); Keeps the load on remote services down by spreading the work |
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-| ``Swift_FailoverTransport``     | Works in conjunction with a collection of the other Transports to provide high-availability | Provides graceful fallback if one Transport fails (e.g. an SMTP server is down)                                                               |
-+---------------------------------+---------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------+
-
-MIME Entities
-~~~~~~~~~~~~~
-
-Everything that forms part of a Message is called a MIME Entity. All MIME
-entities in Swift Mailer share a common set of features. There are various
-types of MIME entity that serve different purposes such as Attachments and
-MIME parts.
-
-An e-mail message is made up of several relatively simple entities that are
-combined in different ways to achieve different results. All of these entities
-have the same fundamental outline but serve a different purpose. The Message
-itself can be defined as a MIME entity, an Attachment is a MIME entity, all
-MIME parts are MIME entities -- and so on!
-
-The basic units of each MIME entity -- be it the Message itself, or an
-Attachment -- are its Headers and its body:
-
-.. code-block:: text
-
-    Other-Header: Another value
-
-    The body content itself
-
-The Headers of a MIME entity, and its body must conform to some strict
-standards defined by various RFC documents. Swift Mailer ensures that these
-specifications are followed by using various types of object, including
-Encoders and different Header types to generate the entity.
-
-Each MIME component implements the base ``Swift_Mime_MimeEntity`` interface,
-which offers methods for retrieving Headers, adding new Headers, changing the
-Encoder, updating the body and so on!
-
-All MIME entities have one Header in common -- the Content-Type Header,
-updated with the entity's ``setContentType()`` method.
-
-Encoders
-~~~~~~~~
-
-Encoders are used to transform the content of Messages generated in Swift
-Mailer into a format that is safe to send across the internet and that
-conforms to RFC specifications.
-
-Generally speaking you will not need to interact with the Encoders in Swift
-Mailer -- the correct settings will be handled by the library itself.
-However they are probably worth a brief mention in the event that you do want
-to play with them.
-
-Both the Headers and the body of all MIME entities (including the Message
-itself) use Encoders to ensure the data they contain can be sent over the
-internet without becoming corrupted or misinterpreted.
-
-There are two types of Encoder: Base64 and Quoted-Printable.
-
-Plugins
-~~~~~~~
-
-Plugins exist to extend, or modify the behaviour of Swift Mailer. They respond
-to Events that are fired within the Transports during sending.
-
-There are a number of Plugins provided as part of the base Swift Mailer
-package and they all follow a common interface to respond to Events fired
-within the library. Interfaces are provided to "listen" to each type of Event
-fired and to act as desired when a listened-to Event occurs.
-
-Although several plugins are provided with Swift Mailer out-of-the-box, the
-Events system has been specifically designed to make it easy for experienced
-object-oriented developers to write their own plugins in order to achieve
-goals that may not be possible with the base library.
diff --git a/typo3/contrib/swiftmailer/doc/plugins.rst b/typo3/contrib/swiftmailer/doc/plugins.rst
deleted file mode 100644 (file)
index 16ae335..0000000
+++ /dev/null
@@ -1,385 +0,0 @@
-Plugins
-=======
-
-Plugins are provided with Swift Mailer and can be used to extend the behavior
-of the library in situations where using simple class inheritance would be more complex.
-
-AntiFlood Plugin
-----------------
-
-Many SMTP servers have limits on the number of messages that may be sent
-during any single SMTP connection. The AntiFlood plugin provides a way to stay
-within this limit while still managing a large number of emails.
-
-A typical limit for a single connection is 100 emails. If the server you
-connect to imposes such a limit, it expects you to disconnect after that
-number of emails has been sent. You could manage this manually within a loop,
-but the AntiFlood plugin provides the necessary wrapper code so that you don't
-need to worry about this logic.
-
-Regardless of limits imposed by the server, it's usually a good idea to be
-conservative with the resources of the SMTP server. Sending will become
-sluggish if the server is being over-used so using the AntiFlood plugin will
-not be a bad idea even if no limits exist.
-
-The AntiFlood plugin's logic is basically to disconnect and the immediately
-re-connect with the SMTP server every X number of emails sent, where X is a
-number you specify to the plugin.
-
-You can also specify a time period in seconds that Swift Mailer should pause
-for between the disconnect/re-connect process. It's a good idea to pause for a
-short time (say 30 seconds every 100 emails) simply to give the SMTP server a
-chance to process its queue and recover some resources.
-
-Using the AntiFlood Plugin
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The AntiFlood Plugin -- like all plugins -- is added with the Mailer class's
-``registerPlugin()`` method. It takes two constructor parameters: the number of
-emails to pause after, and optionally the number of seconds to pause for.
-
-To use the AntiFlood plugin:
-
-* Create an instance of the Mailer using any Transport you choose.
-
-* Create an instance of the ``Swift_Plugins_AntiFloodPlugin`` class, passing
-  in one or two constructor parameters.
-
-* Register the plugin using the Mailer's ``registerPlugin()`` method.
-
-* Continue using Swift Mailer to send messages as normal.
-
-When Swift Mailer sends messages it will count the number of messages that
-have been sent since the last re-connect. Once the number hits your specified
-threshold it will disconnect and re-connect, optionally pausing for a
-specified amount of time.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Mailer using any Transport
-    $mailer = Swift_Mailer::newInstance(
-      Swift_SmtpTransport::newInstance('smtp.example.org', 25)
-    );
-
-    // Use AntiFlood to re-connect after 100 emails
-    $mailer->registerPlugin(new Swift_Plugins_AntiFloodPlugin(100));
-
-    // And specify a time in seconds to pause for (30 secs)
-    $mailer->registerPlugin(new Swift_Plugins_AntiFloodPlugin(100, 30));
-
-    // Continue sending as normal
-    for ($lotsOfRecipients as $recipient) {
-      ...
-
-      $mailer->send( ... );
-    }
-
-Throttler Plugin
-----------------
-
-If your SMTP server has restrictions in place to limit the rate at which you
-send emails, then your code will need to be aware of this rate-limiting. The
-Throttler plugin makes Swift Mailer run at a rate-limited speed.
-
-Many shared hosts don't open their SMTP servers as a free-for-all. Usually
-they have policies in place (probably to discourage spammers) that only allow
-you to send a fixed number of emails per-hour/day.
-
-The Throttler plugin supports two modes of rate-limiting and with each, you
-will need to do that math to figure out the values you want. The plugin can
-limit based on the number of emails per minute, or the number of
-bytes-transferred per-minute.
-
-Using the Throttler Plugin
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The Throttler Plugin -- like all plugins -- is added with the Mailer class'
-``registerPlugin()`` method. It has two required constructor parameters that
-tell it how to do its rate-limiting.
-
-To use the Throttler plugin:
-
-* Create an instance of the Mailer using any Transport you choose.
-
-* Create an instance of the ``Swift_Plugins_ThrottlerPlugin`` class, passing
-  the number of emails, or bytes you wish to limit by, along with the mode
-  you're using.
-
-* Register the plugin using the Mailer's ``registerPlugin()`` method.
-
-* Continue using Swift Mailer to send messages as normal.
-
-When Swift Mailer sends messages it will keep track of the rate at which sending
-messages is occurring. If it realises that sending is happening too fast, it
-will cause your program to ``sleep()`` for enough time to average out the rate.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Mailer using any Transport
-    $mailer = Swift_Mailer::newInstance(
-      Swift_SmtpTransport::newInstance('smtp.example.org', 25)
-    );
-
-    // Rate limit to 100 emails per-minute
-    $mailer->registerPlugin(new Swift_Plugins_ThrottlerPlugin(
-      100, Swift_Plugins_ThrottlerPlugin::MESSAGES_PER_MINUTE
-    ));
-
-    // Rate limit to 10MB per-minute
-    $mailer->registerPlugin(new Swift_Plugins_ThrottlerPlugin(
-      1024 * 1024 * 10, Swift_Plugins_ThrottlerPlugin::BYTES_PER_MINUTE
-    ));
-
-    // Continue sending as normal
-    for ($lotsOfRecipients as $recipient) {
-      ...
-
-      $mailer->send( ... );
-    }
-
-Logger Plugin
--------------
-
-The Logger plugins helps with debugging during the process of sending. It can
-help to identify why an SMTP server is rejecting addresses, or any other
-hard-to-find problems that may arise.
-
-The Logger plugin comes in two parts. There's the plugin itself, along with
-one of a number of possible Loggers that you may choose to use. For example,
-the logger may output messages directly in realtime, or it may capture
-messages in an array.
-
-One other notable feature is the way in which the Logger plugin changes
-Exception messages. If Exceptions are being thrown but the error message does
-not provide conclusive information as to the source of the problem (such as an
-ambiguous SMTP error) the Logger plugin includes the entire SMTP transcript in
-the error message so that debugging becomes a simpler task.
-
-There are a few available Loggers included with Swift Mailer, but writing your
-own implementation is incredibly simple and is achieved by creating a short
-class that implements the ``Swift_Plugins_Logger`` interface.
-
-* ``Swift_Plugins_Loggers_ArrayLogger``: Keeps a collection of log messages
-  inside an array. The array content can be cleared or dumped out to the
-  screen.
-
-* ``Swift_Plugins_Loggers_EchoLogger``: Prints output to the screen in
-  realtime. Handy for very rudimentary debug output.
-
-Using the Logger Plugin
-~~~~~~~~~~~~~~~~~~~~~~~
-
-The Logger Plugin -- like all plugins -- is added with the Mailer class'
-``registerPlugin()`` method. It accepts an instance of ``Swift_Plugins_Logger``
-in its constructor.
-
-To use the Logger plugin:
-
-* Create an instance of the Mailer using any Transport you choose.
-
-* Create an instance of the a Logger implementation of
-  ``Swift_Plugins_Logger``.
-
-* Create an instance of the ``Swift_Plugins_LoggerPlugin`` class, passing the
-  created Logger instance to its constructor.
-
-* Register the plugin using the Mailer's ``registerPlugin()`` method.
-
-* Continue using Swift Mailer to send messages as normal.
-
-* Dump the contents of the log with the logger's ``dump()`` method.
-
-When Swift Mailer sends messages it will keep a log of all the interactions
-with the underlying Transport being used. Depending upon the Logger that has
-been used the behaviour will differ, but all implementations offer a way to
-get the contents of the log.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Mailer using any Transport
-    $mailer = Swift_Mailer::newInstance(
-     Swift_SmtpTransport::newInstance('smtp.example.org', 25)
-    );
-
-    // To use the ArrayLogger
-    $logger = new Swift_Plugins_Loggers_ArrayLogger();
-    $mailer->registerPlugin(new Swift_Plugins_LoggerPlugin($logger));
-
-    // Or to use the Echo Logger
-    $logger = new Swift_Plugins_Loggers_EchoLogger();
-    $mailer->registerPlugin(new Swift_Plugins_LoggerPlugin($logger));
-
-    // Continue sending as normal
-    for ($lotsOfRecipients as $recipient) {
-     ...
-
-     $mailer->send( ... );
-    }
-
-    // Dump the log contents
-    // NOTE: The EchoLogger dumps in realtime so dump() does nothing for it
-    echo $logger->dump();
-
-Decorator Plugin
-----------------
-
-Often there's a need to send the same message to multiple recipients, but with
-tiny variations such as the recipient's name being used inside the message
-body. The Decorator plugin aims to provide a solution for allowing these small
-differences.
-
-The decorator plugin works by intercepting the sending process of Swift
-Mailer, reading the email address in the To: field and then looking up a set
-of replacements for a template.
-
-While the use of this plugin is simple, it is probably the most commonly
-misunderstood plugin due to the way in which it works. The typical mistake
-users make is to try registering the plugin multiple times (once for each
-recipient) -- inside a loop for example. This is incorrect.
-
-The Decorator plugin should be registered just once, but containing the list
-of all recipients prior to sending. It will use this list of recipients to
-find the required replacements during sending.
-
-Using the Decorator Plugin
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-To use the Decorator plugin, simply create an associative array of replacements
-based on email addresses and then use the mailer's ``registerPlugin()`` method
-to add the plugin.
-
-First create an associative array of replacements based on the email addresses
-you'll be sending the message to.
-
-.. note::
-
-    The replacements array becomes a 2-dimensional array whose keys are the
-    email addresses and whose values are an associative array of replacements
-    for that email address. The curly braces used in this example can be any
-    type of syntax you choose, provided they match the placeholders in your
-    email template.
-
-    .. code-block:: php
-
-        $replacements = array();
-        foreach ($users as $user) {
-          $replacements[$user['email']] = array(
-            '{username}'=>$user['username'],
-            '{password}'=>$user['password']
-          );
-        }
-
-Now create an instance of the Decorator plugin using this array of replacements
-and then register it with the Mailer. Do this only once!
-
-.. code-block:: php
-
-    $decorator = new Swift_Plugins_DecoratorPlugin($replacements);
-
-    $mailer->registerPlugin($decorator);
-
-When you create your message, replace elements in the body (and/or the subject
-line) with your placeholders.
-
-.. code-block:: php
-
-    $message = Swift_Message::newInstance()
-      ->setSubject('Important notice for {username}')
-      ->setBody(
-        "Hello {username}, we have reset your password to {password}\n" .
-        "Please log in and change it at your earliest convenience."
-      )
-      ;
-
-    foreach ($users as $user) {
-      $message->addTo($user['email']);
-    }
-
-When you send this message to each of your recipients listed in your
-``$replacements`` array they will receive a message customized for just
-themselves. For example, the message used above when received may appear like
-this to one user:
-
-.. code-block:: text
-
-    Subject: Important notice for smilingsunshine2009
-
-    Hello smilingsunshine2009, we have reset your password to rainyDays
-    Please log in and change it at your earliest convenience.
-
-While another use may receive the message as:
-
-.. code-block:: text
-
-    Subject: Important notice for billy-bo-bob
-
-    Hello billy-bo-bob, we have reset your password to dancingOctopus
-    Please log in and change it at your earliest convenience.
-
-While the decorator plugin provides a means to solve this problem, there are
-various ways you could tackle this problem without the need for a plugin.
-We're trying to come up with a better way ourselves and while we have several
-(obvious) ideas we don't quite have the perfect solution to go ahead and
-implement it. Watch this space.
-
-Providing Your Own Replacements Lookup for the Decorator
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Filling an array with replacements may not be the best solution for providing
-replacement information to the decorator. If you have a more elegant algorithm
-that performs replacement lookups on-the-fly you may provide your own
-implementation.
-
-Providing your own replacements lookup implementation for the Decorator is
-simply a matter of passing an instance of ``Swift_Plugins_Decorator_Replacements`` to the decorator plugin's constructor,
-rather than passing in an array.
-
-The Replacements interface is very simple to implement since it has just one
-method: ``getReplacementsFor($address)``.
-
-Imagine you want to look up replacements from a database on-the-fly, you might
-provide an implementation that does this. You need to create a small class.
-
-.. code-block:: php
-
-    class DbReplacements implements Swift_Plugins_Decorator_Replacements {
-      public function getReplacementsFor($address) {
-        $sql = sprintf(
-          "SELECT * FROM user WHERE email = '%s'",
-          mysql_real_escape_string($address)
-        );
-
-        $result = mysql_query($sql);
-
-        if ($row = mysql_fetch_assoc($result)) {
-          return array(
-            '{username}'=>$row['username'],
-            '{password}'=>$row['password']
-          );
-        }
-      }
-    }
-
-Now all you need to do is pass an instance of your class into the Decorator
-plugin's constructor instead of passing an array.
-
-.. code-block:: php
-
-    $decorator = new Swift_Plugins_DecoratorPlugin(new DbReplacements());
-
-    $mailer->registerPlugin($decorator);
-
-For each message sent, the plugin will call your class' ``getReplacementsFor()``
-method to find the array of replacements it needs.
-
-.. note::
-
-    If your lookup algorithm is case sensitive, you should transform the
-    ``$address`` argument as appropriate -- for example by passing it
-    through ``strtolower()``.
diff --git a/typo3/contrib/swiftmailer/doc/sending.rst b/typo3/contrib/swiftmailer/doc/sending.rst
deleted file mode 100644 (file)
index 3e9c3a8..0000000
+++ /dev/null
@@ -1,607 +0,0 @@
-Sending Messages
-================
-
-Quick Reference for Sending a Message
--------------------------------------
-
-Sending a message is very straightforward. You create a Transport, use it to
-create the Mailer, then you use the Mailer to send the message.
-
-To send a Message:
-
-* Create a Transport from one of the provided Transports --
-  ``Swift_SmtpTransport``, ``Swift_SendmailTransport``, ``Swift_MailTransport``
-  or one of the aggregate Transports.
-
-* Create an instance of the ``Swift_Mailer`` class, using the Transport as
-  it's constructor parameter.
-
-* Create a Message.
-
-* Send the message via the ``send()`` method on the Mailer object.
-
-.. caution::
-
-    The ``Swift_SmtpTransport`` and ``Swift_SendmailTransport`` transports use
-    ``proc_*`` PHP functions, which might not be available on your PHP
-    installation. You can easily check if that's the case by running the
-    following PHP script: ``<?php echo function_exists('proc_open') ? "Yep,
-    that will work" : "Sorry, that won't work";``
-
-When using ``send()`` the message will be sent just like it would be sent if you
-used your mail client. An integer is returned which includes the number of
-successful recipients. If none of the recipients could be sent to then zero will
-be returned, which equates to a boolean ``false``. If you set two ``To:``
-recipients and three ``Bcc:`` recipients in the message and all of the
-recipients are delivered to successfully then the value 5 will be returned.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Transport
-    $transport = Swift_SmtpTransport::newInstance('smtp.example.org', 25)
-      ->setUsername('your username')
-      ->setPassword('your password')
-      ;
-
-    /*
-    You could alternatively use a different transport such as Sendmail or Mail:
-
-    // Sendmail
-    $transport = Swift_SendmailTransport::newInstance('/usr/sbin/sendmail -bs');
-
-    // Mail
-    $transport = Swift_MailTransport::newInstance();
-    */
-
-    // Create the Mailer using your created Transport
-    $mailer = Swift_Mailer::newInstance($transport);
-
-    // Create a message
-    $message = Swift_Message::newInstance('Wonderful Subject')
-      ->setFrom(array('john@doe.com' => 'John Doe'))
-      ->setTo(array('receiver@domain.org', 'other@domain.org' => 'A name'))
-      ->setBody('Here is the message itself')
-      ;
-
-    // Send the message
-    $result = $mailer->send($message);
-
-Transport Types
-~~~~~~~~~~~~~~~
-
-A Transport is the component which actually does the sending. You need to
-provide a Transport object to the Mailer class and there are several possible
-options.
-
-Typically you will not need to know how a Transport works under-the-surface,
-you will only need to know how to create an instance of one, and which one to
-use for your environment.
-
-The SMTP Transport
-..................
-
-The SMTP Transport sends messages over the (standardized) Simple Message
-Transfer Protocol.  It can deal with encryption and authentication.
-
-The SMTP Transport, ``Swift_SmtpTransport`` is without doubt the most commonly
-used Transport because it will work on 99% of web servers (I just made that
-number up, but you get the idea). All the server needs is the ability to
-connect to a remote (or even local) SMTP server on the correct port number
-(usually 25).
-
-SMTP servers often require users to authenticate with a username and password
-before any mail can be sent to other domains. This is easily achieved using
-Swift Mailer with the SMTP Transport.
-
-SMTP is a protocol -- in other words it's a "way" of communicating a job
-to be done (i.e. sending a message). The SMTP protocol is the fundamental
-basis on which messages are delivered all over the internet 7 days a week, 365
-days a year. For this reason it's the most "direct" method of sending messages
-you can use and it's the one that will give you the most power and feedback
-(such as delivery failures) when using Swift Mailer.
-
-Because SMTP is generally run as a remote service (i.e. you connect to it over
-the network/internet) it's extremely portable from server-to-server. You can
-easily store the SMTP server address and port number in a configuration file
-within your application and adjust the settings accordingly if the code is
-moved or if the SMTP server is changed.
-
-Some SMTP servers -- Google for example -- use encryption for security reasons.
-Swift Mailer supports using both SSL and TLS encryption settings.
-
-Using the SMTP Transport
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-The SMTP Transport is easy to use. Most configuration options can be set with
-the constructor.
-
-To use the SMTP Transport you need to know which SMTP server your code needs
-to connect to. Ask your web host if you're not sure. Lots of people ask me who
-to connect to -- I really can't answer that since it's a setting that's
-extremely specific to your hosting environment.
-
-To use the SMTP Transport:
-
-* Call ``Swift_SmtpTransport::newInstance()`` with the SMTP server name and
-  optionally with a port number (defaults to 25).
-
-* Use the returned object to create the Mailer.
-
-A connection to the SMTP server will be established upon the first call to
-``send()``.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Transport
-    $transport = Swift_SmtpTransport::newInstance('smtp.example.org', 25);
-
-    // Create the Mailer using your created Transport
-    $mailer = Swift_Mailer::newInstance($transport);
-
-    /*
-    It's also possible to use multiple method calls
-
-    $transport = Swift_SmtpTransport::newInstance()
-      ->setHost('smtp.example.org')
-      ->setPort(25)
-      ;
-    */
-
-Encrypted SMTP
-^^^^^^^^^^^^^^
-
-You can use SSL or TLS encryption with the SMTP Transport by specifying it as
-a parameter or with a method call.
-
-To use encryption with the SMTP Transport:
-
-* Pass the encryption setting as a third parameter to
-  ``Swift_SmtpTransport::newInstance()``; or
-
-* Call the ``setEncryption()`` method on the Transport.
-
-A connection to the SMTP server will be established upon the first call to
-``send()``. The connection will be initiated with the correct encryption
-settings.
-
-.. note::
-
-    For SSL or TLS encryption to work your PHP installation must have
-    appropriate OpenSSL transports wrappers. You can check if "tls" and/or
-    "ssl" are present in your PHP installation by using the PHP function
-    ``stream_get_transports()``
-
-    .. code-block:: php
-
-        require_once 'lib/swift_required.php';
-
-        // Create the Transport
-        $transport = Swift_SmtpTransport::newInstance('smtp.example.org', 587, 'ssl');
-
-        // Create the Mailer using your created Transport
-        $mailer = Swift_Mailer::newInstance($transport);
-
-        /*
-        It's also possible to use multiple method calls
-
-        $transport = Swift_SmtpTransport::newInstance()
-          ->setHost('smtp.example.org')
-          ->setPort(587)
-          ->setEncryption('ssl')
-          ;
-        */
-
-SMTP with a Username and Password
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Some servers require authentication. You can provide a username and password
-with ``setUsername()`` and ``setPassword()`` methods.
-
-To use a username and password with the SMTP Transport:
-
-* Create the Transport with ``Swift_SmtpTransport::newInstance()``.
-
-* Call the ``setUsername()`` and ``setPassword()`` methods on the Transport.
-
-Your username and password will be used to authenticate upon first connect
-when ``send()`` are first used on the Mailer.
-
-If authentication fails, an Exception of type ``Swift_TransportException`` will
-be thrown.
-
-.. note::
-
-    If you need to know early whether or not authentication has failed and an
-    Exception is going to be thrown, call the ``start()`` method on the
-    created Transport.
-
-    .. code-block:: php
-
-        require_once 'lib/swift_required.php';
-
-        // Create the Transport the call setUsername() and setPassword()
-        $transport = Swift_SmtpTransport::newInstance('smtp.example.org', 25)
-          ->setUsername('username')
-          ->setPassword('password')
-          ;
-
-        // Create the Mailer using your created Transport
-        $mailer = Swift_Mailer::newInstance($transport);
-
-The Sendmail Transport
-......................
-
-The Sendmail Transport sends messages by communicating with a locally
-installed MTA -- such as ``sendmail``.
-
-The Sendmail Transport, ``Swift_SendmailTransport`` does not directly connect to
-any remote services. It is designed for Linux servers that have ``sendmail``
-installed. The Transport starts a local ``sendmail`` process and sends messages
-to it. Usually the ``sendmail`` process will respond quickly as it spools your
-messages to disk before sending them.
-
-The Transport is named the Sendmail Transport for historical reasons
-(``sendmail`` was the "standard" UNIX tool for sending e-mail for years). It
-will send messages using other transfer agents such as Exim or Postfix despite
-its name, provided they have the relevant sendmail wrappers so that they can be
-started with the correct command-line flags.
-
-It's a common misconception that because the Sendmail Transport returns a
-result very quickly it must therefore deliver messages to recipients quickly
--- this is not true. It's not slow by any means, but it's certainly not
-faster than SMTP when it comes to getting messages to the intended recipients.
-This is because sendmail itself sends the messages over SMTP once they have
-been quickly spooled to disk.
-
-The Sendmail Transport has the potential to be just as smart of the SMTP
-Transport when it comes to notifying Swift Mailer about which recipients were
-rejected, but in reality the majority of locally installed ``sendmail``
-instances are not configured well enough to provide any useful feedback. As such
-Swift Mailer may report successful deliveries where they did in fact fail before
-they even left your server.
-
-You can run the Sendmail Transport in two different modes specified by command
-line flags:
-
-* "``-bs``" runs in SMTP mode so theoretically it will act like the SMTP
-  Transport
-
-* "``-t``" runs in piped mode with no feedback, but theoretically faster,
-  though not advised
-
-You can think of the Sendmail Transport as a sort of asynchronous SMTP Transport
--- though if you have problems with delivery failures you should try using the
-SMTP Transport instead. Swift Mailer isn't doing the work here, it's simply
-passing the work to somebody else (i.e. ``sendmail``).
-
-Using the Sendmail Transport
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To use the Sendmail Transport you simply need to call
-``Swift_SendmailTransport::newInstance()`` with the command as a parameter.
-
-To use the Sendmail Transport you need to know where ``sendmail`` or another MTA
-exists on the server. Swift Mailer uses a default value of
-``/usr/sbin/sendmail``, which should work on most systems.
-
-You specify the entire command as a parameter (i.e. including the command line
-flags). Swift Mailer supports operational modes of "``-bs``" (default) and
-"``-t``".
-
-.. note::
-
-    If you run sendmail in "``-t``" mode you will get no feedback as to whether
-    or not sending has succeeded. Use "``-bs``" unless you have a reason not to.
-
-To use the Sendmail Transport:
-
-* Call ``Swift_SendmailTransport::newInstance()`` with the command, including
-  the correct command line flags. The default is to use ``/usr/sbin/sendmail
-  -bs`` if this is not specified.
-
-* Use the returned object to create the Mailer.
-
-A sendmail process will be started upon the first call to ``send()``. If the
-process cannot be started successfully an Exception of type
-``Swift_TransportException`` will be thrown.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Transport
-    $transport = Swift_SendmailTransport::newInstance('/usr/sbin/exim -bs');
-
-    // Create the Mailer using your created Transport
-    $mailer = Swift_Mailer::newInstance($transport);
-
-The Mail Transport
-..................
-
-The Mail Transport sends messages by delegating to PHP's internal
-``mail()`` function.
-
-In my experience -- and others' -- the ``mail()`` function is not particularly
-predictable, or helpful.
-
-Quite notably, the ``mail()`` function behaves entirely differently between
-Linux and Windows servers. On linux it uses ``sendmail``, but on Windows it uses
-SMTP.
-
-In order for the ``mail()`` function to even work at all ``php.ini`` needs to be
-configured correctly, specifying the location of sendmail or of an SMTP server.
-
-The problem with ``mail()`` is that it "tries" to simplify things to the point
-that it actually makes things more complex due to poor interface design. The
-developers of Swift Mailer have gone to a lot of effort to make the Mail
-Transport work with a reasonable degree of consistency.
-
-Serious drawbacks when using this Transport are:
-
-* Unpredictable message headers
-
-* Lack of feedback regarding delivery failures
-
-* Lack of support for several plugins that require real-time delivery feedback
-
-It's a last resort, and we say that with a passion!
-
-Using the Mail Transport
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-To use the Mail Transport you simply need to call
-``Swift_MailTransport::newInstance()``. It's unlikely you'll need to configure
-the Transport.
-
-To use the Mail Transport:
-
-* Call ``Swift_MailTransport::newInstance()``.
-
-* Use the returned object to create the Mailer.
-
-Messages will be sent using the ``mail()`` function.
-
-.. note::
-
-    The ``mail()`` function can take a ``$additional_parameters`` parameter.
-    Swift Mailer sets this to "``-f%s``" by default, where the "%s" is
-    substituted with the address of the sender (via a ``sprintf()``) at send
-    time. You may override this default by passing an argument to
-    ``newInstance()``.
-
-    .. code-block:: php
-
-        require_once 'lib/swift_required.php';
-
-        // Create the Transport
-        $transport = Swift_MailTransport::newInstance();
-
-        // Create the Mailer using your created Transport
-        $mailer = Swift_Mailer::newInstance($transport);
-
-Available Methods for Sending Messages
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The Mailer class offers two methods for sending Messages -- ``send()``.
-Each behaves in a slightly different way.
-
-When a message is sent in Swift Mailer, the Mailer class communicates with
-whichever Transport class you have chosen to use.
-
-Each recipient in the message should either be accepted or rejected by the
-Transport. For example, if the domain name on the email address is not
-reachable the SMTP Transport may reject the address because it cannot process
-it. Whichever method you use -- ``send()`` -- Swift Mailer will return
-an integer indicating the number of accepted recipients.
-
-.. note::
-
-    It's possible to find out which recipients were rejected -- we'll cover that
-    later in this chapter.
-
-Using the ``send()`` Method
-...........................
-
-The ``send()`` method of the ``Swift_Mailer`` class sends a message using
-exactly the same logic as your Desktop mail client would use. Just pass it a
-Message and get a result.
-
-To send a Message with ``send()``:
-
-* Create a Transport from one of the provided Transports --
-  ``Swift_SmtpTransport``, ``Swift_SendmailTransport``,
-  ``Swift_MailTransport`` or one of the aggregate Transports.
-
-* Create an instance of the ``Swift_Mailer`` class, using the Transport as
-  it's constructor parameter.
-
-* Create a Message.
-
-* Send the message via the ``send()`` method on the Mailer object.
-
-The message will be sent just like it would be sent if you used your mail
-client. An integer is returned which includes the number of successful
-recipients. If none of the recipients could be sent to then zero will be
-returned, which equates to a boolean ``false``. If you set two
-``To:`` recipients and three ``Bcc:`` recipients in the message and all of the
-recipients are delivered to successfully then the value 5 will be returned.
-
-.. code-block:: php
-
-    require_once 'lib/swift_required.php';
-
-    // Create the Transport
-    $transport = Swift_SmtpTransport::newInstance('localhost', 25);
-
-    // Create the Mailer using your created Transport
-    $mailer = Swift_Mailer::newInstance($transport);
-
-    // Create a message
-    $message = Swift_Message::newInstance('Wonderful Subject')
-      ->setFrom(array('john@doe.com' => 'John Doe'))
-      ->setTo(array('receiver@domain.org', 'other@domain.org' => 'A name'))
-      ->setBody('Here is the message itself')
-      ;
-
-    // Send the message
-    $numSent = $mailer->send($message);
-
-    printf("Sent %d messages\n", $numSent);
-
-    /* Note that often that only the boolean equivalent of the
-       return value is of concern (zero indicates FALSE)
-
-    if ($mailer->send($message))
-    {
-      echo "Sent\n";
-    }
-    else
-    {
-      echo "Failed\n";
-    }
-
-    */
-
-Sending Emails in Batch
-.......................
-
-If you want to send a separate message to each recipient so that only their
-own address shows up in the ``To:`` field, follow the following recipe:
-
-* Create a Transport from one of the provided Transports --
-  ``Swift_SmtpTransport``, ``Swift_SendmailTransport``,
-  ``Swift_MailTransport`` or one of the aggregate Transports.
-
-* Create an instance of the ``Swift_Mailer`` class, using the Transport as
-  it's constructor parameter.
-
-* Create a Message.
-
-* Iterate over the recipients and send message via the ``send()`` method on
-  the Mailer object.
-
-Each recipient of the messages receives a different copy with only their own
-email address on the ``To:`` field.
-
-Make sure to add only valid email addresses as recipients. If you try to add an
-invalid email address with ``setTo()``, ``setCc()`` or ``setBcc()``, Swift
-Mailer will throw a ``Swift_RfcComplianceException``.
-
-If you add recipients automatically based on a data source that may contain
-invalid email addresses, you can prevent possible exceptions by validating the
-addresses using ``Swift_Validate::email($email)`` and only adding addresses
-that validate. Another way would be to wrap your ``setTo()``, ``setCc()`` and
-``setBcc()`` calls in a try-catch block and handle the
-``Swift_RfcComplianceException`` in the catch block.
-
-Handling invalid addresses properly is especially important when sending emails
-in large batches since a single invalid address might cause an unhandled
-exception and stop the execution or your script early.
-
-.. note::
-
-    In the following example, two emails are sent. One to each of
-    ``receiver@domain.org`` and ``other@domain.org``. These recipients will
-    not be aware of each other.
-
-    .. code-block:: php
-
-        require_once 'lib/swift_required.php';
-
-        // Create the Transport
-        $transport = Swift_SmtpTransport::newInstance('localhost', 25);
-
-        // Create the Mailer using your created Transport
-        $mailer = Swift_Mailer::newInstance($transport);
-
-        // Create a message
-        $message = Swift_Message::newInstance('Wonderful Subject')
-          ->setFrom(array('john@doe.com' => 'John Doe'))
-          ->setBody('Here is the message itself')
-          ;
-
-        // Send the message
-        $failedRecipients = array();
-        $numSent = 0;
-        $to = array('receiver@domain.org', 'other@domain.org' => 'A name');
-
-        foreach ($to as $address => $name)
-        {
-          if (is_int($address)) {
-            $message->setTo($name);
-          } else {
-            $message->setTo(array($address => $name));
-          }
-
-          $numSent += $mailer->send($message, $failedRecipients);
-        }
-
-        printf("Sent %d messages\n", $numSent);
-
-Finding out Rejected Addresses
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-It's possible to get a list of addresses that were rejected by the Transport
-by using a by-reference parameter to ``send()``.
-
-As Swift Mailer attempts to send the message to each address given to it, if a
-recipient is rejected it will be added to the array. You can pass an existing
-array, otherwise one will be created by-reference.
-
-Collecting the list of recipients that were rejected can be useful in
-circumstances where you need to "prune" a mailing list for example when some
-addresses cannot be delivered to.
-
-Getting Failures By-reference
-.............................
-
-Collecting delivery failures by-reference with the ``send()`` method is as
-simple as passing a variable name to the method call.
-
-To get failed recipients by-reference:
-
-* Pass a by-reference variable name to the ``send()`` method of the Mailer
-  class.
-
-If the Transport rejects any of the recipients, the culprit addresses will be
-added to the array provided by-reference.
-
-.. note::
-
-    If the variable name does not yet exist, it will be initialized as an
-    empty array and then failures will be added to that array. If the variable
-    already exists it will be type-cast to an array and failures will be added
-    to it.
-
-    .. code-block:: php
-
-        $mailer = Swift_Mailer::newInstance( ... );
-
-        $message = Swift_Message::newInstance( ... )
-          ->setFrom( ... )
-          ->setTo(array(
-            'receiver@bad-domain.org' => 'Receiver Name',
-            'other@domain.org' => 'A name',
-            'other-receiver@bad-domain.org' => 'Other Name'
-          ))
-          ->setBody( ... )
-          ;
-
-        // Pass a variable name to the send() method
-        if (!$mailer->send($message, $failures))
-        {
-          echo "Failures:";
-          print_r($failures);
-        }
-
-        /*
-        Failures:
-        Array (
-          0 => receiver@bad-domain.org,
-          1 => other-receiver@bad-domain.org
-        )
-        */
diff --git a/typo3/contrib/swiftmailer/doc/uml/Encoders.graffle b/typo3/contrib/swiftmailer/doc/uml/Encoders.graffle
deleted file mode 100644 (file)
index f895752..0000000
Binary files a/typo3/contrib/swiftmailer/doc/uml/Encoders.graffle and /dev/null differ
diff --git a/typo3/contrib/swiftmailer/doc/uml/Mime.graffle b/typo3/contrib/swiftmailer/doc/uml/Mime.graffle
deleted file mode 100644 (file)
index e1e33cb..0000000
Binary files a/typo3/contrib/swiftmailer/doc/uml/Mime.graffle and /dev/null differ
diff --git a/typo3/contrib/swiftmailer/doc/uml/Transports.graffle b/typo3/contrib/swiftmailer/doc/uml/Transports.graffle
deleted file mode 100644 (file)
index 5670e2b..0000000
Binary files a/typo3/contrib/swiftmailer/doc/uml/Transports.graffle and /dev/null differ
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift.php b/typo3/contrib/swiftmailer/lib/classes/Swift.php
deleted file mode 100644 (file)
index 1d1f821..0000000
+++ /dev/null
@@ -1,81 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * General utility class in Swift Mailer, not to be instantiated.
- *
- * @package Swift
- *
- * @author Chris Corbyn
- */
-abstract class Swift
-{
-    public static $initialized = false;
-    public static $inits = array();
-
-    /** Swift Mailer Version number generated during dist release process */
-    const VERSION = '@SWIFT_VERSION_NUMBER@';
-
-    /**
-     * Registers an initializer callable that will be called the first time
-     * a SwiftMailer class is autoloaded.
-     *
-     * This enables you to tweak the default configuration in a lazy way.
-     *
-     * @param mixed $callable A valid PHP callable that will be called when autoloading the first Swift class
-     */
-    public static function init($callable)
-    {
-        self::$inits[] = $callable;
-    }
-
-    /**
-     * Internal autoloader for spl_autoload_register().
-     *
-     * @param string $class
-     */
-    public static function autoload($class)
-    {
-        // Don't interfere with other autoloaders
-        if (0 !== strpos($class, 'Swift_')) {
-            return;
-        }
-
-        $path = dirname(__FILE__).'/'.str_replace('_', '/', $class).'.php';
-
-        if (!file_exists($path)) {
-            return;
-        }
-
-        require $path;
-
-        if (self::$inits && !self::$initialized) {
-            self::$initialized = true;
-            foreach (self::$inits as $init) {
-                call_user_func($init);
-            }
-        }
-    }
-
-    /**
-     * Configure autoloading using Swift Mailer.
-     *
-     * This is designed to play nicely with other autoloaders.
-     *
-     * @param mixed $callable A valid PHP callable that will be called when autoloading the first Swift class
-     */
-    public static function registerAutoload($callable = null)
-    {
-        if (null !== $callable) {
-            self::$inits[] = $callable;
-        }
-        spl_autoload_register(array('Swift', 'autoload'));
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/Attachment.php b/typo3/contrib/swiftmailer/lib/classes/Swift/Attachment.php
deleted file mode 100644 (file)
index 7fdbcb9..0000000
+++ /dev/null
@@ -1,73 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Attachment class for attaching files to a {@link Swift_Mime_Message}.
- *
- * @package    Swift
- * @subpackage Mime
- * @author     Chris Corbyn
- */
-class Swift_Attachment extends Swift_Mime_Attachment
-{
-    /**
-     * Create a new Attachment.
-     *
-     * Details may be optionally provided to the constructor.
-     *
-     * @param string|Swift_OutputByteStream $data
-     * @param string                        $filename
-     * @param string                        $contentType
-     */
-    public function __construct($data = null, $filename = null, $contentType = null)
-    {
-        call_user_func_array(
-            array($this, 'Swift_Mime_Attachment::__construct'),
-            Swift_DependencyContainer::getInstance()
-                ->createDependenciesFor('mime.attachment')
-            );
-
-        $this->setBody($data);
-        $this->setFilename($filename);
-        if ($contentType) {
-            $this->setContentType($contentType);
-        }
-    }
-
-    /**
-     * Create a new Attachment.
-     *
-     * @param string|Swift_OutputByteStream $data
-     * @param string                        $filename
-     * @param string                        $contentType
-     *
-     * @return Swift_Mime_Attachment
-     */
-    public static function newInstance($data = null, $filename = null, $contentType = null)
-    {
-        return new self($data, $filename, $contentType);
-    }
-
-    /**
-     * Create a new Attachment from a filesystem path.
-     *
-     * @param string $path
-     * @param string $contentType optional
-     *
-     * @return Swift_Mime_Attachment
-     */
-    public static function fromPath($path, $contentType = null)
-    {
-        return self::newInstance()->setFile(
-            new Swift_ByteStream_FileByteStream($path),
-            $contentType
-            );
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php b/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/AbstractFilterableInputStream.php
deleted file mode 100644 (file)
index e12c0dd..0000000
+++ /dev/null
@@ -1,183 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Provides the base functionality for an InputStream supporting filters.
- *
- * @package    Swift
- * @subpackage ByteStream
- * @author     Chris Corbyn
- */
-abstract class Swift_ByteStream_AbstractFilterableInputStream implements Swift_InputByteStream, Swift_Filterable
-{
-    /**
-     * Write sequence.
-     */
-    protected $_sequence = 0;
-
-    /**
-     * StreamFilters.
-     */
-    private $_filters = array();
-
-    /**
-     * A buffer for writing.
-     */
-    private $_writeBuffer = '';
-
-    /**
-     * Bound streams.
-     *
-     * @var Swift_InputByteStream[]
-     */
-    private $_mirrors = array();
-
-    /**
-     * Commit the given bytes to the storage medium immediately.
-     *
-     * @param string $bytes
-     */
-    abstract protected function _commit($bytes);
-
-    /**
-     * Flush any buffers/content with immediate effect.
-     */
-    abstract protected function _flush();
-
-    /**
-     * Add a StreamFilter to this InputByteStream.
-     *
-     * @param Swift_StreamFilter $filter
-     * @param string             $key
-     */
-    public function addFilter(Swift_StreamFilter $filter, $key)
-    {
-        $this->_filters[$key] = $filter;
-    }
-
-    /**
-     * Remove an already present StreamFilter based on its $key.
-     *
-     * @param string $key
-     */
-    public function removeFilter($key)
-    {
-        unset($this->_filters[$key]);
-    }
-
-    /**
-     * Writes $bytes to the end of the stream.
-     *
-     * @param string $bytes
-     *
-     * @return int
-     *
-     * @throws Swift_IoException
-     */
-    public function write($bytes)
-    {
-        $this->_writeBuffer .= $bytes;
-        foreach ($this->_filters as $filter) {
-            if ($filter->shouldBuffer($this->_writeBuffer)) {
-                return;
-            }
-        }
-        $this->_doWrite($this->_writeBuffer);
-
-        return ++$this->_sequence;
-    }
-
-    /**
-     * For any bytes that are currently buffered inside the stream, force them
-     * off the buffer.
-     *
-     * @throws Swift_IoException
-     */
-    public function commit()
-    {
-        $this->_doWrite($this->_writeBuffer);
-    }
-
-    /**
-     * Attach $is to this stream.
-     *
-     * The stream acts as an observer, receiving all data that is written.
-     * All {@link write()} and {@link flushBuffers()} operations will be mirrored.
-     *
-     * @param Swift_InputByteStream $is
-     */
-    public function bind(Swift_InputByteStream $is)
-    {
-        $this->_mirrors[] = $is;
-    }
-
-    /**
-     * Remove an already bound stream.
-     *
-     * If $is is not bound, no errors will be raised.
-     * If the stream currently has any buffered data it will be written to $is
-     * before unbinding occurs.
-     *
-     * @param Swift_InputByteStream $is
-     */
-    public function unbind(Swift_InputByteStream $is)
-    {
-        foreach ($this->_mirrors as $k => $stream) {
-            if ($is === $stream) {
-                if ($this->_writeBuffer !== '') {
-                    $stream->write($this->_writeBuffer);
-                }
-                unset($this->_mirrors[$k]);
-            }
-        }
-    }
-
-    /**
-     * Flush the contents of the stream (empty it) and set the internal pointer
-     * to the beginning.
-     *
-     * @throws Swift_IoException
-     */
-    public function flushBuffers()
-    {
-        if ($this->_writeBuffer !== '') {
-            $this->_doWrite($this->_writeBuffer);
-        }
-        $this->_flush();
-
-        foreach ($this->_mirrors as $stream) {
-            $stream->flushBuffers();
-        }
-    }
-
-    // -- Private methods
-
-    /** Run $bytes through all filters */
-    private function _filter($bytes)
-    {
-        foreach ($this->_filters as $filter) {
-            $bytes = $filter->filter($bytes);
-        }
-
-        return $bytes;
-    }
-
-    /** Just write the bytes to the stream */
-    private function _doWrite($bytes)
-    {
-        $this->_commit($this->_filter($bytes));
-
-        foreach ($this->_mirrors as $stream) {
-            $stream->write($bytes);
-        }
-
-        $this->_writeBuffer = '';
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/ArrayByteStream.php b/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/ArrayByteStream.php
deleted file mode 100644 (file)
index aa29597..0000000
+++ /dev/null
@@ -1,186 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Allows reading and writing of bytes to and from an array.
- *
- * @package    Swift
- * @subpackage ByteStream
- * @author     Chris Corbyn
- */
-class Swift_ByteStream_ArrayByteStream implements Swift_InputByteStream, Swift_OutputByteStream
-{
-    /**
-     * The internal stack of bytes.
-     *
-     * @var string[]
-     */
-    private $_array = array();
-
-    /**
-     * The size of the stack
-     *
-     * @var int
-     */
-    private $_arraySize = 0;
-
-    /**
-     * The internal pointer offset.
-     *
-     * @var int
-     */
-    private $_offset = 0;
-
-    /**
-     * Bound streams.
-     *
-     * @var Swift_InputByteStream[]
-     */
-    private $_mirrors = array();
-
-    /**
-     * Create a new ArrayByteStream.
-     *
-     * If $stack is given the stream will be populated with the bytes it contains.
-     *
-     * @param mixed $stack of bytes in string or array form, optional
-     */
-    public function __construct($stack = null)
-    {
-        if (is_array($stack)) {
-            $this->_array = $stack;
-            $this->_arraySize = count($stack);
-        } elseif (is_string($stack)) {
-            $this->write($stack);
-        } else {
-            $this->_array = array();
-        }
-    }
-
-    /**
-     * Reads $length bytes from the stream into a string and moves the pointer
-     * through the stream by $length.
-     *
-     * If less bytes exist than are requested the
-     * remaining bytes are given instead. If no bytes are remaining at all, boolean
-     * false is returned.
-     *
-     * @param int     $length
-     *
-     * @return string
-     */
-    public function read($length)
-    {
-        if ($this->_offset == $this->_arraySize) {
-            return false;
-        }
-
-        // Don't use array slice
-        $end = $length + $this->_offset;
-        $end = $this->_arraySize<$end
-            ?$this->_arraySize
-            :$end;
-        $ret = '';
-        for (; $this->_offset < $end; ++$this->_offset) {
-            $ret .= $this->_array[$this->_offset];
-        }
-
-        return $ret;
-    }
-
-    /**
-     * Writes $bytes to the end of the stream.
-     *
-     * @param string $bytes
-     */
-    public function write($bytes)
-    {
-        $to_add = str_split($bytes);
-        foreach ($to_add as $value) {
-            $this->_array[] = $value;
-        }
-        $this->_arraySize = count($this->_array);
-
-        foreach ($this->_mirrors as $stream) {
-            $stream->write($bytes);
-        }
-    }
-
-    /**
-     * Not used.
-     */
-    public function commit()
-    {
-    }
-
-    /**
-     * Attach $is to this stream.
-     *
-     * The stream acts as an observer, receiving all data that is written.
-     * All {@link write()} and {@link flushBuffers()} operations will be mirrored.
-     *
-     * @param Swift_InputByteStream $is
-     */
-    public function bind(Swift_InputByteStream $is)
-    {
-        $this->_mirrors[] = $is;
-    }
-
-    /**
-     * Remove an already bound stream.
-     *
-     * If $is is not bound, no errors will be raised.
-     * If the stream currently has any buffered data it will be written to $is
-     * before unbinding occurs.
-     *
-     * @param Swift_InputByteStream $is
-     */
-    public function unbind(Swift_InputByteStream $is)
-    {
-        foreach ($this->_mirrors as $k => $stream) {
-            if ($is === $stream) {
-                unset($this->_mirrors[$k]);
-            }
-        }
-    }
-
-    /**
-     * Move the internal read pointer to $byteOffset in the stream.
-     *
-     * @param int     $byteOffset
-     *
-     * @return bool
-     */
-    public function setReadPointer($byteOffset)
-    {
-        if ($byteOffset > $this->_arraySize) {
-            $byteOffset = $this->_arraySize;
-        } elseif ($byteOffset < 0) {
-            $byteOffset = 0;
-        }
-
-        $this->_offset = $byteOffset;
-    }
-
-    /**
-     * Flush the contents of the stream (empty it) and set the internal pointer
-     * to the beginning.
-     */
-    public function flushBuffers()
-    {
-        $this->_offset = 0;
-        $this->_array = array();
-        $this->_arraySize = 0;
-
-        foreach ($this->_mirrors as $stream) {
-            $stream->flushBuffers();
-        }
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/FileByteStream.php b/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/FileByteStream.php
deleted file mode 100644 (file)
index 6f1d87e..0000000
+++ /dev/null
@@ -1,233 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Allows reading and writing of bytes to and from a file.
- *
- * @package    Swift
- * @subpackage ByteStream
- * @author     Chris Corbyn
- */
-class Swift_ByteStream_FileByteStream extends Swift_ByteStream_AbstractFilterableInputStream implements Swift_FileStream
-{
-    /** The internal pointer offset */
-    private $_offset = 0;
-
-    /** The path to the file */
-    private $_path;
-
-    /** The mode this file is opened in for writing */
-    private $_mode;
-
-    /** A lazy-loaded resource handle for reading the file */
-    private $_reader;
-
-    /** A lazy-loaded resource handle for writing the file */
-    private $_writer;
-
-    /** If magic_quotes_runtime is on, this will be true */
-    private $_quotes = false;
-
-    /** If stream is seekable true/false, or null if not known */
-    private $_seekable = null;
-
-    /**
-     * Create a new FileByteStream for $path.
-     *
-     * @param string  $path
-     * @param bool    $writable if true
-     */
-    public function __construct($path, $writable = false)
-    {
-        if (empty($path)) {
-            throw new Swift_IoException('The path cannot be empty');
-        }
-        $this->_path = $path;
-        $this->_mode = $writable ? 'w+b' : 'rb';
-
-        if (function_exists('get_magic_quotes_runtime') && @get_magic_quotes_runtime() == 1) {
-            $this->_quotes = true;
-        }
-    }
-
-    /**
-     * Get the complete path to the file.
-     *
-     * @return string
-     */
-    public function getPath()
-    {
-        return $this->_path;
-    }
-
-    /**
-     * Reads $length bytes from the stream into a string and moves the pointer
-     * through the stream by $length.
-     *
-     * If less bytes exist than are requested the
-     * remaining bytes are given instead. If no bytes are remaining at all, boolean
-     * false is returned.
-     *
-     * @param int     $length
-     *
-     * @return string|bool
-     *
-     * @throws Swift_IoException
-     */
-    public function read($length)
-    {
-        $fp = $this->_getReadHandle();
-        if (!feof($fp)) {
-            if ($this->_quotes) {
-                ini_set('magic_quotes_runtime', 0);
-            }
-            $bytes = fread($fp, $length);
-            if ($this->_quotes) {
-                ini_set('magic_quotes_runtime', 1);
-            }
-            $this->_offset = ftell($fp);
-            
-            // If we read one byte after reaching the end of the file
-            // feof() will return false and an empty string is returned
-            if ($bytes === '' && feof($fp)) {
-               $this->_resetReadHandle();
-               
-               return false;
-            }
-
-            return $bytes;
-        }
-
-        $this->_resetReadHandle();
-
-        return false;
-    }
-
-    /**
-     * Move the internal read pointer to $byteOffset in the stream.
-     *
-     * @param int     $byteOffset
-     *
-     * @return bool
-     */
-    public function setReadPointer($byteOffset)
-    {
-        if (isset($this->_reader)) {
-            $this->_seekReadStreamToPosition($byteOffset);
-        }
-        $this->_offset = $byteOffset;
-    }
-
-    // -- Private methods
-
-    /** Just write the bytes to the file */
-    protected function _commit($bytes)
-    {
-        fwrite($this->_getWriteHandle(), $bytes);
-        $this->_resetReadHandle();
-    }
-
-    /** Not used */
-    protected function _flush()
-    {
-    }
-
-    /** Get the resource for reading */
-    private function _getReadHandle()
-    {
-        if (!isset($this->_reader)) {
-            if (!$this->_reader = fopen($this->_path, 'rb')) {
-                throw new Swift_IoException(
-                    'Unable to open file for reading [' . $this->_path . ']'
-                );
-            }
-            if ($this->_offset <> 0) {
-                $this->_getReadStreamSeekableStatus();
-                $this->_seekReadStreamToPosition($this->_offset);
-            }
-        }
-
-        return $this->_reader;
-    }
-
-    /** Get the resource for writing */
-    private function _getWriteHandle()
-    {
-        if (!isset($this->_writer)) {
-            if (!$this->_writer = fopen($this->_path, $this->_mode)) {
-                throw new Swift_IoException(
-                    'Unable to open file for writing [' . $this->_path . ']'
-                );
-            }
-        }
-
-        return $this->_writer;
-    }
-
-    /** Force a reload of the resource for reading */
-    private function _resetReadHandle()
-    {
-        if (isset($this->_reader)) {
-            fclose($this->_reader);
-            $this->_reader = null;
-        }
-    }
-
-    /** Check if ReadOnly Stream is seekable */
-    private function _getReadStreamSeekableStatus()
-    {
-        $metas = stream_get_meta_data($this->_reader);
-        $this->_seekable = $metas['seekable'];
-    }
-
-    /** Streams in a readOnly stream ensuring copy if needed */
-    private function _seekReadStreamToPosition($offset)
-    {
-        if ($this->_seekable===null) {
-            $this->_getReadStreamSeekableStatus();
-        }
-        if ($this->_seekable === false) {
-            $currentPos = ftell($this->_reader);
-            if ($currentPos<$offset) {
-                $toDiscard = $offset-$currentPos;
-                fread($this->_reader, $toDiscard);
-
-                return;
-            }
-            $this->_copyReadStream();
-        }
-        fseek($this->_reader, $offset, SEEK_SET);
-    }
-
-    /** Copy a readOnly Stream to ensure seekability */
-    private function _copyReadStream()
-    {
-        if ($tmpFile = fopen('php://temp/maxmemory:4096', 'w+b')) {
-            /* We have opened a php:// Stream Should work without problem */
-        } elseif (function_exists('sys_get_temp_dir') && is_writable(sys_get_temp_dir()) && ($tmpFile = tmpfile())) {
-            /* We have opened a tmpfile */
-        } else {
-            throw new Swift_IoException('Unable to copy the file to make it seekable, sys_temp_dir is not writable, php://memory not available');
-        }
-        $currentPos = ftell($this->_reader);
-        fclose($this->_reader);
-        $source = fopen($this->_path, 'rb');
-        if (!$source) {
-            throw new Swift_IoException('Unable to open file for copying [' . $this->_path . ']');
-        }
-        fseek($tmpFile, 0, SEEK_SET);
-        while (!feof($source)) {
-            fwrite($tmpFile, fread($source, 4096));
-        }
-        fseek($tmpFile, $currentPos, SEEK_SET);
-        fclose($source);
-        $this->_reader = $tmpFile;
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/TemporaryFileByteStream.php b/typo3/contrib/swiftmailer/lib/classes/Swift/ByteStream/TemporaryFileByteStream.php
deleted file mode 100644 (file)
index f35f885..0000000
+++ /dev/null
@@ -1,44 +0,0 @@
-<?php
-
-/*
-* This file is part of SwiftMailer.
-* (c) 2004-2009 Chris Corbyn
-*
-* For the full copyright and license information, please view the LICENSE
-* file that was distributed with this source code.
-*/
-
-/**
- * @package    Swift
- * @subpackage ByteStream
- * @author     Romain-Geissler
- */
-class Swift_ByteStream_TemporaryFileByteStream extends Swift_ByteStream_FileByteStream
-{
-    public function __construct()
-    {
-        $filePath = tempnam(sys_get_temp_dir(), 'FileByteStream');
-
-        if ($filePath === false) {
-            throw new Swift_IoException('Failed to retrieve temporary file name.');
-        }
-
-        parent::__construct($filePath, true);
-    }
-
-    public function getContent()
-    {
-        if (($content = file_get_contents($this->getPath())) === false) {
-            throw new Swift_IoException('Failed to get temporary file content.');
-        }
-
-        return $content;
-    }
-
-    public function __destruct()
-    {
-        if (file_exists($this->getPath())) {
-            @unlink($this->getPath());
-        }
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader.php b/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader.php
deleted file mode 100644 (file)
index 91a9c96..0000000
+++ /dev/null
@@ -1,69 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Analyzes characters for a specific character set.
- *
- * @package    Swift
- * @subpackage Encoder
- * @author     Chris Corbyn
- * @author     Xavier De Cock <xdecock@gmail.com>
- */
-interface Swift_CharacterReader
-{
-    const MAP_TYPE_INVALID = 0x01;
-    const MAP_TYPE_FIXED_LEN = 0x02;
-    const MAP_TYPE_POSITIONS = 0x03;
-
-    /**
-     * Returns the complete character map
-     *
-     * @param string  $string
-     * @param int     $startOffset
-     * @param array   $currentMap
-     * @param mixed   $ignoredChars
-     *
-     * @return int
-     */
-    public function getCharPositions($string, $startOffset, &$currentMap, &$ignoredChars);
-
-    /**
-     * Returns the mapType, see constants.
-     *
-     * @return int
-     */
-    public function getMapType();
-
-    /**
-     * Returns an integer which specifies how many more bytes to read.
-     *
-     * A positive integer indicates the number of more bytes to fetch before invoking
-     * this method again.
-     *
-     * A value of zero means this is already a valid character.
-     * A value of -1 means this cannot possibly be a valid character.
-     *
-     * @param integer[] $bytes
-     * @param int       $size
-     *
-     * @return int
-     */
-    public function validateByteSequence($bytes, $size);
-
-    /**
-     * Returns the number of bytes which should be read to start each character.
-     *
-     * For fixed width character sets this should be the number of octets-per-character.
-     * For multibyte character sets this will probably be 1.
-     *
-     * @return int
-     */
-    public function getInitialByteSize();
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/GenericFixedWidthReader.php b/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/GenericFixedWidthReader.php
deleted file mode 100644 (file)
index 6547612..0000000
+++ /dev/null
@@ -1,99 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Provides fixed-width byte sizes for reading fixed-width character sets.
- *
- * @package    Swift
- * @subpackage Encoder
- * @author     Chris Corbyn
- * @author     Xavier De Cock <xdecock@gmail.com>
- */
-class Swift_CharacterReader_GenericFixedWidthReader implements Swift_CharacterReader
-{
-    /**
-     * The number of bytes in a single character.
-     *
-     * @var int
-     */
-    private $_width;
-
-    /**
-     * Creates a new GenericFixedWidthReader using $width bytes per character.
-     *
-     * @param int     $width
-     */
-    public function __construct($width)
-    {
-        $this->_width = $width;
-    }
-
-    /**
-     * Returns the complete character map.
-     *
-     * @param string  $string
-     * @param int     $startOffset
-     * @param array   $currentMap
-     * @param mixed   $ignoredChars
-     *
-     * @return int
-     */
-    public function getCharPositions($string, $startOffset, &$currentMap, &$ignoredChars)
-    {
-        $strlen = strlen($string);
-        // % and / are CPU intensive, so, maybe find a better way
-        $ignored = $strlen % $this->_width;
-        $ignoredChars = substr($string, - $ignored);
-        $currentMap = $this->_width;
-
-        return ($strlen - $ignored) / $this->_width;
-    }
-
-    /**
-     * Returns the mapType.
-     *
-     * @return int
-     */
-    public function getMapType()
-    {
-        return self::MAP_TYPE_FIXED_LEN;
-    }
-
-    /**
-     * Returns an integer which specifies how many more bytes to read.
-     *
-     * A positive integer indicates the number of more bytes to fetch before invoking
-     * this method again.
-     *
-     * A value of zero means this is already a valid character.
-     * A value of -1 means this cannot possibly be a valid character.
-     *
-     * @param string  $bytes
-     * @param int     $size
-     *
-     * @return int
-     */
-    public function validateByteSequence($bytes, $size)
-    {
-        $needed = $this->_width - $size;
-
-        return ($needed > -1) ? $needed : -1;
-    }
-
-    /**
-     * Returns the number of bytes which should be read to start each character.
-     *
-     * @return int
-     */
-    public function getInitialByteSize()
-    {
-        return $this->_width;
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/UsAsciiReader.php b/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/UsAsciiReader.php
deleted file mode 100644 (file)
index 8d03f31..0000000
+++ /dev/null
@@ -1,85 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Analyzes US-ASCII characters.
- *
- * @package    Swift
- * @subpackage Encoder
- * @author     Chris Corbyn
- */
-class Swift_CharacterReader_UsAsciiReader implements Swift_CharacterReader
-{
-    /**
-     * Returns the complete character map.
-     *
-     * @param string  $string
-     * @param int     $startOffset
-     * @param array   $currentMap
-     * @param string  $ignoredChars
-     *
-     * @return int
-     */
-    public function getCharPositions($string, $startOffset, &$currentMap, &$ignoredChars)
-    {
-        $strlen=strlen($string);
-        $ignoredChars='';
-        for ($i = 0; $i < $strlen; ++$i) {
-            if ($string[$i]>"\x07F") { // Invalid char
-                $currentMap[$i+$startOffset]=$string[$i];
-            }
-        }
-
-        return $strlen;
-    }
-
-    /**
-     * Returns mapType
-     *
-     * @return int     mapType
-     */
-    public function getMapType()
-    {
-        return self::MAP_TYPE_INVALID;
-    }
-
-    /**
-     * Returns an integer which specifies how many more bytes to read.
-     *
-     * A positive integer indicates the number of more bytes to fetch before invoking
-     * this method again.
-     * A value of zero means this is already a valid character.
-     * A value of -1 means this cannot possibly be a valid character.
-     *
-     * @param string  $bytes
-     * @param int     $size
-     *
-     * @return int
-     */
-    public function validateByteSequence($bytes, $size)
-    {
-        $byte = reset($bytes);
-        if (1 == count($bytes) && $byte >= 0x00 && $byte <= 0x7F) {
-            return 0;
-        } else {
-            return -1;
-        }
-    }
-
-    /**
-     * Returns the number of bytes which should be read to start each character.
-     *
-     * @return int
-     */
-    public function getInitialByteSize()
-    {
-        return 1;
-    }
-}
diff --git a/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/Utf8Reader.php b/typo3/contrib/swiftmailer/lib/classes/Swift/CharacterReader/Utf8Reader.php
deleted file mode 100644 (file)
index 900bad5..0000000
+++ /dev/null
@@ -1,181 +0,0 @@
-<?php
-
-/*
- * This file is part of SwiftMailer.
- * (c) 2004-2009 Chris Corbyn
- *
- * For the full copyright and license information, please view the LICENSE
- * file that was distributed with this source code.
- */
-
-/**
- * Analyzes UTF-8 characters.
- *
- * @package    Swift
- * @subpackage Encoder
- * @author     Chris Corbyn
- * @author     Xavier De Cock <xdecock@gmail.com>
- */
-class Swift_CharacterReader_Utf8Reader implements Swift_CharacterReader
-{
-    /** Pre-computed for optimization */
-    private static $length_map=array(
-        // N=0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F,
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x0N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x1N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x2N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x3N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x4N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x5N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x6N
-        1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1, // 0x7N
-        0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 0x8N
-        0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 0x9N
-        0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 0xAN
-        0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 0xBN
-        2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2, // 0xCN
-        2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2, // 0xDN
-        3,3,3,3,3,3,3,3,3,3,3,3,3,3,3,3, // 0xEN
-        4,4,4,4,4,4,4,4,5,5,5,5,6,6,0,0  // 0xFN
-    );
-
-    private static $s_length_map=array(
-        "\x00"=>1, "\x01"=>1, "\x02"=>1, "\x03"=>1, "\x04"=>1, "\x05"=>1, "\x06"=>1, "\x07"=>1,
-        "\x08"=>1, "\x09"=>1, "\x0a"=>1, "\x0b"=>1, "\x0c"=>1, "\x0d"=>1, "\x0e"=>1, "\x0f"=>1,
-        "\x10"=>1, "\x11"=>1, "\x12"=>1, "\x13"=>1, "\x14"=>1, "\x15"=>1, "\x16"=>1, "\x17"=>1,
-        "\x18"=>1, "\x19"=>1, "\x1a"=>1, "\x1b"=>1, "\x1c"=>1, "\x1d"=>1, "\x1e"=>1, "\x1f"=>1,
-        "\x20"=>1, "\x21"=>1, "\x22"=>1, "\x23"=>1, "\x24"=>1, "\x25"=>1, "\x26"=>1, "\x27"=>1,
-        "\x28"=>1, "\x29"=>1, "\x2a"=>1, "\x2b"=>1, "\x2c"=>1, "\x2d"=>1, "\x2e"=>1, "\x2f"=>1,
-        "\x30"=>1, "\x31"=>1, "\x32"=>1, "\x33"=>1, "\x34"=>1, "\x35"=>1, "\x36"=>1, "\x37"=>1,
-        "\x38"=>1, "\x39"=>1, "\x3a"=>1, "\x3b"=>1, "\x3c"=>1, "\x3d"=>1, "\x3e"=>1, "\x3f"=>1,
-        "\x40"=>1, "\x41"=>1, "\x42"=>1, "\x43"=>1, "\x44"=>1, "\x45"=>1, "\x46"=>1, "\x47"=>1,
-        "\x48"=>1, "\x49"=>1, "\x4a"=>1, "\x4b"=>1, "\x4c"=>1, "\x4d"=>1, "\x4e"=>1, "\x4f"=>1,
-        "\x50"=>1, "\x51"=>1, "\x52"=>1, "\x53"=>1, "\x54"=>1, "\x55"=>1, "\x56"=>1, "\x57"=>1,
-        "\x58"=>1, "\x59"=>1, "\x5a"=>1, "\x5b"=>1, "\x5c"=>1, "\x5d"=>1, "\x5e"=>1, "\x5f"=>1,
-        "\x60"=>1, "\x61"=>1, "\x62"=>1, "\x63"=>1, "\x64"=>1, "\x65"=>1, "\x66"=>1, "\x67"=>1,
-        "\x68"=>1, "\x69"=>1, "\x6a"=>1, "\x6b"=>1, "\x6c"=>1, "\x6d"=>1, "\x6e"=>1, "\x6f"=>1,
-        "\x70"=>1, "\x71"=>1, "\x72"=>1, "\x73"=>1, "\x74"=>1, "\x75"=>1, "\x76"=>1, "\x77"=>1,
-        "\x78"=>1, "\x79"=>1, "\x7a"=>1, "\x7b"=>1, "\x7c"=>1, "\x7d"=>1, "\x7e"=>1, "\x7f"=>1,
-        "\x80"=>0, "\x81"=>0, "\x82"=>0, "\x83"=>0, "\x84"=>0, "\x85"=>0, "\x86"=>0, "\x87"=>0,
-        "\x88"=>0, "\x89"=>0, "\x8a"=>0, "\x8b"=>0, "\x8c"=>0, "\x8d"=>0, "\x8e"=>0, "\x8f"=>0,
-        "\x90"=>0, "\x91"=>0, "\x92"=>0, "\x93"=>0, "\x94"=>0, "\x95"=>0, "\x96"=>0, "\x97"=>0,
-        "\x98"=>0, "\x99"=>0, "\x9a"=>0, "\x9b"=>0, "\x9c"=>0, "\x9d"=>0, "\x9e"=>0, "\x9f"=>0,
-        "\xa0"=>0, "\xa1"=>0, "\xa2"=>0, "\xa3"=>0, "\xa4"=>0, "\xa5"=>0, "\xa6"=>0, "\xa7"=>0,
-        "\xa8"=>0, "\xa9"=>0, "\xaa"=>0, "\xab"=>0, "\xac"=>0, "\xad"=>0, "\xae"=>0, "\xaf"=>0,
-        "\xb0"=>0, "\xb1"=>0, "\xb2"=>0, "\xb3"=>0, "\xb4"=>0, "\xb5"=>0, "\xb6"=>0, "\xb7"=>0,
-        "\xb8"=>0, "\xb9"=>0, "\xba"=>0, "\xbb"=>0, "\xbc"=>0, "\xbd"=>0, "\xbe"=>0, "\xbf"=>0,
-        "\xc0"=>2, "\xc1"=>2, "\xc2"=>2, "\xc3"=>2, "\xc4"=>2, "\xc5"=>2, "\xc6"=>2, "\xc7"=>2,
-        "\xc8"=>2, "\xc9"=>2, "\xca"=>2, "\xcb"=>2, "\xcc"=>2, "\xcd"=>2, "\xce"=>2, "\xcf"=>2,
-        "\xd0"=>2, "\xd1"=>2, "\xd2"=>2, "\xd3"=>2, "\xd4"=>2, "\xd5"=>2, "\xd6"=>2, "\xd7"=>2,
-        "\xd8"=>2, "\xd9"=>2, "\xda"=>2, "\xdb"=>2, "\xdc"=>2, "\xdd"=>2, "\xde"=>2, "\xdf"=>2,
-        "\xe0"=>3, "\xe1"=>3, "\xe2"=>3, "\xe3"=>3, "\xe4"=>3, "\xe5"=>3, "\xe6"=>3, "\xe7"=>3,