[SOLVED] Parent - Child Accounts?

[jeaguilar]

I was under the impression that Zimbra 5 included support for parent-child accounts where e-mail would arrive in an Inbox for a parent to review and approve before being moved to a folder that a child could review. Am I misunderstanding how that functionality is implemented? I wasn't really able to get that to work. Any suggestions? Thanks.

[dkarp]

"Parent mailbox" refers to the ability for the parent to view and manage the child's mailbox, but does not include the ability to prescreen mail.

[mmorse]

Welcome to the forums,

It was originally a comcast thing that might slowly have spillover effects - and actually the UI is reused in Zimbra Desktop for multiple accounts.

But there is Bug 17538 - Parental Controls extension to family mailboxes (#12212)

Primary (parents) can set policy on secondary (child) mailboxes such that secondary only receives communications (email, IM, invites, etc.) from entries in the child's address book (whitelist).

Communications from anyone not in the child's address book would (optionally) be surfaced in the primary "inbox" for the parent to approve (and add to the child's address book) or deny (no such add, communication discarded).

In this mode, child cannot add user's to their own address book without parental approval.

You can also search family mailboxes in bugzilla and in PMWeb (zimbraPrefChildVisibleAccount & zimbraChildAccount) if you'd like to see what's been done so far.

Other things you could do:
There's the new shared folders.
sender_bcc_maps/recipient_bcc_maps
Or a hidden forward to your account so you can just get the incoming mail & setup a filter to sort it. (If your account is down it will bounce though).
Another way to catch all the incoming & outgoing on NE there's forking in ZAD or if on FOSS there's a nifty always_bcc method.
Or the even newer Legal Intercept - Zimbra :: Wiki

----

To get started:
zmprov ga child1@domain.com | grep zimbraId
zimbraId: {zimbraId-String-Of-Child-1}

zmprov ma parent@domain.com +zimbraChildAccount {zimbraId-String-Of-Child-1}

Visible secondary accounts are those shown in the accordion UI of the primary:
zmprov ma parent@domain.com +zimbraPrefChildVisibleAccount {zimbraId-String-Of-Child-1}
The primary user can also set this later from their AJAX client preferences:
(secondaryIsVisible.png)


Just like how the Zimbra Desktop's accordion UI works, you now have access to mail, contacts, calendar, tasks, & even preferencesof the secondary account.
(multiAccountAccordionView.png)


A few notes:
-Access to IM, Documents, and Briefcase are currently disabled when browsing the secondary account from the primary.
-This is a little different than sharing and requires the AJAX interface for functionality; you may need to still use normal shares for access in other clients.

To remove replace the plus sign with a minus:
zmprov ma parent@domain.com -zimbraChildAccount {zimbraId-String-Of-Child-1}

Update: 5.0.7 fixed briefcase Bug 28149 - offline : Briefcase application tab remains disabled for multi account but not documents: Bug 28411 - family mailboxes : documents & briefcase disabled

[Russianspi]

OK, I posted this to the blog entry too, but this is probably the best place for this. Mike, this looks great, but I can'tget it to work. I get no errors from the CLI, but nothing seems to happen in my AJAX interface. What server version do I need? (I'm running 5.0.9 NE). Is there a server side setting that I missed?

[mmorse]

Remember to make it visible?

(Just tested on 5.0.9_GA_2533.RHEL5_20080815101705 CentOS5 NETWORK edition)

It was implemented far back in 5.0 betas: Bug 12212 - Family Mailboxes
For briefcase you need 5.0.7+: Bug 28149 - offline : Briefcase application tab remains disabled for multi account
Docs you need 5.0.9+: Bug 28411 - family mailboxes : documents & briefcase disabled

[simon.goodwin]

I have a couple of important duos and several task based addresses which this looks like being perfect for but in the blog you said "Don’t go overboard on visible secondary accounts". Why?, What's affected?