How to remove auto_bcc in Postfix (Zimbra)

postfixzimbra

Hi I added a auto_bcc in my postfix config, and now I don't know how to remove it.

This is what I did:

Per user bcc for Zimbra

in /opt/zimbra/postfix/conf, create a file called sender_bcc and added the user you wanted to copy/send to:

employee@domain.com boss@domain.com

in /opt/zimbra/postfix/conf/main.conf, add:

sender_bcc_maps = hash:/opt/zimbra/postfix/conf/sender_bcc

then run as zimbra user

postmap /opt/zimbra/postfix/conf/sender_bcc

And restart all the stuff:

postfix reload
postfix stop
postfix start

How do I remove that? it seems like it created a database entry or something like that.

Best Answer

If you just want to disable the functionality, remove or comment out the line you added to main.cf.

The postmap command you ran generated a .db file, which lets Postfix do more efficient lookups than if it were to parse the text file every time. Both the sender_bcc and sender_bcc.db files are safe to remove after you remove the sender_bcc_maps line from main.cf and reload or restart Postfix.

Related Solutions

Zimbra – How to Change Postfix Parameters

I found the solution to my own problem. By looking at the file /opt/zimbra/conf/zmmta.cf, I saw the following lines:

if VAR zimbraMtaMyNetworks
    POSTCONF mynetworks VAR zimbraMtaMyNetworks
fi

With zmprov I can check the current settings and change them:

zmprov getServer servername.mydomain | grep zimbraMtaMyNetworks
zmprov modifyServer servername.mydomain zimbraMtaMyNetworks "127.0.0.0/8 [...]"
postfix reload

And the problem is solved. Xeon suggested an alternative and simpler way:

You can also change this in the Admin Console under Server Settings -> MTA -> MTA Trusted Networks

External postfix forwarding to zimbra server

You can setup a transport lookup table to override the nexthop on mail delivery.

In /etc/postfix/main.cf

transport_maps =
       hash:/etc/postfix/mytransport_override

In /etc/postfix/mytransport_override you write

migrated_address1@yourdomain smtp:zimbra.yourserver
migrated_address2@yourdomain smtp:zimbra.yourserver
another__migrated@yourdomain smtp:[zimbra.yourserver]

Then postmap hash:/etc/postfix/mytransport_override

I see no issues with spam or being your mail messages treated as spam (as long as your dns entries like PTR records, A records, MX records are okay).

EDIT

Good point in the comments: if you want to avoid MX records lookup add brackets around the hostname. Example is in the last line. Generally it is a good practice to use brackets to avoid surprises.

Best Answer

Related Solutions

Zimbra – How to Change Postfix Parameters

External postfix forwarding to zimbra server

Related Topic