Store Content of outgoing mail messages in the database

[stefanzweifel]

On Twitter the question came up, why the package doesn't store the content/body of outgoging mails.
I honestly didn't think about that at all, as my primary usecase for the packge is to keep track of meta data.

Implementing this feature is trivial, as the Swif_Message instance exposes a getBody() method.

The feature is hidden behind a new configuration flag (sends.store_content) and has to be enabled by the consumer of the package. I will keep it that way in future releases, as I would like to prevent users from shooting themself in the foot. Storing the body of outgoing mails can blow up the size of a database pretty quickly.

Questions to clarify

• Should I create an additional migration to add the content-column? Or should this be the concern of the consumer? (Like done in the UPGRADE guide for v0 to v1) → Will make this a new major version. The package is too young to already add multiple migrations to it. Will provide instructions in the upgrade guide