Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Silverstripe CMS 4 update #11

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

NightJar
Copy link

@NightJar NightJar commented Jan 23, 2020

This work updates the module to be compatible with Silverstripe 4, and the SwiftMailer subsystem used with it. It does this by employing a plugin for SwiftMailer to do the encryption and signing - but still ultimately relies on the same backing GPG library for PHP.

Closes #10

Dylan Wagstaff and others added 5 commits October 10, 2019 14:52
…ixes just PHP fatal error but the module is not usable yet
Silverstripe CMS 4 has updated its mailing backend, which is now powered by SwiftMailer.
SwiftMailer has existing support for signers and encryption, and via this interface the GPGMailer
module has been cleaned up a lot. This also now implements a PGP/MIME message format, as defined
by RFC 3156.

Reference:
 - https://tools.ietf.org/html/rfc3156
 - https://www.mailpile.is/blog/2014-11-21_To_PGP_MIME_Or_Not.html
MAJOR upgrade to Silverstripe 4 - via SwiftMailer
@NightJar NightJar mentioned this pull request Jan 23, 2020
@thomasbnielsen
Copy link

Hi @NightJar in need of the SS4 version, but not sure how to do the following part in SS4
$email->set_mailer(new GPGMailer());
Can you perhaps update the documentation for SS4 also? Would be a great help

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SS4 compatibility
3 participants