Debugging Greenlight Mail Sending

[Klaus Hermann]

Hello everyone,

I try to make greenlight send mails to users via an existing mail account.

I know my account information are correct (I send mails via python script with the credentials in another use case), but i cannot figure out the correct smtp entries for my mail provider in .env file:

ALLOW_MAIL_NOTIFICATIONS=true

SMTP_SENDER=mai...@gibt.de (should not really matter I guess)
SMTP_SERVER=alfa3216.alfahosting-server.de (works in Python script)
SMTP_PORT=465 (works in Python script)
SMTP_DOMAIN=gibt.de (not really sure but tried everything here)
SMTP_USERNAME=myloginname (works in Python script)
SMTP_PASSWORD=mypassword (works in Python script)
SMTP_AUTH=plain (works in Python script)
SMTP_STARTTLS_AUTO=false (tried both, false and true)

Everything I have tried results in the following:

docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check

Checking environment: Passed
Checking Connection: Passed
Checking Secret: Passed
Checking SMTP connection: Failed
Error connecting to SMTP - Net::ReadTimeout

Currently I am at a point where (I think) I have tried every possible combination and need to dig deeper.

Can anyone point me in the right direction on how I can get more verbose output?

I am new to ruby but can handle docker.

[Ali Alhaidary]

I think you should check another key regarding the domain cert which is above the mail settings.

SMTP_OPENSSL_VERIFY_MODE=none

And try port 25 instead of 465, and put your user name in full as username@domainname

Ali

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/baf624f8-1d8f-4562-94d8-53bb4022d83an%40googlegroups.com.

[Rory]

Can you open a connection to the server on port 465 using nc or similar? The error looks as though the box can't communicate with the server, perhaps an inbound fw rule on the provider side, or outbound rule on your box?

[Klaus Hermann]

Thanks for the netcat hint. Learned something new today. Unfortunately that seems not to be the issue here:

     nc -vz alfa3216.alfahosting-server.de 465

     Connection to alfa3216.alfahosting-server.de 465 port [tcp/urd] succeeded!