An error occured during email delivery. Please contact an administrator!

1,706 views
Skip to first unread message

Dhaval

unread,
Jun 25, 2019, 1:24:12 PM6/25/19
to BigBlueButton-dev
Hi, 

I keep getting this error: 
An error occured during email delivery. Please contact an administrator! 

Any help would be appreciated

Fred Dixon

unread,
Jun 25, 2019, 3:11:19 PM6/25/19
to BigBlueButton-dev
Hi,

We would recommend setting up Greenlight v2, see



Regards,... Fred

--
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 post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/cb626f34-027e-4e71-8fe3-44b1586a1790%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
BigBlueButton Developer
@bigbluebutton

Dhaval

unread,
Jun 25, 2019, 9:30:16 PM6/25/19
to BigBlueButton-dev
Hi Fred, I am using Greenlight V2. Is there any way to view a log for the SMTP authentication as I feel like there might be an error there. 
Dhaval


On Tuesday, 25 June 2019 20:11:19 UTC+1, Fred Dixon wrote:
Hi,

We would recommend setting up Greenlight v2, see



Regards,... Fred

On Tue, Jun 25, 2019 at 1:24 PM Dhaval <dsone...@gmail.com> wrote:
Hi, 

I keep getting this error: 
An error occured during email delivery. Please contact an administrator! 

Any help would be appreciated

--
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 bigblueb...@googlegroups.com.

Ahmad Farhat

unread,
Jun 26, 2019, 11:14:59 AM6/26/19
to BigBlueButton-dev
You can follow the steps here to verify that you have correctly configured SMTP. The output of the command should give you a more detailed explanation of why it is not working.


You can also check the logs for Greenlight by following the steps listed here:

Dhaval

unread,
Jun 26, 2019, 11:44:53 AM6/26/19
to BigBlueButton-dev
I ran the rake check command and I get this error. 

Checking SMTP connection: Failed
Error connecting to SMTP - 535-5.7.8 Username and Password not accepted. Learn more at

Strangely there is no link it just says 'Learn more at' and then ends. 
And my config looks like this:

# Set this to true if you want GreenLight to send verification emails upon
# the creation of a new account
#
#ALLOW_MAIL_NOTIFICATIONS=true
#
# The notifications are sent using sendmail, unless the SMTP_SERVER variable is set.
# In that case, make sure the rest of the variables are properly set.
#
#   SMTP_SERVER=smtp.gmail.com
#   SMTP_PORT=587
#   SMTP_DOMAIN=gmail.com
#   SMTP_USERNAME=<your...@gmail.com>
#   SMTP_PASSWORD=<yourpassword>
#   SMTP_AUTH=plain
#   SMTP_STARTTLS_AUTO=true
#
SMTP_SERVER=smtp.gmail.com
SMTP_PORT=587
SMTP_DOMAIN=gmail.com
SMTP_USERNAME=us...@mydomain.com
SMTP_PASSWORD=mypassword1
SMTP_AUTH=plain
SMTP_STARTTLS_AUTO=true

# Specify the email address that all mail is sent from
SMTP_SENDER=us...@mydomain.com


GREENLIGHT_MAIL_NOTIFICATIONS=true
GREENLIGHT_USE_WEBHOOKS=true


Is there anything wrong with my config? I am using G Suite. 

Ahmad Farhat

unread,
Jun 26, 2019, 5:54:16 PM6/26/19
to BigBlueButton-dev
Your SMTP_DOMAIN should be equal to mydomain.com

Once you make that change, run the command from my previous answer again. You should receive a "Critical Security Alert" on your Gmail account. You can then follow the steps there to get your SMTP configuration up and running

Dhaval

unread,
Jun 26, 2019, 8:58:04 PM6/26/19
to BigBlueButton-dev
The rake check command returns no errors 

Checking environment: Passed
Checking Connection: Passed
Checking Secret: Passed
Checking SMTP connection: Passed

However I am still receiving the same error. The log in ~/greenlight/log/production.log only shows rendering text success messages and some SQL. I have turned on insecure app access on my google account as well but the error persists when I try to make a new account. 

Chad Pilkey

unread,
Jun 27, 2019, 12:57:40 PM6/27/19
to BigBlueButton-dev
Did you follow the steps to restart the container correctly after making the environment variable change? http://docs.bigbluebutton.org/greenlight/gl-install.html#applying-env-changes

