<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Nov 20, 2019, at 11:06 AM, Deborah Pickett wrote:<br></div><blockquote type="cite" id="qt"><div class="qt-moz-cite-prefix">On 2019-11-20 10:03, ellie timoney
wrote:<br></div><blockquote cite="mid:5f8afb4d-e9cc-4135-a2b8-18bd362d8a3c@www.fastmail.com" type="cite"><blockquote type="cite"><pre wrap="" class="qt-moz-quote-pre">foo also includes "#calendars" and "#addressbooks" on my server so there
are weird characters to deal with.
<br></pre></blockquote><pre wrap="" class="qt-moz-quote-pre">Now that's an interesting detail to consider.
<br></pre></blockquote><p>I should restate my original message because I'm being fast and
loose with the meaning of "contains": two of the values for foo on
my server are "#calendars" and "#addressbooks". In other words,
there are top-level public mailboxes #calendars and #addressbooks
which themselves contain sub-calendars and sub-addressbooks. It
never occurred to me to have calendar or contacts folders deeper
in the normal shared folder namespace, though it has evidently
occurred to you.<br></p></blockquote><div><br></div><div>Oh, I see how I misread that! And... that also complicates things for me, I think (well, it's a possibility I hadn't even considered).<br></div><div><br></div><div>I'm curious how these are working for you, or what sort of configuration and workflows leads to having #calendars and #addressbooks as top-level shared mailboxes? I've only very recently started learning how our DAV bits work (they have previously been black-boxes for me), and so far have only seen these existing in user accounts. Maybe this is a separate thread though.<br></div><div><br></div></body></html>