-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of S/MIME Signing #296
Labels
Comments
Looking forward to your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I would like to send signed mails with a valid S/MIME certificate and for this reason I have already looked into the go-mail middleware.
Describe the solution you'd like
After consultation with @wneessen the implementation of the S/MIME feature in the core of go-mail seems to make more sense than within a go-mail middleware.
Describe alternatives you've considered
The issue wneessen/go-mail-middleware#49 can be seen as the start and reference for the discussion
Additional context
Content-Type: multipart/signed; protocol=”application/pkcs7-signature“; micalg=sha-256; boundary=”----=_Part_0_1161688972.1725478215506“
with reference to the net message and signature partsTest Content
and should be adopted in the first part withContent-Type
andContent-Transfer-Encoding
Content-Type: application/pkcs7-signature; name="smime.p7s"; smime-type=signed-data
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
A valid S/MIME mail could look like this:
The text was updated successfully, but these errors were encountered: