Filter sequence copy message to another inbox and then move original to another folder is not reliable (IMAP)

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
3 years ago
8 months ago

People

(Reporter: info, Unassigned)

Tracking

38 Branch
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [dupme])

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 2015091700

Steps to reproduce:

I have two IMAP accounts, say #1 and #2. Messages arrive in account #1. Filters are set for the inbox folder of account #1 to first copy the message to the inbox folder of account #2 and then move the original from the inbox folder of account #1 into a another subfolder of account #1. 


Actual results:

All messages are moved into the subfolder of account #1. About one third of the messages are not copied into the account #2 inbox folder before as they should. 


Expected results:

I expect to have two identical copies of all messages in the IMAP inbox folder of account #2 and the subfolder of account #1.
(Reporter)

Updated

3 years ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
(Reporter)

Updated

3 years ago
Summary: Filter sequence copy message to another inbox and then move original to another folder is not reliable (IAMP) → Filter sequence copy message to another inbox and then move original to another folder is not reliable (IMAP)
(Reporter)

Comment 1

3 years ago
Filter settings for the inbox folder of account #1 in detail:

Just one filter, in my case named "copy_move". "Manually Run" and "Getting new mail" are ticked. "Filter before Junk-Classification" is selected. "Archiving" and "After sending" are not ticked. "Match all messages" is selected. Two actions are specified in the following sequence: "Copy message into [Inbox folder of account #2]" and "Move messae into [subfolder of account #1]".

Updated

8 months ago
Component: Untriaged → Filters
Whiteboard: [dupme]
You need to log in before you can comment on or make changes to this bug.