🧪 Help testing the upcoming 1.20.X release

Sure. I’ve clicked at 8:30. I’m providing log starting with last entry timestamped with 8:29. After clicking on “BLOCK CONTACT” the dialog disappeared as expected, but the “Contact request” remained. Then I closed the DC client (as seen in the logs below).

2021-06-07T08:29:58.130Z	main/state            	INFO		"Saving state to /home/user/.config/DeltaChat/config.json"
2021-06-07T08:29:58.245Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: INBOX: Idle entering wait-on-remote state"
2021-06-07T08:30:30.131Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:30.132Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:30.132Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:30.132Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/scheduler.rs:283: smtp fake idle - interrupted"
2021-06-07T08:30:30.132Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/job.rs:1295: loading job for Smtp-thread"
2021-06-07T08:30:30.132Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/scheduler.rs:281: smtp fake idle - started"
2021-06-07T08:30:30.191Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/job.rs:1295: loading job for Imap-thread"
2021-06-07T08:30:30.238Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"odeslan&AOE-\"."
2021-06-07T08:30:30.257Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"INBOX\"."
2021-06-07T08:30:30.258Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"DeltaChat\"."
2021-06-07T08:30:30.290Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: odeslan&AOE-: Idle entering wait-on-remote state"
2021-06-07T08:30:30.318Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: INBOX: Idle entering wait-on-remote state"
2021-06-07T08:30:30.318Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: DeltaChat: Idle entering wait-on-remote state"
2021-06-07T08:30:32.261Z	main/state            	INFO		"Saving state to /home/user/.config/DeltaChat/config.json"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:97: Idle wait was interrupted"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/scheduler.rs:283: smtp fake idle - interrupted"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/job.rs:1295: loading job for Smtp-thread"
2021-06-07T08:30:32.580Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/scheduler.rs:281: smtp fake idle - started"
2021-06-07T08:30:32.642Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/job.rs:1295: loading job for Imap-thread"
2021-06-07T08:30:32.682Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"odeslan&AOE-\"."
2021-06-07T08:30:32.705Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"INBOX\"."
2021-06-07T08:30:32.706Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap.rs:734: 0 mails read from \"DeltaChat\"."
2021-06-07T08:30:32.731Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: odeslan&AOE-: Idle entering wait-on-remote state"
2021-06-07T08:30:32.766Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: INBOX: Idle entering wait-on-remote state"
2021-06-07T08:30:32.766Z	core/event            	INFO		"DC_EVENT_INFO"	0	"src/imap/idle.rs:71: DeltaChat: Idle entering wait-on-remote state"
2021-06-07T08:30:34.573Z	main/state            	INFO		"Saving state to /home/user/.config/DeltaChat/config.json"
2021-06-07T08:30:39.985Z	main/state            	INFO		"Saving state to /home/user/.config/DeltaChat/config.json"
2021-06-07T08:30:40.130Z	main/index            	INFO		"Quitting now. Bye."

Nothing in the logs. Looks like the problem is that Contact::block is not resultified and ignores most of the errors:

Same here. I’m using Delta Chat on Android as well as on Linux (Ubuntu), both connected to a self-hosted Dovecot/Postfix setup. Worked like a charm with all previous versions up to (including) 1.15. With 1.20, I have the following regressions:

  • “IMAP operation attempted while it is torn down” on start of Delta Chat. Apart from this message, the application seems to operate normal.
  • Messages I write from my Linux desktop Delta Chat do not show up any more on my Android delta chat. This was the case with previous versions.

Additional information:

  • I use procmail to sort incoming emails having the “Chat-Version” header field into the “DeltaChat” IMAP folder
  • Sent messages are also copied to the “DeltaChat” IMAP folder by postfix and procmail
  • Because of this, DeltaChat only monitors the “DeltaChat” IMAP folder, not “Sent”, not “Inbox”. “Copy to self” is also turned off
  • As said above, this setup worked great up to (including) version 1.15

Thanks for any hint!
Sven

1 Like

I have just refactored IMAP to ensure it’s connected from the beginning: imap: refactor to always create Imap configured by link2xt · Pull Request #2459 · deltachat/deltachat-core-rust · GitHub If “IMAP operation attempted while it is torn down” appears after this change, it probably means a call to prepare() is missing somewhere.

2 Likes

Wow. I just upgraded my Android device to 1.20.5 and can confirm that the “IMAP operation attempted while it is torn down” message doesn’t appear any more.

Many thanks, @link2xt !

Regarding the mails sent from DC for Linux desktop not showing up on DC android, should I file an issue on github? I could also create a test user for my mail server and provide credentials so the problem should be reproducible.

Thanks!
Sven

1 Like

Regarding the mails sent from DC for Linux desktop not showing up on DC android, should I file an issue on github?

You probably just need to enable “Copy to self” on Desktop.

Thanks for the hint, @link2xt , but I configured my mailserver to save copies of outgoing mails and I configured procmail to move mails having the “Chat-Version” header into the “DeltaChat” IMAP folder.

This means that “Copy to self” is not needed because postfix + procmail do exactly what “Copy to self” would do: they make sure that my sent’ chat messages also show up in the “DeltaChat” IMAP folder.

Although the messages sent via Delta Chat correctly show up in the “DeltaChat” IMAP folder (I triple-checked this!), they do not show up on my other devices. This worked with Delta Chat up to (including) 1.15 and stopped with 1.20.

In other words, sent chat messages aren’t synchronized any more. Received messages still do.

A test account to reproduce this would be helpful indeed then. You can PM credentials on the forum here.

I have version DC 1.20.2 on a Android 10 phone.

I also suffer the messages “IMAP operation attempted while it is torn down” and I do not receive any messages and no verification for reading my messages with DC any more, while I still can successfully send messages. But I checked, there are incoming messages, I can see them with my email program.

On Google Playstore there is still version 1.20.2
I do not see version 1.20.5
Where can I update to 1.20.5 ?

You can follow the APK link on https://get.delta.chat
1.20.5 is at https://download.delta.chat/android/deltachat-gplay-release-1.20.5.apk
It is the same APK as distributed by Google Play, so downloading and installing it manually is no different than updating from the store.

New versions are not made available for all users at once via Google Play to reduce damage in case there is some critical bug. So far there were no updates that broke Delta Chat setups irreversibly, but many users never make backups so deployment of new versions is done carefully.

1 Like

I successfully installed the update and immediately received the missing messages.
Thank You @link2xt
best regards
Hans

1 Like

DC 1.20.5 , Android 10
@link2xt
What I observed now with the newly installed 1.20.5 is that the read-verification did not update towards the double-ticks, despite my email-prog registered that the verification did arrive. I waited for an hour, but no success. Same with incoming messages.

Stopping and restarting the app made DC to immediately display the double-tick and new messages.
For the Double ticks that solution was not permanent and worked only once after the fresh install. Afterwards they again were not updated at reading at the other side.

I was able to “solve” the problem in my case. As so often the problem existed between chair and keyboard (PEBCAK - Wiktionary): the filter I used to move chat-related emails to the DeltaChat IMAP folder also marked these emails as read which prevented DC to trigger notifications. Please apologize any confusion caused!