Server side rule to BCC all mail from sender

Come on... Linc... Mr Humphries... one of you knows the answer to this question just off the top of your head... one line command, I bet...

Bowl me over with your mail wisdom...

Thank you Mr Hoffman, and forgive me for referring to you as Mr Humphries earlier. It was Friday and I was in a fit of stupor regarding how simple my need seemed to be and how complex all of the answers I was mining became.

So are you confident this CAN be done?

Again and again, it seems someone points to this notion that almost all server side mail rules are created for INCOMING mail, not outgoing mail.

I'm not averse to experimenting with some of the BCC mapping commands, but I am a little nervous about what degree of probability that I'll destroy our mail server I'm dancing around.

If you think it can be done, perhaps I'll conduct some trial and error attempts today.

Any additional insight/guidance you can offer will be most appreciated!

So I look at this:

sender_bcc_maps (default: empty)

Optional BCC (blind carbon-copy) address lookup tables, indexed by sender address. The BCC address (multiple results are not supported) is added when mail enters from outside of Postfix.

Specify zero or more "type:name" lookup tables, separated by whitespace or comma. Tables will be searched in the specified order until a match is found.

The table search order is as follows:

• Look up the "user+extension@domain.tld" address including the optional address extension.
• Look up the "user@domain.tld" address without the optional address extension.
• Look up the "user+extension" address local part when the sender domain equals $myorigin, $mydestination, $inet_interfaces or $proxy_interfaces.
• Look up the "user" address local part when the sender domain equals $myorigin, $mydestination, $inet_interfaces or $proxy_interfaces.
• Look up the "@domain.tld" part.

Note: with Postfix 2.3 and later the BCC address is added as if it was specified with NOTIFY=NONE. The sender will not be notified when the BCC address is undeliverable, as long as all down-stream software implements RFC 3461.

Note: with Postfix 2.2 and earlier the sender will be notified when the BCC address is undeliverable.

Note: automatic BCC recipients are produced only for new mail. To avoid mailer loops, automatic BCC recipients are not generated after Postfix forwards mail internally, or after Postfix generates mail itself.

Example:

sender_bcc_maps = hash:/etc/postfix/sender_bcc

After a change, run "postmap /etc/postfix/sender_bcc".

This feature is available in Postfix 2.1 and later.

And the syntax doesn't look intelligible to me at all. Being it simply doesn't seem like there is a beginners guide to Postfix, I'm going to go ahead and ask the stupid questions:

First off, are these instructions for editing the main.cf or the master.cf files? Or is this done through Terminal commands?

Second, if I am editing one of the main config files for Postfix, I don't understand how I specify sender and and bcc accounts?

sender_bcc_maps = joshua@example.com:/etc/postfix/vic@example.com

If I were trying to coax Postfix into triggering a BCC to vic@example.com each time joshua@example.com composed and sent an email, is that how the command should look?

Should I be using UUID's rather than email addresses? I feel like the examples don't include placeholders for the sender and the BCC recipient

Forgive my first foray into postfix

Really, really easy instructions to follow - thank you so much for spoon feeding me the answer

Honestly, after looking at it now, it is way simpler than I was making it.

But without your instructions, there is no way I would have organized the commands the way I needed to in order to work effectively the first time!

If you're ever in Cincinnati, I'll buy you a beer!