Skip to content
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

Emails are not being send #211

Closed
faethon opened this issue Apr 17, 2024 · 2 comments
Closed

Emails are not being send #211

faethon opened this issue Apr 17, 2024 · 2 comments

Comments

@faethon
Copy link

faethon commented Apr 17, 2024

I seems to be having a problem with sending emails. I have added the config to seahub_settings.py conform the instructions from Seafile:
(Using a app password from Gmail.)

EMAIL_USE_TLS = True
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_HOST_USER = 'email@email.com'
EMAIL_HOST_PASSWORD = 'app_password'
EMAIL_PORT = 587
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
SERVER_EMAIL = EMAIL_HOST_USER

Whenever an email needs to be send I get a notification that says

"Successfully reset password to ------, but failed to send email to 5fde94bf------------------5697af@auth.local, please check your email configuration."

I am running the latest ggogel/seafile-containerized docker file with seafile 11.0.6.

As per issue 5933 I have tried to add the following to the environment of the seahub container, but this does not seem to solve anything.

SSL_CERT_FILE=/etc/ssl/certs/cabundle.pem

Furthermore, that pem file is not available at that location within the container:

Looking in seahub.log I see this error popping up when trying to send an email:
[WARNING] seahub.api2.endpoints.admin.users:1508 put [Errno -3] Try again

@ggogel
Copy link
Owner

ggogel commented Apr 17, 2024

Is your seahub container only in the internal network seafile-net? Then it won't be able to reach gmail.com. Refer to this wiki article with the similar situation when using LDAP https://github.com/ggogel/seafile-containerized/wiki/LDAP

@faethon
Copy link
Author

faethon commented Apr 17, 2024

Thanks so much. That was indeed the problem. The stack was not accessing outside.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants