You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The ContentType of the message should be set to Content-Type: multipart/signed; protocol=”application/pkcs7-signature“; micalg=sha-256; boundary=”----=_Part_0_1161688972.1725478215506“ with reference to the net message and signature parts
For example, the actual net body is Test Content and should be adopted in the first part with Content-Type and Content-Transfer-Encoding
The subsequent part, i.e. the signature, would need the following headers, followed by the signature in base64 encoding.
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: