Alright, the building survived!
So, the solution, to get Zarafa to deliver email to a public folder is as such:
Installed SMEServer 7.3, updated to 7.4 using usual step.
Installed Zarafa for 'db' option as per the contribs instructions on this site.
Created three users in SMEServer server-manager page (one of which has username 'info').
Disabled webmail in Email panel (not required, but a step I took).
Created three users in Zarafa using Zarafa panel (it only appeared after the second reboot of server)...
In Outlook, using the Zarafa client, I created a public folder called Info and gave all three users full permissions to folder using one of the Zarafa users I had delegated as administrative fromt eh Zarafa panel in server-manager page).
At the console of the SMEServer, as root, created this file (with the great, professional help I had on this post):
[root@server30 ~]# cat /etc/e-smith/templates-user-custom/.qmail/80Zarafa
{
my $zarafa = $user->prop('zarafa') || 'disabled';
my $zarafa2 = ${'zarafa-server'}{GlobalForward} || 'disabled';
if ($zarafa eq 'enabled' || $zarafa2 eq 'enabled') {
if ( $USERNAME ne 'info' ) {
return "| /usr/bin/zarafa-dagent -q $USERNAME ; if [ $? -ne 0 ] ; then exit -1; else exit 99; fi;";
}
else
{
return "| /usr/bin/zarafa-dagent --public 'Public Folders\\Info' -C info ; if [ $? -ne 0 ] ; then exit -1; else exit 99; fi;";
}
}
}
Notice it ends with three }'s one on each line, copy and paste carefully.
signal-event email-update
Will alter the .qmail folders in each users home and make teh 'info' user different as such (comapring 'gund' and 'info'):
[root@server30 ~]# cat /home/e-smith/files/users/gund/.qmail
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at
http://www.contribs.org/development/#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
| condredirect gund-junkmail headermatch 'X-Spam-Status: Yes'
# Forward not set
| /usr/bin/zarafa-dagent -q gund ; if [ 0 -ne 0 ] ; then exit -1; else exit 99; fi;
./Maildir/
[root@server30 ~]# cat /home/e-smith/files/users/info/.qmail
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at
http://www.contribs.org/development/#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
| condredirect info-junkmail headermatch 'X-Spam-Status: Yes'
# Forward not set
| /usr/bin/zarafa-dagent --public 'Public Folders\Info' -C info ; if [ 0 -ne 0 ] ; then exit -1; else exit 99; fi;
./Maildir/
Note, if you don't use SME, and you use qmail in most other Linux distro's, this second file, from 'info' user is what your .qmail should look like, substitute folder names etc as required. Essentially, this tells qmail application to respond with this command if email is pushed out to 'info' user.
Now, when email is sent to info@yourdomains.com is automatically gets delivered to the Info public folder, so that any employee can see the email and react to the customer's query.
Note, I used 6.20-7 and there is a bug listed where you cannot reply to this email while it is in the public folder. This has been address in 6.20-8, which I have yet to try, refer to zarafa forums for more info.
I hope this helps anybody who want to use Zarafa with SME, so far, we are happy with the product, it has a high WAF (wife acceptance factor), too.
Cheers, thanks for the script help here, I can use this information elsewhere.
Gund