Thanks for the response, and sorry for my delayed reaction. I understand that always_bcc should send a copy to the address indicated or the alias of the address indicated. My situation is slightly different. It’s the initial recipient (the To:) that is aliased AND uses a transport to execute an external app. The app is expecting the alias, and that all works fine. The app is happy. My problem is that I also want to bcc that incoming email to an aliased address. That doesn’t seem to happen.
By-the-by, my app also generates a new email to be sent to an employee (without any aliases) and that always_bcc works fine. Let me try another example. Email is addressed to i...@mycompany.com <mailto:j...@mycompany.com>. All email addressed to i...@mycompany.com <mailto:j...@mycompany.com> is aliased to j...@mycompany.com <mailto:j...@mycompany.com>. There is also a transport set up to send email addressed to j...@mycompany.com <mailto:j...@mycompany.com> via pipe in master.cf to my application. I would also like a copy of the email to i...@mycompany.com <mailto:i...@mycompany.com> to go to an archive mailbox. Always_bcc is not functioning on the incoming email to i...@mycompany.com <mailto:i...@mycompany.com>. Is there any way to log always_bcc actions? I know adding it to the header defeats the purpose of the bcc. Does that also apply to the server’s log? > On Mar 15, 2020, at 3:10 PM, Wietse Venema <wie...@porcupine.org> wrote: > > always_bcc is implemented upon receving email, so that > > always_bcc = arch...@example.com > > will send a copy to arch...@example.com, unless you have aliased > that to something else. In that case, your BCC copy will be sent > there. > > For example if you have a wild-card alias > > @example.com blah > > Then your BCC copy will be sent to blah, unless you also add an 1:1 > alias to prevent that: > > # Everything aliased to blah > @example.com blah > # Except for arch...@example.com > arch...@example.com arch...@example.com > > Wietse
