#366 Public folders no more accessible

[Roquemaurel]

The public folders are no more accessible ("not found") with this new version, unless other settings must be defined (?)

[Mickael Guessant]

You probably switched from WebDav to EWS... I can confirm public folders do not work wiht 5.3.1 in EWS mode.
=> should be fixed in latest trunk build

[Roquemaurel]

<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">

I was in EWS mode

---

From: Mickael Guessant
[mailto:mguessan@users.sourceforge.net]

Sent: Sat,
Sep 7, 2019 7:17 PM GMT+0200

To:
[davmail:support-requests]
<366@support-requests.davmail.p.re.sourceforge.net>

Subject:
[davmail:support-requests] #366 Public folders no more
accessible

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

You probably switched from WebDav to EWS... I can confirm
public folders do not work wiht 5.3.1 in EWS mode.

=> should be fixed in latest trunk build

---

[support-requests:#366] Public
folders no more accessible

Status: open

Group: v5.3.1

Created: Tue Sep 03, 2019 07:04 AM UTC by
Roquemaurel

Last Updated: Tue Sep 03, 2019 07:04 AM UTC

Owner: Mickael Guessant

The public folders are no more accessible ("not found") with
this new version, unless other settings must be defined (?)

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/davmail/support-requests/366/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

<link href="https://sourceforge.net/p/davmail/support-requests/366/" itemprop="url">
<meta content="View" itemprop="name">

<meta content="View" itemprop="description">

[Scott Alfter]

I've run into the same problem when bringing up a new machine. I copied settings from the old desktop to the new, but didn't notice that the old one still had DavMail 5.2.0 on it. I put 5.3.1 on the new one, but with the same settings as on the older instance, I was unable to access a public folder on our Exchange 2010 server. (Don't blame me for the server; I don't manage it. :) ) This would seem to be a regression of some sort in CalDAV handling introduced some time after 5.2.0 was released. For now, I'm sticking with 5.2.0.

[Mickael Guessant]

Can you please test with latest trunk ?
https://github.com/mguessan/davmail#trunk-builds

[Roquemaurel]

<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">

I have access to the public folders with
this version

Thank you

---

From: Mickael Guessant
[mailto:mguessan@users.sourceforge.net]

Sent: Wed,
Sep 11, 2019 12:19 PM GMT+0200

To:
[davmail:support-requests]
<366@support-requests.davmail.p.re.sourceforge.net>

Subject:
[davmail:support-requests] Re: #366 Public folders no more
accessible

<meta content="text/html; charset=UTF-8" http-equiv="content-type">

Can you please test with latest trunk ?

https://github.com/mguessan/davmail#trunk-builds

---

[support-requests:#366] Public
folders no more accessible

Status: open

Group: v5.3.1

Created: Tue Sep 03, 2019 07:04 AM UTC by
Roquemaurel

Last Updated: Tue Sep 10, 2019 09:32 PM UTC

Owner: Mickael Guessant

The public folders are no more accessible ("not found") with
this new version, unless other settings must be defined (?)

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/davmail/support-requests/366/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

<link href="https://sourceforge.net/p/davmail/support-requests/366/" itemprop="url">
<meta content="View" itemprop="name">

<meta content="View" itemprop="description">

[Scott Alfter]

With the trunk build, I was able to view existing events and create a new event, but I wasn't able to delete the event I had created:

"ErrorInvalidOperation Meeting requests and cancellations can't be sent for calendar items located in public folders."

FWIW, 5.2.0 exhibits the same behavior, so that's probably an unrelated (or at best tangential) issue. The trunk build does fix basic accessibility to the calendar, however. I might never have noticed the deletion problem as I rarely have a need to delete entries once they're created. For now, I can delete them through OWA.

[Mickael Guessant]

Makes sense, this should be fixed in latest trunk.