huan/docker-simple-mail-forwarder

Cert Hostname DOES NOT VERIFY (* != simple-mail-forwarder.com)

Open

#71 opened on Apr 20, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Shell (563 stars) (92 forks)user submission
help wanted

Description

Is there any way to change this? Gmail has started to refuse to work with this since earlier this month. checktls.com also catches this error.

Related thread: https://support.google.com/mail/thread/38336515?msgid=39890656

I tried setting -e SMF_DOMAIN=mydomain.com as #10 but no luck.

Contributor guide

Tech stack
dockershell
Domain
devopsinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Docker basicsSSL/TLS knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the Dockerfile and how environment variable SMF DOMAIN is used. Check if the hostname verification can be disabled or if a proper certificate needs to be configured. Look at related issue #10 and the Google support thread for context. The fix may involve adding an option to set the certificate common name or skip verification.
Cert Hostname DOES NOT VERIFY (* != simple-mail-forwarder.com) · huan/docker-simple-mail-forwarder#71 | Good First Issue