Store complete Swift_Message object in mail_queue database #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Column is used for storing serialized Swift_Message object
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes bug #17.
By using this approach, a complete Swift_Message object, including attachments, is stored into the mail_queue database.
Note: attachements have to be added as Dynamic Content! http://swiftmailer.org/docs/messages.html#attaching-dynamic-content
When sending the mail from queue, the stored Swift_Message obect is retrieved and sent.
The table columns
to,cc,bcc,subject,html_body,text_body,charsetare now obsolete and can be removed.