Delta Chat developer here. Only seeing this thread/topic here now. I believe the issue is fixed but not yet released yet. Here is a “nightly” apk which you could use to try connecting. Would be grateful about feedback if it works now. https://download.delta.chat/android/nightly/2020-10-15/deltachat-gplay-debug-1.13.4.apk – problem is i couldn’t install this on my e.foundation phone – as i couldn’t find a way to install from file. Is there something special to allow installing from a file on e.foundation phones? Any help appreciated. note that the tutorial https://community.e.foundation/t/install-an-app-from-a-3rd-party-source-or-apk-file-directly/13341does not fit with my install – my samsung 7 (ordered from shop) or so was updated August 31, android 7.1.2 /e/OS-20200831170819 … and after spending half an hour trying to figure out how to install APK’s i gave up for now. This was a no-brainer on lineage therefor i am clueless.
Hello,
…tried the mentionned dev-version of DC from above, unfortunately the error persist…
here is the log-text:
This log may contain sensitive information. If you want to post it publicly you may examine and edit it beforehand.
device=samsung SM-G398FN (xcover4seea)
android=10 (G398FNXXS8BTJ3, QP1A.190711.020.G398FNXXS8BTJ3)
sdk=29
memory=7M (19.44% free, 512M max)
memoryClass=192
host=SWDI2013
applicationId=chat.delta.beta
app=Delta Chat 1.13.4-gplay-debug
installer=com.google.android.packageinstaller
ignoreBatteryOptimizations=false
notifications=true
reliableService=false
arch=64
bcc_self=0
blobdir=/data/user/0/chat.delta.beta/files/messenger.db-blobs
configured_mvbox_folder=
configured_sentbox_folder=
database_dir=/data/user/0/chat.delta.beta/files/messenger.db
database_version=69
deltachat_core_version=v1.46.0
display_name=0
e2ee_enabled=1
entered_account_settings=xxx.xxx@e.email imap:xxx.xxx@e.email::mail.ecloud.global:993:cert_automatic smtp:xxx.xxx@e.email::mail.ecloud.global:587:cert_automatic 0
fingerprint=
folders_configured=0
inbox_watch=1
is_configured=0
journal_mode=wal
level=awesome
mdns_enabled=1
messages_in_contact_requests=0
mvbox_move=1
mvbox_watch=1
number_of_chat_messages=0
number_of_chats=0
number_of_contacts=0
private_key_count=0
public_key_count=0
selfavatar=
sentbox_watch=1
sqlite_version=3.33.0
uptime=0h 2m 2s
used_account_settings=unset imap:unset:0:unset:0:cert_automatic smtp:unset:0:unset:0:cert_automatic 0
maybe, this could help clarifying…
greetings,
npfp (thread-starter)
thanks! could you maybe provide the actual log lines? Could you maybe attach the full log file as a file here?
Thanks for the fast response!
Hello and thank you for making deta chat. I try but the same 111 error ccured with the Dev version.
ok, i think we just found the issue. the e.email provider has one IPV6 and one IPV4 address. IPV6 delivers connection refused while IPV4 works (you can verify this yourself):
$ host mail.ecloud.global
mail.ecloud.global has address 135.181.85.105
mail.ecloud.global has IPv6 address 2a01:4f9:c010:c4fd::1
$ telnet 2a01:4f9:c010:c4fd::1 587
Trying 2a01:4f9:c010:c4fd::1...
telnet: Unable to connect to remote host: Connection refused
$ telnet 135.181.85.105 587
Connected to 135.181.85.105.
We are going to think on the Delta Chat side if we can make this work automatically. But “e.email” probably shouldn’t advertise an IPV6 address if it doesn’t accept connections on the smtp-port it advertises in its autoconfig settings (https://autoconfig.e.email/mail/config-v1.1.xml?emailaddress=deltatest%40e.email ).
If anyone knows who could be CCed on this issue, or how it could be reported to e.email sysadmins that’d be very helpful. thanks!
Pl send the details to support@e.email
k, i sent a mail there.
Thanks a lot for figuring this out.
Deat hpk,
first of all: thanx for this peace of software which can push using email to the next level !! 
here again the error-log when using the above-mentionned dev-version of DC:
device=samsung SM-G398FN (xcover4seea)
android=10 (G398FNXXS8BTJ3, QP1A.190711.020.G398FNXXS8BTJ3)
sdk=29
memory=7M (19.44% free, 512M max)
memoryClass=192
host=SWDI2013
applicationId=chat.delta.beta
app=Delta Chat 1.13.4-gplay-debug
installer=com.google.android.packageinstaller
ignoreBatteryOptimizations=false
notifications=true
reliableService=false
arch=64
bcc_self=0
blobdir=/data/user/0/chat.delta.beta/files/messenger.db-blobs
configured_mvbox_folder=
configured_sentbox_folder=
database_dir=/data/user/0/chat.delta.beta/files/messenger.db
database_version=69
deltachat_core_version=v1.46.0
display_name=0
e2ee_enabled=1
entered_account_settings=xxx.xxx@e.email imap: xxx.xxx@e.email::mail.ecloud.global:993:cert_automatic smtp:
xxx.xxx@e.email::mail.ecloud.global:587:cert_automatic 0
fingerprint=
folders_configured=0
inbox_watch=1
is_configured=0
journal_mode=wal
level=awesome
mdns_enabled=1
messages_in_contact_requests=0
mvbox_move=1
mvbox_watch=1
number_of_chat_messages=0
number_of_chats=0
number_of_contacts=0
private_key_count=0
public_key_count=0
selfavatar=
sentbox_watch=1
sqlite_version=3.33.0
uptime=0h 2m 2s
used_account_settings=unset imap:unset:0:unset:0:cert_automatic smtp:unset:0:unset:0:cert_automatic 0
hope that could help…
Problem is solved Thanks to Arnau: https://community.e.foundation/t/ipv6-smtp-e-mail-server-bug/21989
So all DC installs are working for all e.email accounts nicely right now – please confirm 
@tyxo @Sebu @Manoj @anon38440295 @hpk
Thanx for all the hard work,
a fabulous app working again !! 
I’d suggest to close the thread…
Greetings from Mainz, Germany,
npfp
[btw, I think its time to donate to the DC-project…]