Dhaval

unread,
Jun 27, 2019, 2:04:46 PM6/27/19
to BigBlueButton-dev
Yup! I am very confused by this issue. Have you or anybody else managed to get SMTP working with g suite?

Ahmad Farhat

unread,
Jun 27, 2019, 4:37:59 PM6/27/19
to BigBlueButton-dev
What is the output of running the following command:

docker exec greenlight-v2 /bin/bash -c "printenv | grep 'SMTP_DOMAIN'"

Dhaval

unread,
Jun 27, 2019, 6:29:29 PM6/27/19
to BigBlueButton-dev
It returns SMTP_DOMAIN=mydomain.com (following the example domain I wrote earlier). 

My domain is however a .academy domain. Could this be a problem?

German Acevedo

unread,
Jun 27, 2019, 6:55:00 PM6/27/19
to BigBlueButton-dev
Hi Dhaval,
This how I succeeded to use Gmail to send the invitations:
  • Configured the smtp section on the .env file as follows:
# Set this to true if you want GreenLight to send verification emails upon
# the creation of a new account
#
   ALLOW_MAIL_NOTIFICATIONS=true
#
# The notifications are sent using sendmail, unless the SMTP_SERVER variable is set.
# In that case, make sure the rest of the variables are properly set.
#
#   SMTP_SERVER=smtp.gmail.com
#   SMTP_PORT=587
#   SMTP_DOMAIN=gmail.com
#   SMTP_USERNAME=<your...@gmail.com>
#   SMTP_PASSWORD=<yourpassword>
#   SMTP_AUTH=plain
#   SMTP_STARTTLS_AUTO=true
#
SMTP_SERVER=smtp.gmail.com
SMTP_PORT=587
SMTP_DOMAIN=gmail.com
SMTP_USERNAME=acevedo...@gmail.com
SMTP_PASSWORD=**********
SMTP_AUTH=plain
SMTP_STARTTLS_AUTO=true

# Specify the email address that all mail is sent from
  • Turned on the switch on Allow less secure apps ON on my Gmail account (https://myaccount.google.com/lesssecureapps?pli=1)
  • Executed the check command: docker run --rm --env-file .env bigbluebutton/greenlight:v2 bundle exec rake conf:check (This time it passed all the checks!!!)
  • Turned OFF my Greenlight with the command: docker-compose down
  • Turned ON my Greenlight with the command docker-compose up -d
  • Restarted my BBB server with the command bbb-conf --restart
Everything is working now!

Hope this helps you!

 

Dhaval

unread,
Jun 28, 2019, 5:26:33 PM6/28/19
to BigBlueButton-dev
Hey German, it worked! 

The restart did the trick. Maybe we could get the docs updated over here: https://docs.bigbluebutton.org/greenlight-v1.html#configure-the-greenlight-to-send-emails to add bbb-conf --restart to the instructions as it only says to restart the docker image. 

Thank you all. :) 

Chad Pilkey

unread,
Jun 28, 2019, 6:05:14 PM6/28/19
to BigBlueButton-dev
I don't see how "bbb-conf --restart" could have had any effect. There's no references to "docker" or "greenlight" in the bbb-conf script. https://github.com/bigbluebutton/bigbluebutton/blob/master/bigbluebutton-config/bin/bbb-conf

The only component related to GL that the restart would touch is nginx and that would only make a difference if the nginx definition for GL was changed and you'd be getting different errors if it needed updating.

German Acevedo

unread,
Jun 28, 2019, 6:29:11 PM6/28/19
to BigBlueButton-dev
Hi Dahval and Chad,
I don't know why but every time I restart Greenlight I get a 404 error until I restart BigBlueButton, that's why I do this every time I change something in my .env file.  Glad to know that it worked for you also Dahval.
Regards,
German

Dorian Caval

unread,
Jun 20, 2020, 3:34:25 PM6/20/20
to BigBlueButton-dev
Sometimes when you restart Greenlight, if you are on a slower server - it takes around 45 seconds to get it up & running.
Even while you ssh will says it's up, it takes additional time to start up in the background.
Reply all
Reply to author
Forward
0 new messages