DC_EVENT_INCOMING_MSG sometimes not followed by DC_EVENT_INCOMING_MSG_BUNCH

[lk108]

• Operating System: Linux (Debian trixie)
• Core Version: 2.49.0
• Client Version: DeltaTouch 2.49.0 dev version

Expected behavior

DC_EVENT_INCOMING_MSG events are always followed by DC_EVENT_INCOMING_MSG_BUNCH, just as for account 96 in the log below.

Actual behavior

When receiving an uncencrypted html email with two attachments, core fired three DC_EVENT_INCOMING_MSG events that were not immediately followed by a DC_EVENT_INCOMING_MSG_BUNCH event. About 20 and 30 seconds later, respectively, two DC_EVENT_INCOMING_MSG_BUNCH events appeared for the account in question.

Some minutes later, a very similar email was received, again causing three DC_EVENT_INCOMING_MSG events, but this time no DC_EVENT_INCOMING_MSG_BUNCH was received in the following minutes (the bunch event in the log below is for a different account).

See account 3 in the log below.

Logs

Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 3: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 3: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 96: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 238: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 94: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 94: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 5: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 5: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 119: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 238
Mai 10 18:40:30 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:40:30 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 96
Mai 10 18:40:31 Info: Emitter: DC_EVENT_NEW_BLOB_FILE, account 3: $BLOBDIR/xxxxxxx.ics
Mai 10 18:40:31 Info: Emitter: DC_EVENT_NEW_BLOB_FILE, account 3: $BLOBDIR/xxxxxxx.pdf
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 119
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 119
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONTACTS_CHANGED, account 3, contact ID: 316
Mai 10 18:40:31 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6464
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:31 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6465
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:31 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6466
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 210: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_CONNECTED, account 210: IMAP-LOGIN as xxxxxxxx
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 210
Mai 10 18:40:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:40:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94
Mai 10 18:40:36 Info: Emitter: DC_EVENT_MSGS_NOTICED, account 3, chat_id: 124
Mai 10 18:40:36 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:36 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:36 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:36 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:36 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:36 Info: Emitter: DC_EVENT_SMTP_CONNECTED, account 3: SMTP-LOGIN as xxxxxxxx
Mai 10 18:40:36 Info: Emitter: DC_EVENT_SMTP_MESSAGE_SENT, account 3: Message len=2262 was SMTP-sent to xxxxxxxx
Mai 10 18:40:36 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_MSGS_NOTICED, account 3, chat_id: 124
Mai 10 18:40:42 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_SMTP_MESSAGE_SENT, account 3: Message len=2254 was SMTP-sent to xxxxxxxx
Mai 10 18:40:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_IMAP_MESSAGE_MOVED, account 3: IMAP messages 45832 moved to DeltaChat
Mai 10 18:40:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:42 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_MSGS_NOTICED, account 3, chat_id: 124
Mai 10 18:40:43 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:40:43 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_SMTP_MESSAGE_SENT, account 3: Message len=2262 was SMTP-sent to xxxxxxxx
Mai 10 18:40:43 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_IMAP_MESSAGE_MOVED, account 3: IMAP messages 45833 moved to DeltaChat
Mai 10 18:40:43 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:43 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_INCOMING_MSG_BUNCH, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_IMAP_MESSAGE_MOVED, account 3: IMAP messages 45834 moved to DeltaChat
Mai 10 18:40:51 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:40:51 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_INCOMING_MSG_BUNCH, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:41:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:45:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:45:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:45:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:45:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:45:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94
Mai 10 18:46:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:46:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:46:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:46:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:46:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:46:41 Info: Emitter: DC_EVENT_NEW_BLOB_FILE, account 3: $BLOBDIR/xxxxxxx.ics
Mai 10 18:46:41 Info: Emitter: DC_EVENT_NEW_BLOB_FILE, account 3: $BLOBDIR/xxxxxxx.pdf
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CONTACTS_CHANGED, account 3, contact ID: 316
Mai 10 18:46:41 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6470
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:46:41 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6471
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:46:41 Info: Emitter: DC_EVENT_INCOMING_MSG, account 3, chat_id: 124, msg_id: 6472
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 3
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:46:41 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:46:41 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:50:19 Info: Emitter: DC_EVENT_CONTACTS_CHANGED, account 3, contact ID: 316
Mai 10 18:50:19 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 3, chat_id: 124
Mai 10 18:50:29 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:50:29 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:50:31 Info: Emitter: DC_EVENT_CONTACTS_CHANGED, account 96, contact ID: 138
Mai 10 18:50:31 Info: Emitter: DC_EVENT_CONTACTS_CHANGED, account 96, contact ID: 138
Mai 10 18:50:31 Info: Emitter: DC_EVENT_INCOMING_MSG, account 96, chat_id: 75, msg_id: 22307
Mai 10 18:50:31 Info: Emitter: DC_EVENT_CHATLIST_CHANGED, account 96
Mai 10 18:50:31 Info: Emitter: DC_EVENT_CHATLIST_ITEM_CHANGED, account 96, chat_id: 75
Mai 10 18:50:31 Info: Emitter: DC_EVENT_INCOMING_MSG_BUNCH, account 96
Mai 10 18:50:31 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 96
Mai 10 18:50:31 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 96
Mai 10 18:51:01 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:51:01 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:51:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:51:42 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 3
Mai 10 18:51:42 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 3
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:52:33 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 5
Mai 10 18:52:33 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 5
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:52:33 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:52:33 Info: Emitter: DC_EVENT_CONNECTIVITY_CHANGED, account 94
Mai 10 18:52:33 Info: Emitter: DC_EVENT_IMAP_INBOX_IDLE, account 94

