mirror of
https://github.com/decke/smtprelay.git
synced 2026-04-25 12:55:54 +03:00
[GH-ISSUE #185] Client certificate authentication (Office 365 connector) #42
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/smtprelay#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JadRho on GitHub (Feb 18, 2025).
Original GitHub issue: https://github.com/decke/smtprelay/issues/185
Could client certificate authentication be used for the remote smtp server ?
The use case is for Office 365 with the connector enabled for subject name in the certificate.
local_cert and local_key are used only for the local part not with the upstream connection to the smtp server.
@decke commented on GitHub (Feb 22, 2025):
It's definitely not possible at the moment but I can check if our SMTP client code can support it in the future.
@Bert-Proesmans commented on GitHub (Dec 13, 2025):
This feature would be useful to me too!
I looked into the code and it looks like the tls.Config struct could be configured with "Certificates" (https://pkg.go.dev/crypto/tls#Config). If my deduction is correct, then this feature (luckily) requires some plumbing to complete. I'll make an attempt, but don't hold your breath because my Go is bad.
github.com/decke/smtprelay@780ac71f74/smtp.go (L338-L343)github.com/decke/smtprelay@780ac71f74/smtp.go (L364-L372)