Ken,
Thanks for the explanation, it was part of the problem! Now I get this
reply:
<?xml version="1.0" encoding="utf-8"?>
<C:schedule-response xmlns:C="urn:ietf:params:xml:ns:caldav" xmlns:D="DAV:">
<C:response>
<C:recipient>
<D:href>mailto:x...@yyy.zzz</D:href>
</C:recipient>
<C:request-status>5.3;No scheduling support for user</C:request-status>
<C:request-status>3.7;Invalid calendar user</C:request-status>
</C:response>
</C:schedule-response>
And the user is also on the server. Even more, it returns the same for
the same user that makes the request. At the same time, the freebusy URL
returns the scheduling info correctly for any user on the system.
What could be wrong now?
Thanks,
Anatoli
On 15/4/20 09:31, Ken Murchison wrote:
>
> On 4/14/20 10:22 PM, Anatoli wrote:
>> Hi All,
>>
>> I'm experimenting with freebusy support in Cyrus paired with Thunderbird.
>>
>> The manual [1] details the freebusy URL functionality and it works
>> correctly (if retrieved manually). But TB, AFAICU, doesn't support it.
>> Instead, it supports rfc6638 "Scheduling Extensions to CalDAV"
>> (https://wiki.mozilla.org/Lightning_implementing_RFC6638).
>>
>> The Cyrus documentation doesn't say explicitly if any of this is
>> supported, but when enabled:
>>
>> httpmodules: webdav caldav freebusy ischedule
>>
>> I can't make Cyrus return the correct info. Instead it replies with
>> "5.1;Service unavailable" (below goes an example exchange).
>>
>> Is this rfc supported? If yes, why may it not work as expected? I'm
>> testing it now with v3.0.5 as this is what I have at one deployment. I
>> can update it if there were relevant changes in later versions.
>>
>> Thanks,
>> Anatoli
>>
>> [1]
>> https://www.cyrusimap.org/dev/imap/download/installation/http/caldav.html#freebusy-url
>>
>>
>>
>> <1586914170<POST /dav/calendars/user/aaa%40bbb.xyz/Outbox/ HTTP/1.1
>> Accept: text/xml
>> Content-type: text/calendar; charset=utf-8
>> Connection: keep-alive
>> Accept-charset: utf-8,*;q=0.1
>> Recipient: mailto:t...@bbb.xyz
>> Content-length: 396
>> Host: mail.bbb.xyz
>> User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
>> Thunderbird/60.9.1 Lightning/6.2.5
>> Pragma: no-cache
>> Originator: mailto:a...@bbb.xyz
>> Accept-language: en-GB,en;q=0.5
>> Authorization: Basic ...
>> Cache-control: no-cache
>> Accept-encoding: gzip, deflate, br
>>
>> BEGIN:VCALENDAR
>> PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
>> VERSION:2.0
>> METHOD:REQUEST
>> BEGIN:VFREEBUSY
>> DTSTAMP:20200415T012930Z
>> ORGANIZER:mailto:a...@bbb.xyz
>> DTSTART:20200417T030000Z
>> DTEND:20200503T030000Z
>> UID:e7381fb8-f437-4772-b0ec-b019b909c50f
>> ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL:mail
>>
>> to:t...@bbb.xyz
>> END:VFREEBUSY
>> END:VCALENDAR
>>> 1586914170>HTTP/1.1 200 OK
>> Date: Wed, 15 Apr 2020 01:29:30 GMT
>> Strict-Transport-Security: max-age=600
>> Cache-Control: no-cache
>> Content-Type: application/xml; charset=utf-8
>> Content-Length: 317
>>
>> <?xml version="1.0" encoding="utf-8"?>
>> <C:schedule-response xmlns:C="urn:ietf:params:xml:ns:caldav"
>> xmlns:D="DAV:">
>> <C:response>
>> <C:recipient>
>> <D:href>mailto:t...@bbb.xyz</D:href>
>> </C:recipient>
>> <C:request-status>5.1;Service unavailable</C:request-status>
>> </C:response>
>> </C:schedule-response>
>
>
> This response looks like Cyrus thinks that t...@bbb.xyz is a remote user
> and is trying to send the free/busy request over email.
>
> Try adding the following option to imapd.conf:
>
> calendar_user_address_set: bbb.xyz
>
>
