Ángel -

Thank you - that's a good observation. I'm sure we've been migrated many,
many times, and I do have other clients connected to this Exchange account:
another Evolution client (no real troubles with it), and an Android Outlook
client.

Milan -

Fixing the debugging expression yields more of the same:
1. folder names that are more-often-than-not '(null)' in the Evolution
client, and
2. the only consistent error is a bit of XML:
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";>
  <s:Header>
    <h:ServerVersionInfo MajorVersion="15" MinorVersion="20"
MajorBuildNumber="4951"
      MinorBuildNumber="19" Version="V2018_01_08"
      xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types";
      xmlns:xsd="http://www.w3.org/2001/XMLSchema";
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  </s:Header>
  <s:Body>
    <m:SubscribeResponse xmlns:m="
http://schemas.microsoft.com/exchange/services/2006/messages";
      xmlns:xsd="http://www.w3.org/2001/XMLSchema";
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
      xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types";>
      <m:ResponseMessages>
        <m:SubscribeResponseMessage ResponseClass="Error">
          <m:MessageText>Id must be non-empty.</m:MessageText>
          <m:ResponseCode>ErrorInvalidIdEmpty</m:ResponseCode>
          <m:DescriptiveLinkKey>0</m:DescriptiveLinkKey>
        </m:SubscribeResponseMessage>
      </m:ResponseMessages>
    </m:SubscribeResponse>
  </s:Body>
</s:Envelope>
3. and a trailing error: (evolution:13676): evolution-ews-WARNING **:
11:49:26.814:
/wrkdirs/usr/portsmail/evolution-ews/work/evolution-ews-3.42.3/src/EWS/common/e-ews-notification.c:411:
Id must be non-empty.

The most frustrating thing about all of this is how nondeterministic it
feels - yesterday, Evolution started and recognized folder names correctly.
Today, it didn't. When I start it w/debugging turned on, the result is the
same (folder names are all '(null)').
There probably aren't many other FreeBSD+ews users, but I'll check in
greater depth on the forums.
Thanks to you both for your time!
Best,
Bridger

On Sat, Jan 29, 2022 at 5:09 PM Ángel <an...@16bits.net> wrote:

> On 2022-01-27 at 10:13 +0100, Milan Crha wrote:
> > Why the server returns multiple similarly-named folders
> > I do not know.
>
> Account was probably migrated through several servers / backends /
> versions, which had multiple ideas on how they should be named.
>
> Or, alternatively, it got multiple clients connected, each with its own
> idea on the right way to name them...
>
>
> Best regards
>
>
>
> _______________________________________________
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
>
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to