I searched and seem to see that the admin has some global email setting but I can’t find that on my admin page
How does one configure this to send notifications via email?
You need to configure seafile to know how to contact an email server and send emails. It is documented here:
https://manual.seafile.com/12.0/config/sending_email/
Thank you @tomservo
I saw that but wasn’t sure if it was the right approach
I’m still trying to learn the docker environment. How do I restart seafile after making congig changes. I have been rebooting the whole box but a seafile restart and seahub restart would be niice I just don’t know where to do that in the docker
I think the mail are here: /opt/seafile-data/seafile/logs
The file seahub_email_sender.log is empty BUT if I do a grep -i mail* sea*
I see
[2025-07-01 16:24:51] Start seafevents.main
seafile-monitor.log:/opt/seafile/seafile-pro-server-12.0.14/pro/python/seafevents/main.py:66: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See SSLContext infinite recursion in Python 3.6 · Issue #1016 · gevent/gevent · GitHub. Modules that had direct imports (NOT patched): [‘urllib3.util.ssl_ (/opt/seafile/seafile-pro-server-12.0.14/seahub/thirdpart/urllib3/util/ssl_.py)’, ‘urllib3.util (/opt/seafile/seafile-pro-server-12.0.14/seahub/thirdpart/urllib3/util/init.py)’, ‘jwt.jwks_client (/opt/seafile/seafile-pro-server-12.0.14/seahub/thirdpart/jwt/jwks_client.py)’].
seafile-monitor.log:[2025-07-01 16:30:13.441016] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:30:15.078920] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 16:35:31.009761] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:35:31.071701] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 16:40:36.918246] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:40:36.922285] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 16:45:41.691760] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:45:41.698550] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 16:50:49.046129] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:50:49.050693] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 16:55:57.281572] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 16:55:57.286704] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 17:01:02.827527] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 17:01:02.831531] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 17:06:07.789189] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 17:06:07.793851] Finish sending file updates emails.
seafile-monitor.log:[2025-07-01 17:11:12.818928] Start sending file updates emails…
seafile-monitor.log:[2025-07-01 17:11:12.822856] Finish sending file updates emails.
seahub.log:[2025-06-30 23:57:44] [ERROR] seahub.api2.endpoints.send_upload_link_email:100 post Connection unexpectedly closed
seahub.log:[2025-07-01 16:33:00] [ERROR] seahub.api2.endpoints.send_share_link_email:108 post Connection unexpectedly closed
seahub.log.2025-06-30:[2025-06-30 23:22:56] [ERROR] seahub.utils.mail:128 send_html_email_with_dj_template [Errno -2] Name or service not known
seahub.log.2025-06-30:[2025-06-30 23:22:56] [ERROR] seahub.api2.utils:326 send_share_link_emails Failed to send code via email to domdis@gdc.com
seahub.log.2025-06-30:[2025-06-30 23:23:21] [ERROR] seahub.utils.mail:128 send_html_email_with_dj_template [Errno -2] Name or service not known
seahub.log.2025-06-30:[2025-06-30 23:23:21] [ERROR] seahub.api2.utils:326 send_share_link_emails Failed to send code via email to domdis@gdc.com
seahub.log.2025-06-30:[2025-06-30 23:23:26] [ERROR] seahub.api2.endpoints.send_share_link_email:108 post [Errno -2] Name or service not known
I think that’s just “docker compose down” and then “docker compose up” unless you have already set it up so that systemd starts it. If you have added a unit to systemd, it would be something like “systemctl restart docker-compose.service”.