[WofWca]

We also rely on this on Desktop to know when to flush notifications:

https://github.com/deltachat/deltachat-desktop/blob/8768f68f5befeab9f6a9fc7f28f35b08de241a2a/packages/frontend/src/system-integration/notifications.ts#L60-L62

But I wonder if it should be something to rely on? The docs for the event are sparse.

My analysis (I'm a noob in Core)

This is the place where DC_EVENT_INCOMING_MSG_BUNCH gets emitted:

core/src/imap.rs

Lines 782 to 784 in f2f2dd4

	if !received_msgs.is_empty() {
	context.emit_event(EventType::IncomingMsgBunch);
	}

And apparently this is the main place where the DC_EVENT_INCOMING_MSG events get emitted, for non-bots:

core/src/receive_imf.rs

Lines 1030 to 1032 in 855153c

	for msg_id in &received_msg.msg_ids {
	chat_id.emit_msg_event(context, *msg_id, important);
	}

This code apparently only gets called by fetch_many_msgs. fetch_many_msgs only has 2 places where it can get called.
In fetch_new_msg_batch the BUNCH event always follows the DC_EVENT_INCOMING_MSG events (or rather, as long as there is no early-return).
However, in fetch_single_msg fetch_many_msgs is not followed by the BUNCH event. fetch_single_msg itself is only called from download_msg, which can get called in these two places:

core/src/download.rs

Line 281 in a70924a

let res = download_msg(context, rfc724_mid.clone(), session).await;

core/src/download.rs

Lines 317 to 340 in a70924a

	/// Downloads known post-messages without pre-messages
	/// in order to guard against lost pre-messages.
	pub(crate) async fn download_known_post_messages_without_pre_message(
	context: &Context,
	session: &mut Session,
	) -> Result<()> {
	let rfc724_mids = context
	.sql
	.query_map_vec("SELECT rfc724_mid FROM available_post_msgs", (), |row| {
	let rfc724_mid: String = row.get(0)?;
	Ok(rfc724_mid)
	})
	.await?;
	for rfc724_mid in &rfc724_mids {
	if msg_is_downloaded_for(context, rfc724_mid).await? {
	delete_from_available_post_msgs(context, rfc724_mid).await?;
	continue;
	}
	// Download the Post-Message unconditionally,
	// because the Pre-Message got lost.
	// The message may be in the wrong order,
	// but at least we have it at all.
	let res = download_msg(context, rfc724_mid.clone(), session).await;

the latter kind of seems like what you're describing: plain emails, which, AFAIK, means that for them there is no post messages.

Solution?

I'm guessing that a solution would be to add emit_event(EventType::IncomingMsgBunch); to inside of fetch_single_msg, or maybe even move emit_event(EventType::IncomingMsgBunch) to inside of fetch_many_msgs

Misc

There is also another place here, maybe also buggy.

core/src/calls.rs

Line 366 in 2637c3b

self.emit_incoming_msg(call.msg.chat_id, call_id); // notify missed call

[iequidoo]

There is also another place here, maybe also buggy.
[...]

This is going to be replaced with CallMissed event in #7955 , probably we don't want to emit IncomingMsgBunch after it, we don't do that after other call events.

...

or maybe even move emit_msg_event() to inside of fetch_many_msgs

I'd vote for this if it doesn't break anything.

[WofWca]

or maybe even move emit_msg_event() to inside of fetch_many_msgs

I'd vote for this if it doesn't break anything.

Whoops, sorry I meant "move emit_event(EventType::IncomingMsgBunch) to inside of fetch_many_msgs".

[WofWca]

I dug a bit deeper. Back when IncomingMsgBunch was introduced in #3643, there were 2 calls to fetch_many_msgs inside of fetch_new_messages.

core/src/imap.rs

Lines 860 to 882 in ffd5777

	// Actually download messages.
	let (largest_uid_fully_fetched, mut received_msgs) = self
	.fetch_many_msgs(
	context,
	folder,
	uids_fetch_fully,
	&uid_message_ids,
	false,
	fetch_existing_msgs,
	)
	.await?;
	let (largest_uid_partially_fetched, received_msgs_2) = self
	.fetch_many_msgs(
	context,
	folder,
	uids_fetch_partially,
	&uid_message_ids,
	true,
	fetch_existing_msgs,
	)
	.await?;
	received_msgs.extend(received_msgs_2);

I suspect that that could have been the reason not to have emit_event(EventType::IncomingMsgBunch) inside of fetch_many_msgs.

[WofWca]

I opened #8259 which supposedly fixes the situation (although I didn't test this yet).

However, I'm concerned that the IncomingMsgBunch is not the only problem caused by this bug. This line also looks suspicious:

core/src/imap.rs

Line 786 in d069650

chat::mark_old_messages_as_noticed(context, received_msgs).await?;

We don't do it on the other occurrence of fetch_many_msgs, and I'm not sure if we should.

Edit: Also I think that in tests wherever we check for IncomingMsg we must also check for IncomingMsgBunch. With some utility function perhaps.

[iequidoo]

We don't do it on the other occurrence of fetch_many_msgs, and I'm not sure if we should.

The other one is in download_msg() which replaces a pre-message with the downloaded post-message, i.e. there's no new message, so there's no need to mark any incoming messages as noticed additionally. EDIT: download_msg() is also called from download_known_post_messages_without_pre_message(), so indeed we should call chat::mark_old_messages_as_noticed() from fetch_single_msg().

[WofWca]

OK, then it seems like #8259 would only solve a part of the actual problem.
I've unassigned myself, it's probably best if someone more qualified deals with this.