Hello Ronald,
On Tue, 04 May 2010, Ronald J. Yacketta wrote:
> The main reason for asking is that during our initial (today)
> testing events created with iCal or Sunbird are not showing up on
> attendees calendars but emails are showing up. It seems (to me) that
> we would need to use zarafa's email features in-order to send /
> accept meeting invitations? Using other calendar type applications
> (bedework) events created and submitted via ics/caldav show on both
> the creators and attendees calendar for which they can be accepted,
> declined or what have you.
some people might slap me for the comparison, but the Zarafa Webaccess is
something like Thunderbird with Lightning. But instead of using IMAP and
CalDav it's MAPI-based. And instead of a client application, it's
webbased.
If you create an appointment using Lightning or Sunbird, they will create
an e-mail which gets send to the invited person(s). If the person(s)
accept
the invitation, the appointment data will be written into their calendars.
This has not been the case for us, we have created numerous events via
external clients and those being invited never see the meeting or get an
invitation.
For example, I created an event, invited Joe and Fred for which neither
received a meeting request or seen the meeting in there calendar.
It behaves equivalent at Zarafa Webaccess: And thus without Zarafa
Spooler,
no e-mail appointment invitation will be sent and without Zarafa DAgent,
no
appointment invitation will show up in the inbox which could get accepted
by somebody. So yes, you need the e-mail features if you would like to use
the Zarafa Webaccess as calendaring software. Or you need a worse hack to
only get appointment e-mails pushed into Zarafa (e.g. by using .procmailrc
rules to detect appointment invitations or using a special e-mail
address).
We are not keen on using the webaccess portion, it is nice but faculty /
staff have grown accustom to using ics / caldav aware clients (iCal,
SunBird etc..)
An alternative could be to just use the iCal/CalDav server component
Zarafa
provides and skip the Zarafa Webaccess completely. But then you need a
client software handling iCal/CalDav and sending/receiving e-mails. And it
is not webbased, Zarafa would just provide an iCal/CalDav server. I'm not
absolutely sure whether it really makes sense to use Zarafa for only iCal/
CalDav, because there are other iCal/CalDav server implementations around.
As mentioned earlier this is exactly (Zarafa would just provide an
iCal/CalDav server) what we are looking for, but have been unable to get
working.
Regards,
Ron
If I explained something wrong above, somebody might correct me,
please.
Greetings,
Robert
_______________________________________________
zarafa mailing list
zarafa(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/zarafa