mattermost / mattermost/docker
Problem with SMTP Mail verification
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 533
- Forks
- 284
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I try to use a custom Mail Server to send emails to user, to verify login. I tried different settings but always get this error:
Here are my configs:
And here is my log:
{"timestamp":"2024-10-04 08:21:06.130 Z","level":"warn","msg":"Error decoding the config","caller":"api4/system.go:207","path":"/api/v4/email/test","request_id":"cii43nktxiffteigjih3eg8kwe","ip_addr":"172.18.0.3","user_id":"1rd9yxud3tbumd5b6kngjgpduo","method":"POST","error":"EOF"}
{"timestamp":"2024-10-04 08:21:16.133 Z","level":"error","msg":"Connection unsuccessful: unable to connect to the SMTP server: dial tcp 162.55.254.207:587: i/o timeout","caller":"web/context.go:117","path":"/api/v4/email/test","request_id":"cii43nktxiffteigjih3eg8kwe","ip_addr":"172.18.0.3","user_id":"1rd9yxud3tbumd5b6kngjgpduo","method":"POST","err_where":"testEmail","http_code":500,"error":"testEmail: Connection unsuccessful: unable to connect to the SMTP server: dial tcp 162.55.254.207:587: i/o timeout"}
I’ve double-checked the configuration of my web server, and everything seems to be set up correctly. However, I’m still encountering the issues. I would really appreciate any guidance or help you can provide.
One more thing, I am using caddy (as a reverse Proxy) with the following settings:
mattermost.techmountain.dev {
reverse_proxy mattermost:8065
}
I already asked this question here:
Thank you
Best regards,
lemmi25
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /api/v4/email/test request and the log locations api4/system.go:207 and web/context.go:117. Check the reported SMTP connection timeout and the Docker deployment and Caddy reverse-proxy configuration. This issue does not define a code change or a clear completion condition; done would require identifying and documenting the cause or a verified configuration fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100