Forum

The only thing that I am aware of that might cause this issue is if you tried to move or delete a message that you were trying to save the attachment for. If this is not your issue, then I would appreciate details of what you are trying to do that fails, so that I can investigate. I would need to know things like type of account and folder, filter search term, and all filter actions.

I don't fully understand your post I'm afraid. But let me describe the problem more fully, and why it is difficult to solve, and offer a workaround.

The detach operation actually must rewrite the message in its message store. That is an async operation – as is a move. There is no way in the base filter code currently to coordinate the operation of two async actions on a single message in a single folder.

However, I was able to devise a method to get around this using the existing FiltaQuilla. It is a little tricky, but feel free to try it. It will only work with messages moved to an IMAP store.

1) With FiltaQuilla installed, enable processing of message filters in the destination folder using (select folder)/(right click)/Properties/(enable "Apply incoming Filters")

2) On the IMAP account, create a first filter which is a move. In addition to whatever your usual move criteria is, add an additional search criteria which uses a javascript search term, and rejects the filter if the folder matches the destination. So if for example the folder name is "xxx1" add a javascript search term (matches):

  message.folder.name != 'xxx1'

3) Add an additional filter, located after the MOVE filter, that does the message detach

On my tests, this combination was able to successfully do a detach after a move. Obviously I need to develop an easier way to do this and get core and/or FiltaQuilla patches to do this.

You can email me at rkent@mesquilla.com