Config issue with echo bot changing server domain

Bots
1

I’m trying to get my feet wet with DC bots, starting from How to set up a delta-bot in 7 steps. I managed to start the echo bot using an address env. var. like ADDR='foo@posteo.net' and its respective password in PASSWORD, but DC seems to turn foo@posteo.net into foo@posteo.net@posteo.de which seems to cause this autoconfig issue (?) below. Any ideas? Should I post this on GitHub and where?

2020-12-24 22:18:45,574 - deltabot - ERROR - Failed to configure: DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:82: Configure ...
DC_EVENT_CONFIGURE_PROGRESS data1=1 data2=None
DC_EVENT_CONFIGURE_PROGRESS data1=200 data2=None
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:458: checking internal provider-info for offline autoconfig
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:470: offline autoconfig found
DC_EVENT_CONFIGURE_PROGRESS data1=500 data2=None
DC_EVENT_CONFIGURE_PROGRESS data1=550 data2=None
DC_EVENT_CONFIGURE_PROGRESS data1=600 data2=None
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:541: Trying: smtp: foo@posteo.net@posteo.de:587 security=STARTTLS certificate_checks=automatic oauth2=false
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:516: Trying: imap: foo@posteo.net@posteo.de:143 security=STARTTLS certificate_checks=automatic oauth2=false
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:544: failure: SMTP: failed to connect: io: future timed out
DC_EVENT_WARNING data1=0 data2=src/imap/mod.rs:385: try_setup_handle: io: Cannot assign requested address (os error 99)
DC_EVENT_INFO data1=0 data2=src/configure/mod.rs:519: failure: io: Cannot assign requested address (os error 99)
DC_EVENT_CONFIGURE_PROGRESS data1=800 data2=None
DC_EVENT_CONFIGURE_PROGRESS data1=0 data2=Error:

“io: Cannot assign requested address (os error 99)”
FAIL: failed to configure with: foo@posteo.net
FAIL: account not configured: /home/jovyan/bots/foo_posteo.net/account.db
2

The log message foo@posteo.net@posteo.de:587 means it tries to connect to posteo.de:587 and login as foo@posteo.net.

The real error here is that connection to posteo.de:587 timed out. Which operating system are you using? Can you connect to this account with Thunderbird? What is the result of running nmap -p 587 posteo.de?

3

Meanwhile, after trying another email provider, I also suspected a network access issue. In fact, I’m using this from mybinder.org running https://github.com/deeplook/dcbot to get a quick Linux OS as I’m on macOS which DC sadly seems to have a harder time to build on. So on a docker/binder this Python code hangs (but on my local machine it works ok): import imaplib; m = imaplib.IMAP4_SSL('posteo.net'). I have to find out why/how binder is causing/blocking this…

4

Turns out that mybinder allows only http(s), git, rsync, xroot, see https://github.com/jupyterhub/mybinder.org-deploy/blob/8051ea04774ac5a6f25c370a2177943b0fe77224/mybinder/values.yaml#L44.

But using https://github.com/jupyterhub/repo2docker I can run the repo in a local docker container, which kind of is good enough for me.

So feel free to close this, and thanks!