Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-20 Thread armin.v...@mmlab.de
To close the case I can confirm that the Outlook FreeBusy lookup works 
now in our SOGo environment.


The solution was:

As our users have to authenticate using their full email address, the 
URL would has to look this way:


https://myserver.mydomain.mytld/SOGo/dav/public/%Name%@mydomain.mytld/freebusy.ifb

Thank you again for your assistance @MJ. Your hint made the difference:

> We see that outlook replaces the %Name% placeholder at lookup time with
> the appropriate localpart of the email address, and thus locates
> freebuzy info for all users on that domain.

Best regards
Armin



__ Information from mm-lab IT security __The message was 
checked by ESET Mail Security.
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-16 Thread mj




On 7/14/20 5:17 PM, armin.v...@mmlab.de wrote:
Then I assume that the %Name% placeholder works with Outlook but not 
with the webbrowser.


True, a webbrowser would have no idea what to replace %Name% with, and 
outlook does.


MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-14 Thread armin.v...@mmlab.de

Am 13.07.2020 um 18:02 schrieb mj (li...@merit.unu.edu):



On 13/07/2020 11:38, armin.v...@mmlab.de wrote:
Conclusion: Outlook won't be able to lookup the ifb file, if you do 
not use the real username but the %Name% placeholder.


Well my conclusion is different. We use the url with %Name% in it, and 
it works.


We see that outlook replaces the %Name% placeholder at lookup time with 
the appropriate localpart of the email address, and thus locates 
freebuzy info for all users on that domain.


Then I assume that the %Name% placeholder works with Outlook but not 
with the webbrowser.


But another idea reading again your hint that the %Name% placeholder 
will be replaced by the *localpart* of the email address:


As our users have to authenticate using their full email address, the 
URL would have to look this way:


https://myserver.mydomain.mytld/SOGo/dav/public/%Name%@mydomain.mytld/freebusy.ifb

I'll try that.

Best regards
Armin


You could even use the %SERVER% placeholder, to access different servers 
for different domains.


But anyway: if your config works for you, then there we have no problem, 
I guess. :-)


MJ


__ Information from mm-lab IT security __The message was 
checked by ESET Mail Security.
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-13 Thread mj




On 13/07/2020 11:38, armin.v...@mmlab.de wrote:
Conclusion: Outlook won't be able to lookup the ifb file, if you do not 
use the real username but the %Name% placeholder.


Well my conclusion is different. We use the url with %Name% in it, and 
it works.


We see that outlook replaces the %Name% placeholder at lookup time with 
the appropriate localpart of the email address, and thus locates 
freebuzy info for all users on that domain.


You could even use the %SERVER% placeholder, to access different servers 
for different domains.


But anyway: if your config works for you, then there we have no problem, 
I guess. :-)


MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-13 Thread armin.v...@mmlab.de

Hi MJ,

Am 08.07.2020 um 14:48 schrieb mj (li...@merit.unu.edu):

Hi,

On 7/8/20 2:18 PM, armin.v...@mmlab.de wrote:

I think that I made the mistake not to replace the %Name% string in
No you should keep the %Name%. Outlook will replace it with the 
localpart(@) of the provided email address.


Info: Our users have to authenticate by their email address: 
firstname.lastname@mydomain.mytld


For the following URLs called by the browser I get these results:

1) https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb
-> 400 Bad Request

2) https://myserver.mydomain.mytld/SOGo/dav/public/john.doe/freebusy.ifb
-> object not found: public -> john.doe -> freebusy.ifb

3) 
https://myserver.mydomain.mytld/SOGo/dav/public/john.doe@mydomain.mytld/freebusy.ifb

-> Download of John Doe's freebusy.ifb will be offered

Conclusion: Outlook won't be able to lookup the ifb file, if you do not 
use the real username but the %Name% placeholder.




https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb

by the real username. I assumed that this variable will be resolved 
automatically.

It will.

The test with the webbrowser shows that the freebusy.ifb file will be 
generated without any issue.

Then normally it should also work with the %Name% placeholder.

Could you tell me if you are also running Thunderbird Lightning 
clients in your environment? I'm wondering if the Freebusy lookup will 
work between users using Thunderbird Lightning and Outlook users 
because the mail clients use different mechanisms for it.


We were running straight caldav/lightning, but are more and more moving 
towards TbSync with CalDAV and ActiveSync.


Best,
MJ


__ Information from mm-lab IT security __The message was 
checked by ESET Mail Security.
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-08 Thread mj

Hi,

On 7/8/20 2:18 PM, armin.v...@mmlab.de wrote:

I think that I made the mistake not to replace the %Name% string in
No you should keep the %Name%. Outlook will replace it with the 
localpart(@) of the provided email address.




https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb

by the real username. I assumed that this variable will be resolved 
automatically.

It will.

The test with the webbrowser shows that the freebusy.ifb file will be 
generated without any issue.

Then normally it should also work with the %Name% placeholder.

Could you tell me if you are also running Thunderbird Lightning clients 
in your environment? I'm wondering if the Freebusy lookup will work 
between users using Thunderbird Lightning and Outlook users because the 
mail clients use different mechanisms for it.


We were running straight caldav/lightning, but are more and more moving 
towards TbSync with CalDAV and ActiveSync.


Best,
MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-08 Thread armin.v...@mmlab.de

Hi MJ!

Thank you very much for your detailed reply.

I think that I made the mistake not to replace the %Name% string in

https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb

by the real username. I assumed that this variable will be resolved 
automatically.


Your way to write it made very clear that it had to be replaced manually:

