In the new age when we can use OpenClaw to help manage our emails, I have a question about how EMClient would respond in the case of the “deduplication bug”.
As is well documented, if you ask eM Client to de-duplicate an email folder, it removes duplicate emails, leaving one behind, but then marks that email as deleted on the IMAP server. This means that the email will now no longer be visible to any other email client or service, such as Pipedrive, that accesses that same email account. This is a major frustration for me because I can no longer use the deduplication tool this means I literally have thousands of emails sitting in my inbox that are completely unnecessary and duplicated. Anyway, this is well known and you can find other posts about it here.
So OpenClaw now has access to my inbox and is able to read emails and move emails, deduplicate, draft replies, look for context etc. It’s a very very powerful tool. I’m surprised that not everyone is using it. I can give it instructions to find emails, to sort emails, and do so many different things. It works really, really well. eM Client does not have an API, so this is the best way to do it. It literally saves me hours every day.
Before somebody posts about the risks of letting OpenClaw loose on your emails, I am, of course, sandboxing this in a very specific account environment and limited selection of folders.
It can also scan a folder looking for duplicates. And it can then be instructed to keep only one copy if it finds multiple identical emails. It can make that decision using an personal AI instruction in case the addresses on the emails are different. My question is if anybody has tried this because I’m terrified of letting it loose with this capability automatically. Is this a way to bypass the deduplication bug in EM Client?
I guess I’m asking to chat with someone who is using OpenClaw with the end client.
if you ask eM Client to de-duplicate an email folder, it removes duplicate emails, leaving one behind, but then marks that email as deleted on the IMAP server. This means that the email will now no longer be visible to any other email client or service, such as Pipedrive, that accesses that same email account.
I don’t know that eM Client devs could do it any other way “other than to mark them deleted on the server” after running the de-duplicate tool unless you possibly had a POP account setup and ran the de-duplicator tool locally on the messages on each device installed with eM Client.
Does de-duplicating do it any differently using any other mail client with an IMAP account setup ?
I think maybe you misunderstood me. When the deduplicator runs, it removes duplicates and leaves only one email. But that email is now marked as deleted. This means that other devices attempting to access the eMap account will not see it. It should be marked as a perfectly normal regular email.
This, to me, is a bug.
When the deduplicator runs, it should then go back and ensure that there is one clean, normal copy remaining.
Yes I understand what you are saying and “I don’t believe it’s a problem with eM Client”. Other free forum users or moderators might comment.
It appears too you already have a large thread below on this issue with feedback from Pipedrive support and your own reasoning on why you believe it’s an eM Client issue.
Have you contacted offical eM Client support via lodging a ticket via the VIP support page to get their response on your problem ?