wekan-snap
wekan-snap copied to clipboard
Feature Request: Setting key to disable mail server certificate validity verification
Hello,
When I try to send me a test mail I have this error :
Error trying to send email: Hostname/IP doesn't match certificate's altnames:
It happens because the mail server certificate is a wildcard for *.myorganisation.com
, and it is used also for the adress smtp.mymail.myorganisation.com
, so the verification fails.
Could it be possible to have a setting to set rejectUnauthorized
to false
? Default should remain true
as it mitigate risks of man-in-the-middle attack.
Either the feature request is accepted or rejected : How can I use this kind of workaround with a snap installation ?
Regards.
Hello,
Any advice or workaround ? (I can't invite people to use Wekan with me so I feel quite lonely !)
Regards.
@GuiGuiSoft
When you have logged out of Wekan, and your Wekan server is for example http://example.com
, new users can register at http://example.com/sign-up
. Ignore email error. Then that new registered user can login at http://example.com/sign-in
. After that, in some Wekan board, at left sidebar where board member avatars are visible, click +
button to add that new user to shared Wekan board.
On Standalone Wekan, including Snap, if you don't have admin access to Wekan or some board, you can add admin access when you need it to Wekan or some board
Thank you for your answer @xet7 .
As it is a corporate instance, I disabled self-inscription in the panel admin so only invited people could log-in. (I am waiting for LDAP integration soooo much :smile: )
Will this method work even if self-inscription is disabled ?
Regards.
@GuiGuiSoft
I rely on Wekan users for reporting all bugs at https://github.com/wekan/wekan/issues .
Wekan snap-specific issues are here https://github.com/wekan/wekan-snap/issues .
Wekan docker-specific issues are here https://github.com/wekan/wekan-mongodb/issues .
Please test your Wekan, search issues and add comment or new issue if some info is wrong. Usually open issues still are not fixed, and closed issues are already fixed. If I don't get bug report, I don't know something does not work.
Most self-registration bugs are already on roadmap to be fixed, I think.
Excuse me, I have deviated from the initial feature request, which is about snap I think (setting key).
How can I know if the feature request will be included in the roadmap (or if you refuse, or if you ask for a pull request) ?
@GuiGuiSoft
https://github.com/wekan/wekan/wiki/FAQ#will-my-feature-request-be-implemented
If some use my Commercial Support, I can pay my bills, and add every bugfix and feature requested.
I need to refuse some feature requests, if they would get me into trouble somehow.
The solution is described in the Wekan wiki!
You need to set the SMTP host in your admin panel to:
mail.example.com:587/?ignoreTLS=true&tls={rejectUnauthorized:false}&secure=false