https://myserver.mydomain.mytld/SOGo/dav/public/username/freebusy.ifb

The test with the webbrowser shows that the freebusy.ifb file will be 
generated without any issue.


Could you tell me if you are also running Thunderbird Lightning clients 
in your environment? I'm wondering if the Freebusy lookup will work 
between users using Thunderbird Lightning and Outlook users because the 
mail clients use different mechanisms for it.


Best regards
Armin

Am 07.07.2020 um 12:13 schrieb mj (li...@merit.unu.edu):

Hi Armin,

I have just checked, and it seems to work here, Outlook 2016, imap mode, 
with the freebuzy url configured.


Just for the record: you don't need the CalDAV synchonizer for this 
config. The freebuzy lookup works of the provided .ifb url.


Perhaps the CalDAV Synchronizer is getting in the way?

The file freebusy.ifb is nowhere on your system, as it is generated 
dynamically on the fly by SOGo, specific for each user's freebuzy info. 
So no: don't create it.


Suppose you invite username@mydomain.mytld, try access in a browser:

https://myserver.mydomain.mytld/SOGo/dav/public/username/freebusy.ifb

It should give you the generated file with freebuzy info.

(note the matching mydomain.mytld in the url and the email address)

Best,
MJ

On 06/07/2020 08:34, armin.v...@mmlab.de wrote:

Hi!

FreeBusy lookups with Outlook do not work in my environment 
(black-white hatched bar which indicates that the FreeBusy info is not 
available). The environment consists of the following:


- Server: SOGo 4.3.1

- E-Mail-Client: Outlook 2016 (16.0.11929.20836)

- CalDAV Synchronizer: 3.8.0.0

I followed this guide 
https://sogo.nu/files/docs/SOGoOutlookConnectorConfigurationGuide.html 
and can confirm that synchronisation of both personal SOGo calendar 
and SOGo global address book work fine.


In the SOGo config file sogo.conf I added the following FreeBusy 
related lines and restarted the sogod service:


SOGoEnablePublicAccess = YES;
SOGoFreeBusyDefaultInterval = (7, 365);

In Outlook's FreeBusy settings I entered the URL 
https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb 
accordingly (path for publication and lookup path).


I was wondering where the file called "freebusy.ifb" would be located 
on the SOGo server and searched its entire filesystem, but couldn't 
detect it. Do I have to create it manually as an empty file and if so, 
where would I have to create it exactly (local path on the server)?


Regarding the users personal calendars' sharing settings I configured 
them for public access with "See Date & Time" by the SOGo WebGUI.


Apparently the above mentioned configuration guide is not complete. 
Sth. is missing there.


Could so. point me into the right direction, please?

Maybe the first thing to clarify is whether the file called 
"freebusy.ifb" has to be created manually.


Thank you very much!

BTW: FreeBusy lookup using Thunderbird Lightning works perfectly.

Kind regards
Armin



__ Information from mm-lab IT security __The message was 
checked by ESET Mail Security.
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Outlook 2016 FreeBusy lookup

2020-07-07 Thread mj

Hi Armin,

I have just checked, and it seems to work here, Outlook 2016, imap mode, 
with the freebuzy url configured.


Just for the record: you don't need the CalDAV synchonizer for this 
config. The freebuzy lookup works of the provided .ifb url.


Perhaps the CalDAV Synchronizer is getting in the way?

The file freebusy.ifb is nowhere on your system, as it is generated 
dynamically on the fly by SOGo, specific for each user's freebuzy info. 
So no: don't create it.


Suppose you invite username@mydomain.mytld, try access in a browser:

https://myserver.mydomain.mytld/SOGo/dav/public/username/freebusy.ifb

It should give you the generated file with freebuzy info.

(note the matching mydomain.mytld in the url and the email address)

Best,
MJ

On 06/07/2020 08:34, armin.v...@mmlab.de wrote:

Hi!

FreeBusy lookups with Outlook do not work in my environment (black-white 
hatched bar which indicates that the FreeBusy info is not available). 
The environment consists of the following:


- Server: SOGo 4.3.1

- E-Mail-Client: Outlook 2016 (16.0.11929.20836)

- CalDAV Synchronizer: 3.8.0.0

I followed this guide 
https://sogo.nu/files/docs/SOGoOutlookConnectorConfigurationGuide.html 
and can confirm that synchronisation of both personal SOGo calendar and 
SOGo global address book work fine.


In the SOGo config file sogo.conf I added the following FreeBusy related 
lines and restarted the sogod service:


SOGoEnablePublicAccess = YES;
SOGoFreeBusyDefaultInterval = (7, 365);

In Outlook's FreeBusy settings I entered the URL 
https://myserver.mydomain.mytld/SOGo/dav/public/%Name%/freebusy.ifb 
accordingly (path for publication and lookup path).


I was wondering where the file called "freebusy.ifb" would be located on 
the SOGo server and searched its entire filesystem, but couldn't detect 
it. Do I have to create it manually as an empty file and if so, where 
would I have to create it exactly (local path on the server)?


Regarding the users personal calendars' sharing settings I configured 
them for public access with "See Date & Time" by the SOGo WebGUI.


Apparently the above mentioned configuration guide is not complete. Sth. 
is missing there.


Could so. point me into the right direction, please?

Maybe the first thing to clarify is whether the file called 
"freebusy.ifb" has to be created manually.


Thank you very much!

BTW: FreeBusy lookup using Thunderbird Lightning works perfectly.

Kind regards
Armin

__ Information from mm-lab IT security __The message was 
checked by ESET Mail Security.

--
users@sogo.nu
https://inverse.ca/sogo/lists