[OGo-Outlook] zidestore recurring appt

Peter Duda outlook@opengroupware.org
Tue, 29 Jan 2008 12:22:54 -0800


This is a multi-part message in MIME format.

------=_NextPart_000_006C_01C86271.ACB5C800
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Recently reading a number of posts on the users list concerning an old bug
made me wonder about another old bug - that being recurring appointments.
Does anyone know the status of what seems to be the pandora's box that is
recurring appointments via zidestore (specifically
zidelook/zidestore/outlook)?  Is zidestore what it is and it is up to the
clients to conform to zidestore?  Do I need to ask this question of the
zidelook people or the sogo groupdav connector for mozilla? I have read
enough posts to understand the differences between zidestore and various
clients, but not many posts about what is being done about it.  

We are a church that has been "trying" to use ogo for about a year, but
since 85% of what gets posted to the calendar are recurring appointments
nobody wants to use the calendar as trying to get people to use more than
one interface (webui vs. outlook or mozilla) is next to impossible
(especially considering half our people are volunteers).

 

Peter

 


------=_NextPart_000_006C_01C86271.ACB5C800
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Recently reading a number of posts on the users list
concerning an old bug made me wonder about another old bug &#8211; that =
being
recurring appointments.&nbsp; Does anyone know the status of what seems =
to be
the pandora&#8217;s box that is recurring appointments via zidestore
(specifically zidelook/zidestore/outlook)?&nbsp; Is zidestore what it is =
and it
is up to the clients to conform to zidestore?&nbsp; Do I need to ask =
this
question of the zidelook people or the sogo groupdav connector for =
mozilla? I
have read enough posts to understand the differences between zidestore =
and
various clients, but not many posts about what is being done about =
it.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>We are a church that has been &#8220;trying&#8221; to =
use
ogo for about a year, but since 85% of what gets posted to the calendar =
are
recurring appointments nobody wants to use the calendar as trying to get =
people
to use more than one interface (webui vs. outlook or mozilla) is next to
impossible (especially considering half our people are =
volunteers).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Peter<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_006C_01C86271.ACB5C800--