exmdb: adjust event notifications in the face of soft-deletion actions

Creating a message in a folder not only updates a content table
showing the normal set, but also a CT showing the softdeleted set.
That ought not to happen.

References: GXL-337

Author: jengelh

exch/exmdb/db_engine.cpp

@@ -1679,6 +1679,14 @@ static void dbeng_notify_cttbl_add_row(db_conn *pdb,
 	if (!cu_get_property(MAPI_MESSAGE, message_id, CP_ACP,
 	    pdb->psqlite, PR_ASSOCIATED, &pvalue0))
 		return;	
+	char qstr[256];
+	snprintf(qstr, std::size(qstr), "SELECT is_deleted FROM messages WHERE message_id=%llu", LLU{message_id});
+	auto stm = pdb->prep(qstr);
+	if (stm == nullptr)
+		return;
+	auto b_del = stm.step() != SQLITE_ROW || stm.col_uint64(0) != 0;
+	stm.finalize();
+
 	std::unique_ptr<prepared_statements> optim;
 	BOOL b_fai = pvb_enabled(pvalue0) ? TRUE : false;
 	auto sql_transact_eph = gx_sql_begin(pdb->m_sqlite_eph, txn_mode::write);
@@ -1693,6 +1701,8 @@ static void dbeng_notify_cttbl_add_row(db_conn *pdb,
 			continue;
 		if (!!(ptable->table_flags & TABLE_FLAG_ASSOCIATED) == !b_fai)
 			continue;
+		if (!!(ptable->table_flags & TABLE_FLAG_SOFTDELETES) == !b_del)
+			continue;
 		if (dbase.tables.b_batch && ptable->b_hint)
 			continue;
 		if (ptable->prestriction != nullptr &&

exch/exmdb/message.cpp

@@ -630,6 +630,9 @@ BOOL exmdb_server::delete_messages(const char *dir, cpid_t cpid,
 			const TPROPVAL_ARRAY npropds = {std::size(nprop), nprop};
 			cu_set_properties(MAPI_MESSAGE, tmp_val, CP_ACP, pdb->psqlite,
 				&npropds, &problems);
+
+			/* For GCT(SHOW_SOFTDELETES), this is a new message now */
+			pdb->notify_message_creation(src_val, tmp_val, *dbase, notifq);
 		}
 		if (!b_hard && !is_private()) {
 			char sql_string[256];