New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v3] no mails are being sent #4760
Comments
Is there any more logs after that? This is the action preparing to perform and then performing. There should be a bit more logs on whether it succeeded or failed |
Yes. Here the complete log. (anonymized)
And here the smtp part from .env. (anonymized too) SMTP_SENDER_EMAIL=noreply@my.domain Username and password I tried. But this makes no difference. My mailserver does not need auth. I allowed the bbb ip to mail. thanks! t. |
As far as Greenlight is concered, the email was sent. Can you check your spam and your SMTP server to see if potentially it was blocked there? |
I tried telnet from within the greenlight docker container and this worked.
So there seems to be no network or other problem. The mailserver is under my control. There is no connection attempt when greenlight is sending mail although greenlight says so. How can I debug this further? cheers, t. |
Honestly, I'm not quite sure at this point. From Greenlight's perspective, the email was sent. Assuming you've configured your |
Thank you. Maybe one question. Is it mandatory to fill in smtp_user, smtp_pass and smtp_auth in .env although no authentication is needed?
cheers, t.
Am 7. Februar 2023 15:25:13 MEZ schrieb Ahmad Farhat ***@***.***>:
…Honestly, I'm not quite sure at this point. From Greenlight's perspective, the email was sent. Assuming you've configured your `.env` variables correctly and restarted Greenlight after the changes, then the only explanation is your SMTP server stopping the email from being sent
|
Try completely removing |
Then the docker container refuses to start complaining about the missing variable.
I take it it is supposed to work sending mail with beta15, right? Could you share a working .env file? I mean with mailing configured? Anonymized obviousely.
cheers, t.
Am 7. Februar 2023 16:13:21 MEZ schrieb Ahmad Farhat ***@***.***>:
…Try completely removing `SMTP_USERNAME`, `SMTP_PASSWORD`, and `SMTP_AUTH`
|
After further testing I found out that even with this entries in .env:
I get this in the logs:
So this messages do not mean very much. Is the location ~/greenlight-v3/.env even right? cheers, t. |
Here's what I have locally (not recommended for production)
|
Are you sure you're restarting Greenlight after making |
Unless I'm not schizophrenic I'm pretty much sure, yes. :) But it seems I'm the only one affected. Let me start from scratch and see what happens then.
cheers, t.
Am 9. Februar 2023 20:46:33 MEZ schrieb Ahmad Farhat ***@***.***>:
…Are you sure you're restarting Greenlight after making `.env` changes?
|
I started from scratch completely. Same outcome. Strange. This is of course a dev system. If you like to have a look, I can put your public ssh-key on that machine. cheers, t. |
Can you try using another SMTP server? Maybe a google one through gmail? |
Tried my gmail account. Same thing. I guess for some reason the $SMTP values are not processed because as I said even with empty values success messages appear in the docker logs. |
The success logs you sent are related to the controller itself - not the actual sending of an email -> This is the log related to emails that you need to see:
|
Try doing the following: Set your
Go to line 73 and replace
Try to send an email while watchingthe logs |
Now I get:
Setting SMTP_AUTH now...stay tuned. |
Now we have a read timeout.
Whats that suppose to mean? |
Cna you send me your SMTP settings (with things blanked out) |
SMTP_SENDER_EMAIL=noreply@letsmeet.my.domain |
Try setting SMTP_TLS=true (making sure to remove the # before |
Yeah, this cannot work.
I'll try all possible settings now and get back to you. Thanks for the debug commands. |
I'm working on a configuration check task that should make your life easier if you can wait a few hours |
Just a quick chime in, I'm sure this is on your roadmap but yes it would be nice if SMTP settings could be managed within GL Administration were as soon as you change Registration Method to Approve/Decline or force apply SMTP setup you should then be prompted for settings. Maybe also offer a test send button after docker has reloaded when save/update is exec. |
@himpierre There is a new configuration rake task with the latest beta of Greenlight. First upgrade Greenlight, then run @bayden10 That's a bit tricky. Rails requires a full restart to apply the mailer changes, which is why they can't be fields in the UI. There are a few changes we need to make in terms of feedback to the user when choosing an option that requires SMTP |
Check command gives me:
Thanks for leaving the debug option to true. Still not able to send mail though. Will try tomorrow a bit more. cheers, t. |
yup, I get the same issue when running configuration:check |
Add a |
Does mailing work for you @bayden10? If so, what's your mail server setup? cheers, t. |
Started exim in debug mode. This is what I get:
So greenlight just drops the connection. I'm out of ideas here. |
Can you run the configuration check command again |
Net::ReadTimeout is very strange. I tried delivering a mail via telnet from within the docker container and it worked. I don't know why ruby fails. Like they don't understand each other. |
We can go through a few troubleshooting steps 1 by 1. |
Progress! I need to open port 113 and port 25 (iptables) on the greenlight machine. That's kinda odd. (maybe the bbb-install-2.6.sh script forgets to set the statefull firewall rules?) |
@himpierre , been busy but port 113? does this mean port forwarding is required for NATed hosts? Still an issue Docker Log ` greenlight-v3 | E, [2023-02-15T16:30:48.569965 #129] ERROR -- : [ActiveJob] [ActionMailer::MailDeliveryJob] [a4381605-d577-4c7c-aa80-3d5faa1d994a] Error performing ActionMailer::MailDeliveryJob (Job ID: a4381605-d577-4c7c-aa80-3d5faa1d994a) from Async(greenlight_v3_production_mailing) in 152.87ms: OpenSSL::SSL::SSLError (SSL_connect returned=1 errno=0 peeraddr=x.x.x.x:587 state=error: wrong version number): ` Config Check ` ` my config ` ` |
@bayden10 uncomment |
same:
|
Yeah. Somehow the new greenlight version needs to be reached from outside when sending mail. I guess that's new? In fact until now I never had to fiddle with firewall settings. |
@himpierre are you behind NAT? |
Nope. It's a regular dedicated server.
Am 15. Februar 2023 18:10:31 MEZ schrieb bayden10 ***@***.***>:
…
@himpierre are you behind NAT?
|
Alright. To summarize things up. The main reason mailing did not work was this. My mailserver tries to contact the connecting server on port 113 when there is authentication involved. Timeout was 5s. This is obviousely to long for the ruby process on the greenlight machine and ruby hangs up. After I disabled that lookup no firewall rules are needed anymore and all works as expected. Remaining question @farhatahmad: It does not seem to be possible to not enter credentials in the mail settings. So we are forced to use authentication. I would prefer to just let the greenlight machine mail along without authentication by accepting mails from their ip address. Could you please have a look at this? cheers, t. |
We'll make a change to allow Greenlight to connect to SMTP without authentication |
@himpierre , @farhatahmad I was sure it was working |
Interesting. Still fails for me. Care to share the anonymized .env?
cheers, t.
Am 28. Februar 2023 08:21:20 MEZ schrieb anmg ***@***.***>:
…
@himpierre , @farhatahmad
I just uncommented login and password lines without assining anything there
it worked for the server without authentification
|
SOLVED using this #1574 |
Hello @himpierre @farhatahmad we encountered the same issue here #5400 which since then has evolved also to a time out issue with this .env config
I'm able to send mail via this infomaniak smtp from the server with an openssl command (couldn't try from the docker itself as I don't think openssl or telnet command exist in the container)
as far as I understood the exchange, do you think we should create a firewall rule to drive a reply from the smtp server to greenlight docker internal ip to finish the authentication mechanism and avoid the time out ? In this case what should be this port ? any advice would be super welcome as we are now a bit clueless ! |
Hello Faced with a similar problem. When you try to send an invitation, the system does not manage, does not send any connections to the mail server, checked for 2 different smtp. I have a dedicated server for BBB with an external IP. Ubuntu 22.04.4 LTS Tried turning off UFW - it didn't help. Is there any solution? docker logs greenlight-v3 It can be seen that the token is generated, and if you copy it manually and paste it in the browser, you can complete the registration. |
Describe the bug
I have set the SMTP variables in .env and I can see, greenlight is trying to sent mail but it never makes a connect to my configured mail server. Here is what I see in the logs.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Mails are recieved.
Actual behavior
No mails.
Greenligght: 3.0 beta 15
BigBlueButton: 2.6.0-rc2
The text was updated successfully, but these errors were encountered: