I tried using the egg in https://paste.c-net.org/UnlawfulComfy and it has the same issue. The only signal I see that I know for sure that the conf file was updated properly is if when I click OK and the settings box closes. If after pressing OK it doesn't close, I know for sure that the conf file wa...

That's great to hear, good job mate, glad to hear it! :) Indeed that output of the python code is the expected result like mine always looked like, so was baffled at your output seemingly hanging after tls initiation, prior to the sendmail() call. Btw, about your previous post about not being able ...

I got it to work on Debian too! I just thought of something that might work and it did. Let me explain. So my setup is like this: Site A <-> IPsec tunnel <-> Site B The deluge we were troubleshooting was in Site B and all its traffic goes through the tunnel to Site A and eventually to the Internet. ...

Synology test result: So it worked! It also gave me the critical security alert warning like you and I just turned on less secure apps access for that as a workaround for the test. So I'm not really sure why it's not working for my Debian box considering that the deluge docker containers are exactly...

Yeah, I have an updated Debian. As for the Synology, I started fresh because the Deluge container I have there was not setup for Notifications to work ever. I put the Notifications2 egg in the plugins folder, restarted the container, and saw both Notifications and Notifications2 in the plugins secti...

I saw that the LSIO deluge image was using ubuntu 18.04.1, so I downloaded the iso and fired it up in a VM to test the code-sections I posted earlier plus deluge and the moded plugin, in the livecd - unfortuently could not reproduce there neither, as works fine for me with deluge and the moded noti...

Sorry Kevin, I also thought to myself that you obviously would know that since posting usefull troubleshooting data so much, and it's me that's a docker/LSIO noob here :) I'm guessing it's a TLS/smtplib/python issue, as even though it shows the notifications plugin issue from a ssl.c file, so sound...

Your docker exec syntax is correct. I'm familiar with it and I usually open a terminal inside of the running container when troubleshooting things. That's how I got the /usr/lib references in my previous posts. Here you go: For the openssl test: root@f55733cd79cc:/# openssl s_client -connect smtp.gm...

It still doesn't work but we're getting closer. Thank you for your effort, I really appreciate it :) It looks like it is using the correct Notifications2 egg now but it somehow failing the SSL handshake: Line 1608: 22:44:27 [DEBUG ][deluge_notifications2.core :212 ] ENABLING CORE NOTIFICATIONS Line ...

Still not working :( Line 395: 01:04:55 [DEBUG ][deluge_notifications.core :212 ] ENABLING CORE NOTIFICATIONS Line 7351: 01:14:20 [DEBUG ][deluge_notifications.common :52 ] Calling CORE custom email providers for TorrentFinishedEvent: ('5fff0e1c8ac414860310bcc1cb76ac28e960efbe',) {} Line 7352: 01:14...