Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Message filter to copy msg to imap folder and then move msg to a local folder always works re: local folder but somtimes the msg is missing from imap folder.

  • 6 respostas
  • 2 have this problem
  • 7 views
  • Last reply by fjriskey

more options

I use one message filter to perform two actions on certain messages: 1) Copy message to an imap folder 2) Move message to a local folder.

Usually this works; the message is in the imap folder and the local folder, and is not in the Inbox. But about 10% of the time the message shows in my local folder but not the corresponding imap folder. I compare the contents of the local folder and the imap folder, and the local folder will have messages that the imap folder is missing. I can then copy the messages to the imap folder but I want to avoid manually checking.

Any ideas what could be occurring? (I just enabled the Filter Log to see if anything interesting shows there).

I use one message filter to perform two actions on certain messages: 1) Copy message to an imap folder 2) Move message to a local folder. Usually this works; the message is in the imap folder and the local folder, and is not in the Inbox. But about 10% of the time the message shows in my local folder but not the corresponding imap folder. I compare the contents of the local folder and the imap folder, and the local folder will have messages that the imap folder is missing. I can then copy the messages to the imap folder but I want to avoid manually checking. Any ideas what could be occurring? (I just enabled the Filter Log to see if anything interesting shows there).

Chosen solution

I swapped the operations to be 1) copy to local folder, 2) move to imap folder. I set Filter before classification. This works reliably so I will mark the issue solved.

Matt, thank you for your assistance!

Ler a resposta no contexto 👍 0

All Replies (6)

more options

Are you running the filter after classification. Doing so often fixed weird issues like these.

more options

No, I was running the default, "Filter before classification". I just changed them all to "Filter after classification". Thank you for the suggestion, I will give it a day or so and then respond with results.

more options

Well, that didn't take long to show results, but it is not good. When I start TB I see the number of new messages in both the imap folders and the local folders are the same. Within a couple of seconds though all the new emails are moved from the imap folders to the local folders so that I end up with 2 copies of each email in the local folder and none in the corresponding imap folder. This only started after I set all to "Filter after classification".

more options

I confirmed that "Run selected filter(s) on: Inbox" only, not the other imap folders.

I do have each filter set "Apple filter when: Manually Run" and "Getting New Mail".

My first action is to Copy Message to imap folder, the second action is Move Message to Local Folder. I could try to swap those actions as an experiment.

more options

once you move the message, it is gone from the folder, so the rest of that filter will fail if your then try and copy it.

Given the IMAP action involves a round trip to the mail server, I would try copy to IMAP and follow that with a move to the local folder. But how that works out will depend, I think, entirely on how quickly the round trip to the IMAP server occurs.for the copy. That also depends on the server implementation of IMAP. Some server software copies and deletes to move. Others simply Move from folder to folder.

It might actually work better as two filters. Same basic criteria. First one to copy and then one to move. Or copy twice and delete

more options

Chosen Solution

I swapped the operations to be 1) copy to local folder, 2) move to imap folder. I set Filter before classification. This works reliably so I will mark the issue solved.

Matt, thank you for your assistance!