User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36

Steps to reproduce:

I have set up a filter which autoreplies with a template and then moves the original message to a specific folder.

Actual results:

When the original message is sent to me in cc and it meets the filter criterion, the autoreply doesn't work (though the original message is indeed moved to the specified folder).

Expected results:

The autoreply should have been done

Hmm, the summary doesn't match the description. In the summary you talk about receiving a message as part of a BCC group (undisclosed recipients) and in the description you talk about a CC. So which one is it? The former doesn't work by design, and I can explain that more, the latter one works.

Hi,
I'm sorry for creating confusion
It is as I explained in the title: the problem occurs when the message is sent to me in bcc.

So comment 0 should read Bcc.

Thomas, can you reproduce?

(In reply to Jorg K (CEST = GMT+2) from comment #1)

Hmm, the summary doesn't match the description. In the summary you talk about receiving a message as part of a BCC group (undisclosed recipients) and in the description you talk about a CC. So which one is it? The former doesn't work by design, and I can explain that more, the latter one works.

Let's trust the expert: Jörg is right, auto-reply must not work by design if the message replied-to was received via BCC, to prevent exposing yourself as having received the message (which is not supposed to be known, hence BCC). Whilst this may not be harmful when you'd just auto-reply to sender, I'd guess that we also respect reply-to headers for auto-reply, and already the risk of exposure is there, because you are not in control of reply-to which was set by sender. Worse when you have set up your own auto-reply template with extra recipients, again the secret fact would leak to all of those. Probably there are other scenarios which I haven't even considered, maybe bounce. So I think it's way too easy to shoot yourself in the foot with that, so that's why it won't work by design. It follows that this isn't a bug. I wonder if we have any documentation for this...?