Posted by Archiving is one of important thing on email. Archiving of email, usually used for audit complain or other needed. Actually, feature archiving is there on Zimbra paid version (Network Edition) and only there for Professional edition. If you often use webmail, you can archive inbox item, sent item even draft item as described at Zimbra wiki link : http://wiki.zimbra.com/wiki/Legal_Intercept. However, just work if using webmail. If using email client such as Thunderbird or Outlook, your email will not archive.
If you want to archive email and using Zimbra OSE, you can use auto bcc with simple modification on Postfix. But in this section, i will just archive email by sender (auto bcc by sender). For example, i have account with name user1@imanudin.net and archive account with name user1@imanudin.archive. Every email sent from user1@imanudin.net will automatically bcc to user1@imanudin.archive. You can do the following tips to do that
# Create domain archive on Zimbra. Example imanudin.archive. To do that, you can do via Zimbra Admin | Configure | Domains or via Command Line with the following command
su - zimbra zmprov cd imanudin.archive
# Create account for archive. Example account user1@imanudin.net have account archive user1@imanudin.archive. To do that, you can do via Zimbra Admin | Manage or via Command Line with the following command
su - zimbra zmprov ca user1@imanudin.archive passwordarchiveuser1
# Create rule on Zimbra for archive every sent email from user that will be archived
vi /opt/zimbra/postfix/conf/main.cf
Add the following line on the bottom
sender_bcc_maps = lmdb:/opt/zimbra/postfix/conf/sender_bcc
# Create file /opt/zimbra/postfix/conf/sender_bcc and fill with the users who will be archived
vi /opt/zimbra/postfix/conf/sender_bcc
Fill with the following example
user1@imanudin.net user1@imanudin.archive
# Postmap file /opt/zimbra/postfix/conf/sender_bcc
postmap /opt/zimbra/postfix/conf/sender_bcc
# Reload service Postfix Zimbra
postfix reload
Please try to sending email from user who have been configured auto bcc. Every sent email from user1@imanudin.net will be also copied to user1@imanudin.archive
Note :
– This guidance using Zimbra 8.5. If using old Zimbra and above guidance is not working, please change lmdb become hash
– Every add/change/delete users archives on /opt/zimbra/postfix/conf/sender_bcc, don’t forget to doing postmap and reload Postfix Zimbra
If you have budget and want to simple archives users, consider to using Zimbra NE with more features available
Good luck and hopefully useful 😀
Hi Dear,
i need alway_bcc seting in zimbra 8.7 , i can recive all user incoming & outgoing mail into one archive accounts
Hello,
You can add on the file /opt/zimbra/postfix/conf/main.cf and adding always_bcc
Foud Not Working –>Always_bcc afterZCS_OSE 8.7.1
Hi
After configuring mail archive and while updating postmap getting below error
postmap: fatal: open database /opt/zimbra/postfix/conf/sender_bcc.lmdb: Permission denied
pls can you give me solution…
you are getting this error because postmap is not having permissions wo create db file in conf directory.
You can try:
chown postfix:postfix /opt/zimbra/postfix/conf/
chmod 775 /opt/zimbra/postfix/conf/
Now run postmap. It should work. I have tested it. Post the issue here if you face.
Hi
I set the bcc with steps given in this article – https://docs.mithi.com/home/how-to-configure-zimbra-open-source-to-journal-mail-in-vaultastic
But after doing so all my incoming & outgoing emails started bouncing. The error I could see in logs is “unsupported dictionary type : hash”
Can you please help me to set the bcc properly. I have zimbra ose 8.6
Hi,
You can change “hash” with “lmdb”
Hi i am getting bellow error.
Dec 25 14:33:27 mail postfix/cleanup[170532]: warning: database /opt/zimbra/postfix/conf/sender_bcc.lmdb is older than source file /opt/zimbra/postfix/conf/sender_bcc
Dec 25 14:33:27 mail postfix/cleanup[170532]: warning: database /opt/zimbra/postfix/conf/recipient_bcc.lmdb is older than source file /opt/zimbra/postfix/conf/recipient_bcc
Hi Raj,
You can perform postmap again
Hello Friend,
How this can be accomplished on Zimbra 8.8.11 as there is no post fix installed.
I had updated main.cf file as instructed above from the following location.
/opt/zimbra/common/conf/main.cf
And then created the file sender_bcc in /opt/zimbra/common/conf/
Then when I “post map ” the following error pops up.
postmap /opt/zimbra/common/conf/sender_bcc
The program ‘postmap’ is currently not installed. You can install it by typing:
apt install postfix
So that means the new version dont have postfix,right?
Then how I can accomplish the same as in the post.
Please help.
Regards,
Liju
Hello,
Please login as Zimbra user (su – zimbra) and then run postmap
Hi Iman,
Thank you for your nice post. My requirement is that I want to apply forwarding in 2-3 layers like we do in postfix with procmail. For example, user1@example.com and user2@example.com outgoing emails shall be forwarded to user3@example.com. user3@example.com outgoing emails shall be forwarded to user4@example.com.
How should I do it in Zimbra?
Hello,
You can use this guidance to do that. Or you can create filter at user1, user2 and user3 on outgoing rule
Dear Imanudin,
Do you have any kind of automated script in which if a new user is created in Zimbra, the script will create a Archive user and created the entries in sender_bcc and receipinet_bcc.
Hi Sandeep,
No, i do not have that script
I have a working archive and AutoBCC is working fine. But Now I need to add another email.
The email should be sent to two different email addresses, how can I accomplish this?
Hi Kashif Alvi,
You can use Distribution list to accomplish it
We tried steps mentioned in this article “https://docs.mithi.com/home/how-to-configure-zimbra-open-source-to-journal-mail-in-vaultastic”
But after doing that all our incoming & outgoing emails started bouncing. It was like a double bounce error & the error message that we see in the logs was ” postfix: unsupported dictionary type: hash”
We have zimbra OSE 8.6, can you let us know what could be the reason for this error?