You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using IMAP and I have two Email accounts, Acc1 & Acc2, where each account has an Inbox. I have forwarded messages from Acc1 to Acc2 and I therefore have duplicate messages in the Inbox of Acc2. I would like to remove the duplicates in the Inbox of Acc2.
I have tried the following (using TB v102.x)
Look for duplicates in the Inbox folders of Acc1 & Acc2. Duplicates are found, but they do not show which account they belong to (they both show as found in "Inbox"). Even if the Accounts would be shown, there does not appear to be a way to remove the duplicate from a specific Account?
To get around the issue of the same Inbox name for the two accounts, I created Saved Searches in Local Folders for the the two Inboxes (with different names). However, I then get an error "Not searching special Folders". I thought that the Add-on could search Local Folders?
The text was updated successfully, but these errors were encountered:
I am using IMAP and I have two Email accounts, Acc1 & Acc2, where each account has an Inbox. I have forwarded messages from Acc1 to Acc2 and I therefore have duplicate messages in the Inbox of Acc2. I would like to remove the duplicates in the Inbox of Acc2.
I have tried the following (using TB v102.x)
Look for duplicates in the Inbox folders of Acc1 & Acc2. Duplicates are found, but they do not show which account they belong to (they both show as found in "Inbox"). Even if the Accounts would be shown, there does not appear to be a way to remove the duplicate from a specific Account?
To get around the issue of the same Inbox name for the two accounts, I created Saved Searches in Local Folders for the the two Inboxes (with different names). However, I then get an error "Not searching special Folders". I thought that the Add-on could search Local Folders?
The text was updated successfully, but these errors were encountered: