Hi Tshimanga, On 17/11/2023 16:12, TSHIMANGA Minkoka wrote:
Dear All,[...]The problem is that the above sieve rule seems not enough to catch email where supp...@example.com is not the "To" fields, as with cases of "Cc:" or "Bcc:".
It does not matter because your final recipient is tshimangaxxx@. Postfix wise, it's always sent *to* someone even if you use Bcc,Cc.
Can you see the sieve actions in the logs for incoming emails?
In the log of postfix, I can see lines with "... postfix/lmtp ... orig_to=<supp...@example.com> ...". The problem I am facing is that "orig_to" is not part of the headers postfix/lmtp (in reality dovecot/lmtp process) can see in order to apply on it a sieve rule.
It does not matter. As long as postfix set "to=<tshimanga.mink...@example.com>" along orig_to=<supportxxx@xxx> ; it is not a problem.
You said earlier you can see the emails in your mailbox.
Any suggestions on how I can also sieve filter those emails ?
Can you show your config? (doveconf -n)? Have you enable sieve on dovecot? If sieve is enabled, you will see in your logs , lines with 'sieve' -- Willy Manga @ongolaboy https://ongola.blogspot.com/
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
