• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

postfix sender_bcc

maclenin

New Pleskian
Hello!

Given the following configuration within plesk 12.0.18 (centos7):

/etc/postfix/sender_bcc
# contents
[email protected] [email protected]
[email protected] [email protected]
[email protected] [email protected]

/etc/postfix/main.cf
# at the end of the file
sender_bcc_maps = hash:/etc/postfix/sender_bcc

# run after set-up
postmap /etc/postfix/sender_bcc
postfix reload

# confirm creation of
/etc/postfix/sender_bcc.db

Questions:

1. Will emails sent from [email protected] to [email protected] be blind copied to [email protected]?

2. Or will only emails sent from [email protected] to [email protected] be blind copied to [email protected]?

3. I have forwarding set up in plesk using the same logic. Will forwarding in plesk conflict with the sender_bcc configuration? Should I set up both sender_bcc and recipient_bcc in postfix and switch off forwarding in plesk?

3.a. Do the same rules apply to incoming / recipient_bcc and sender_bcc (as in 1. and 2.)?

4. What happens to this configuration when plesk updates?

5. If plesk updates break it, is there a way to make this configuration "permanent"?

Thanks for any guidance!
 
Last edited:
It works. I will edit the OP (in the body of this post) to clarify:

Plesk version 12.5.30 / CentOS 7

All actions performed as root:

1. nano /etc/postfix/main.cf
# sender_bcc
sender_bcc_maps = hash:/etc/postfix/sender_bcc

2. nano /etc/postfix/sender_bcc
[email protected] [email protected]

3. postmap /etc/postfix/sender_bcc

4. Restart postfix as root <---- or reload (need to clarify - both seem to work)
postfix restart

The only unanswered question (thus far) involves what happens to the sender_bcc configuration in the face of plesk updates or upgrades....

I have kept (recipient) forwarding within plesk "ticked" (and functional).

More, anon!
 
Last edited:
Back
Top