evolution ews cannot follow our autodiscovery

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
For some reson Evo 3.32.x cannot follow our Autodiscovery at:
http://autodiscover.infinera.com/AutoDiscover/AutoDiscover.xml

That lands in our on premise exchange which should redirect to O365
Any idea why?

    Jocke
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
On Mon, 2019-07-01 at 16:35 +0000, Joakim Tjernlund via evolution-list
wrote:
> Any idea why?

        Hi,
not really, as it can be a server configuration thing too. You can try
to run evolution from a terminal with EWS debugging on:

   $ EWS_DEBUG=2 evolution

then open the EWS account Properties (or add a new user) and when you
click "Fetch URL" at the Receiving Email tab, then you'll see what
evolution-ews tried to use and what the server returned. You should be
asked for credentials, if not stored anywhere already.

The actual autodiscover URL is derived from the email address domain
and from the current Host URL.

        Bye,
        Milan

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
On Tue, 2019-07-02 at 08:39 +0200, Milan Crha via evolution-list wrote:

> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Mon, 2019-07-01 at 16:35 +0000, Joakim Tjernlund via evolution-list
> wrote:
> > Any idea why?
>
>         Hi,
> not really, as it can be a server configuration thing too. You can try
> to run evolution from a terminal with EWS debugging on:
>
>    $ EWS_DEBUG=2 evolution
>
> then open the EWS account Properties (or add a new user) and when you
> click "Fetch URL" at the Receiving Email tab, then you'll see what
> evolution-ews tried to use and what the server returned. You should be
> asked for credentials, if not stored anywhere already.
>
> The actual autodiscover URL is derived from the email address domain
> and from the current Host URL.

Did a manual autodisovery req using curl:

#! /bin/bash
function print_usage()
{
 echo "Usage: `basename $0` [options]"
 echo "Options:"
 echo "  -e  Autodiscover Endpoint URL"
 echo "  -a  SMTP address of account to perform autodiscover"
 echo "  -u  user ID used when logging into the specified Autodiscover Endpoint"
 exit 2
}
function parse_args()
{
 args=`getopt u:e:a: $*`
 if [ $? != 0 ]; then
  print_usage
 fi
 autod_url="https://autodiscover.infinera.com/autodiscover/autodiscover.xml"
 autod_email="[hidden email]"
 set -- $args
 for i
 do
  case "$1" in
   -e)
    autod_url="$2"; shift
    shift
    ;;
   -a)
    autod_email="$2"; shift
    shift
    ;;
   -u)
    autod_id="$2"; shift
    shift
    ;;
   --)
    shift
    break
    ;;
  esac
 done
 if [ -z "$autod_url" ] || [ -z "$autod_email" ]; then
  print_usage
 fi
}
function generate_autod_request_xml()
{
 _email_address=$1
 autod_xml=""
 autod_xml+='<?xml version="1.0" encoding="UTF-8"?>'
 autod_xml+='<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">'
 autod_xml+='   <Request>'
 autod_xml+='      <EMailAddress>'$_email_address'</EMailAddress>'
 autod_xml+='      <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>'
 autod_xml+='   </Request>'
 autod_xml+='</Autodiscover>'
}
parse_args $*
generate_autod_request_xml $autod_email
xml="$autod_xml"
curl --silent -v -k --header 'Content-Type: text/xml' --user "$autod_id" "$autod_url" --data "$xml"

where $auto_id is my domain user, I get this answer:
....

> POST /autodiscover/autodiscover.xml HTTP/1.1
> Host: autodiscover.infinera.com
> Authorization: Basic am9ja2VAaW5maW5lcmEuY29tOkt1cnRhbjgu
> User-Agent: curl/7.65.0
> Accept: */*
> Content-Type: text/xml
> Content-Length: 380
>
* upload completely sent off: 380 out of 380 bytes
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Cache-Control: private
< Content-Type: text/xml; charset=utf-8
< Server: Microsoft-IIS/8.0
< request-id: e9a4d88f-7e0d-405d-8767-eefae6cadbca
< Set-Cookie: ClientId=GLSJLS0BYUUHVVZQYCBQ; expires=Wed, 01-Jul-2020 11:07:38 GMT; path=/; HttpOnly
< X-CalculatedBETarget: sv-ex13-prd1.infinera.com
< X-DiagInfo: SV-EX13-PRD1
< X-BEServer: SV-EX13-PRD1
< X-AspNet-Version: 4.0.30319
< Set-Cookie: X-BackEndCookie=S-1-5-21-1757981266-1085031214-682003330-51010=u56Lnp2ejJqBm5nKyp7NxsjSmZzOz9LLypvL0p3JmczSxsrJm8nGzsaey82cgYHNz87G0s/H0s/Oq87Oxc/IxczH; expires=Thu, 01-Aug-2019 11:07:38 GMT; path=/autodiscover; secure; HttpOnly
< X-Powered-By: ASP.NET
< X-FEServer: SV-EX13-PRD1
< Date: Tue, 02 Jul 2019 11:07:38 GMT
< Content-Length: 407
<
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
  <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <Account>
      <Action>redirectAddr</Action>
      <RedirectAddr>[hidden email]</RedirectAddr>
    </Account>
  </Response>
* Connection #0 to host autodiscover.infinera.com left intact

Does this <Action>redirectAddr</Action> address make sense to Evolution?

 Jocke
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
In reply to this post by Gnome Evolution - General mailing list
On Tue, 2019-07-02 at 08:39 +0200, Milan Crha via evolution-list wrote:

> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Mon, 2019-07-01 at 16:35 +0000, Joakim Tjernlund via evolution-list
> wrote:
> > Any idea why?
>
>         Hi,
> not really, as it can be a server configuration thing too. You can try
> to run evolution from a terminal with EWS debugging on:
>
>    $ EWS_DEBUG=2 evolution
>
> then open the EWS account Properties (or add a new user) and when you
> click "Fetch URL" at the Receiving Email tab, then you'll see what
> evolution-ews tried to use and what the server returned. You should be
> asked for credentials, if not stored anywhere already.
>
> The actual autodiscover URL is derived from the email address domain
> and from the current Host URL.

EWS_DEBUG=2 evolution autodiscovery yields:

< HTTP/1.1 2 Error resolving “autodiscover.exchange.infinera.com”: Name or service not known
< Soup-Debug-Timestamp: 1562059608
< Soup-Debug: SoupMessage 0 (0x55b373a13460)
 
< HTTP/1.1 4 Could not connect: Connection refused
< Soup-Debug-Timestamp: 1562059608
< Soup-Debug: SoupMessage 0 (0x7fd8c8a160d0)
 

> POST /autodiscover/autodiscover.xml HTTP/1.1
> Soup-Debug-Timestamp: 1562059608
> Soup-Debug: SoupSessionAsync 1 (0x7fd820003220), SoupMessage 1 (0x7fd8c86c1e50), SoupSocket 1 (0x7fd81000bb60)
> Host: autodiscover.infinera.com
> User-Agent: Evolution/3.32.2
> Content-Type: text/xml; charset=utf-8
> Connection: Keep-Alive
> Authorization: NTLM TlRMTVNTUAABAAAABYIIAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAwAAAA
>
> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
>   <Request>
>     <EMailAddress>[hidden email]</EMailAddress>
>     <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>
>   </Request>
> </Autodiscover>
 
< HTTP/1.1 401 Unauthorized
< Soup-Debug-Timestamp: 1562059609
< Soup-Debug: SoupMessage 1 (0x7fd8c86c1e50)
< Server: Microsoft-IIS/8.0
< request-id: bf2ff059-d0e6-423e-afba-af08d93583aa
< Set-Cookie: ClientId=0PFBYHUURYZLMLGM9W; expires=Wed, 01-Jul-2020 09:26:49 GMT; path=/; HttpOnly
< WWW-Authenticate: NTLM
TlRMTVNTUAACAAAAEAAQADgAAAAFgokC0gVpwh6RHloAAAAAAAAAAK4ArgBIAAAABgLwIwAAAA9JAE4ARgBJAE4ARQBSAEEAAgAQAEkATgBGAEkATgBFAFIAQQABABgAUwBWAC0ARQBYADEAMwAtAFAAUgBEADEABAAYAGkAbgBmAGkAbg
BlAHIAYQAuAGMAbwBtAAMAMgBzAHYALQBlAHgAMQAzAC0AcAByAGQAMQAuAGkAbgBmAGkAbgBlAHIAYQAuAGMAbwBtAAUAGABpAG4AZgBpAG4AZQByAGEALgBjAG8AbQAHAAgAroBjRrgw1QEAAAAA
< WWW-Authenticate: Negotiate
< WWW-Authenticate: Basic realm="autodiscover.infinera.com"
< X-Powered-By: ASP.NET
< X-FEServer: SV-EX13-PRD1
< Date: Tue, 02 Jul 2019 09:26:48 GMT
< Content-Length: 0
<
 
> POST /autodiscover/autodiscover.xml HTTP/1.1
> Soup-Debug-Timestamp: 1562059609
> Soup-Debug: SoupSessionAsync 1 (0x7fd820003220), SoupMessage 1 (0x7fd8c86c1e50), SoupSocket 1 (0x7fd81000bb60), restarted
> Host: autodiscover.infinera.com
> User-Agent: Evolution/3.32.2
> Content-Type: text/xml; charset=utf-8
> Connection: Keep-Alive
> Content-Length: 341
> Authorization: NTLM
TlRMTVNTUAADAAAAGAAYAHIAAAAYABgAigAAAAAAAABAAAAAJAAkAEAAAAAOAA4AZAAAAAAAAAAAAAAAAYIIAGoAbwBjAGsAZQBAAGkAbgBmAGkAbgBlAHIAYQAuAGMAbwBtAFUATgBLAE4ATwBXAE4AwOrz3JwnYGgAAAAAAAAAAAAAAA
AAAAAA8oQ9RIcr5dkWFMk8X5BgqpD4CoZA58AF
>
> <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
>   <Request>
>     <EMailAddress>[hidden email]</EMailAddress>
>     <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>
>   </Request>
> </Autodiscover>
 
 The response code: 200
 The response headers for message 0x55b373e7f920
 =====================
Cache-Control: private
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
request-id: a0a5c293-f2bb-45b9-9ccb-04eae6b1a0fc
X-CalculatedFETarget: BN6PR04CU002.internal.outlook.com
X-BackEndHttpStatus: 200
Set-Cookie: exchangecookie=73f062e1e0534919be4bdfcbfb409a1e; path=/; secure
X-FEProxyInfo: BN6PR04CA0041.NAMPRD04.PROD.OUTLOOK.COM
X-CalculatedBETarget: BN8PR10MB3540.namprd10.prod.outlook.com
X-BackEndHttpStatus: 200
X-RUM-Validated: 1
X-NoBuffering: 1
X-AspNet-Version: 4.0.30319
X-BeSku: WCS5
X-DiagInfo: BN8PR10MB3540
X-BEServer: BN8PR10MB3540
X-FEServer: BN6PR04CA0041
X-Powered-By: ASP.NET
X-FEServer: HE1PR05CA0154
Date: Tue, 02 Jul 2019 09:24:14 GMT

<?xml version="1.0"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
  <soap11:Header xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <ServerVersionInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="
http://schemas.microsoft.com/exchange/services/2006/types" MajorVersion="15" MinorVersion="20" MajorBuildNumber="2032" MinorBuildNumber="20" Version="V2018_01_08"/>
  </soap11:Header>
  <soap11:Body xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <m:GetStreamingEventsResponse 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" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">
      <m:ResponseMessages>
        <m:GetStreamingEventsResponseMessage ResponseClass="Success">
          <m:ResponseCode>NoError</m:ResponseCode>
          <m:ConnectionStatus>OK</m:ConnectionStatus>
        </m:GetStreamingEventsResponseMessage>
      </m:ResponseMessages>
    </m:GetStreamingEventsResponse>
  </soap11:Body>
</Envelope>

 The response code: 200
 The response headers for message 0x55b373e7f920
 =====================
Cache-Control: private
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
request-id: a0a5c293-f2bb-45b9-9ccb-04eae6b1a0fc
X-CalculatedFETarget: BN6PR04CU002.internal.outlook.com
X-BackEndHttpStatus: 200
Set-Cookie: exchangecookie=73f062e1e0534919be4bdfcbfb409a1e; path=/; secure
X-FEProxyInfo: BN6PR04CA0041.NAMPRD04.PROD.OUTLOOK.COM
X-CalculatedBETarget: BN8PR10MB3540.namprd10.prod.outlook.com
X-BackEndHttpStatus: 200
X-RUM-Validated: 1
X-NoBuffering: 1
X-AspNet-Version: 4.0.30319
X-BeSku: WCS5
X-DiagInfo: BN8PR10MB3540
X-BEServer: BN8PR10MB3540
X-FEServer: BN6PR04CA0041
X-Powered-By: ASP.NET
X-FEServer: HE1PR05CA0154
Date: Tue, 02 Jul 2019 09:24:14 GMT

<?xml version="1.0"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
  <soap11:Header xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <ServerVersionInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="
http://schemas.microsoft.com/exchange/services/2006/types" MajorVersion="15" MinorVersion="20" MajorBuildNumber="2032" MinorBuildNumber="20" Version="V2018_01_08"/>
  </soap11:Header>
  <soap11:Body xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <m:GetStreamingEventsResponse 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" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">
      <m:ResponseMessages>
        <m:GetStreamingEventsResponseMessage ResponseClass="Success">
          <m:ResponseCode>NoError</m:ResponseCode>
          <m:ConnectionStatus>OK</m:ConnectionStatus>
        </m:GetStreamingEventsResponseMessage>
      </m:ResponseMessages>
    </m:GetStreamingEventsResponse>
  </soap11:Body>
</Envelope>

 The response code: 200
 The response headers for message 0x55b373e7f920
 =====================
Cache-Control: private
Transfer-Encoding: chunked
Server: Microsoft-IIS/10.0
request-id: a0a5c293-f2bb-45b9-9ccb-04eae6b1a0fc
X-CalculatedFETarget: BN6PR04CU002.internal.outlook.com
X-BackEndHttpStatus: 200
Set-Cookie: exchangecookie=73f062e1e0534919be4bdfcbfb409a1e; path=/; secure
X-FEProxyInfo: BN6PR04CA0041.NAMPRD04.PROD.OUTLOOK.COM
X-CalculatedBETarget: BN8PR10MB3540.namprd10.prod.outlook.com
X-BackEndHttpStatus: 200
X-RUM-Validated: 1
X-NoBuffering: 1
X-AspNet-Version: 4.0.30319
X-BeSku: WCS5
X-DiagInfo: BN8PR10MB3540
X-BEServer: BN8PR10MB3540
X-FEServer: BN6PR04CA0041
X-Powered-By: ASP.NET
X-FEServer: HE1PR05CA0154
Date: Tue, 02 Jul 2019 09:24:14 GMT

<?xml version="1.0"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
  <soap11:Header xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <ServerVersionInfo xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="
http://schemas.microsoft.com/exchange/services/2006/types" MajorVersion="15" MinorVersion="20" MajorBuildNumber="2032" MinorBuildNumber="20" Version="V2018_01_08"/>
  </soap11:Header>
  <soap11:Body xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <m:GetStreamingEventsResponse 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" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages">
      <m:ResponseMessages>
        <m:GetStreamingEventsResponseMessage ResponseClass="Success">
          <m:ResponseCode>NoError</m:ResponseCode>
          <m:ConnectionStatus>OK</m:ConnectionStatus>
        </m:GetStreamingEventsResponseMessage>
      </m:ResponseMessages>
    </m:GetStreamingEventsResponse>
  </soap11:Body>
</Envelope>

futhermore I notice that
- plain http requests are just redirected to https
- I never get an user/passwd prompt when I do fetch URL in Evo

 Jocke

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
On Tue, 2019-07-02 at 11:16 +0000, Joakim Tjernlund wrote:
> Does this <Action>redirectAddr</Action> address make sense
> to Evolution?

        Hi,
no, evolution-ews doesn't know about it. It would work fine if a
standard redirect response had been made by the server, the one through
the HTTP response code and such. It seems it might not be possible in
this case, as it changes the user name too. The RedirectAddr element
does that at least, according to [1]. And this [2] link shows what the
Action values can be.

You can rerun your script with
autodiscover.infinera.mail.onmicrosoft.com
host name and user as returned by the server, which should give you the
desired settings. You can copy the ASUrl content into the Host URL and
the OABUrl content into the OAB URL in Evolution, if they are present.
You can get multiple addresses for each, some may work only from the
company network, some can be accessible also from the public addresses.

On Tue, 2019-07-02 at 11:30 +0000, Joakim Tjernlund wrote:
> futhermore I notice that
> - plain http requests are just redirected to https
> - I never get an user/passwd prompt when I do fetch URL in Evo

It looks like the credentials had been read from the libsecret/gnome-
keyring. I see a request for "SoupMessage 1 (0x7fd8c86c1e50)", but not
its response (after the 401 response, which means that the server asked
for the credentials). It looks like you didn't receive the
"redirectAddr" within evolution-ews for some reason, or you didn't wait
long enough to have it included in the log. The next time, try to not
expose the whole log, remove the private information and the
information you cannot decipher (like the encoded bits).

This looks like a very specific case, but if you are willing to help to
test any changes, then feel free to open a new bug against evolution-ews
at [3] and we can follow there.
        Thanks and bye,
        Milan

[1] https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/redirectaddr-pox
[2] https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/action-pox
[3] https://gitlab.gnome.org/GNOME/evolution-ews/issues/new

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
On Tue, 2019-07-02 at 14:07 +0200, Milan Crha via evolution-list wrote:

> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On Tue, 2019-07-02 at 11:16 +0000, Joakim Tjernlund wrote:
> > Does this <Action>redirectAddr</Action> address make sense
> > to Evolution?
>
>         Hi,
> no, evolution-ews doesn't know about it. It would work fine if a
> standard redirect response had been made by the server, the one through
> the HTTP response code and such. It seems it might not be possible in
> this case, as it changes the user name too. The RedirectAddr element
> does that at least, according to [1]. And this [2] link shows what the
> Action values can be.

Right, seems this RedirectAddr is something new one have to deal with.

>
> You can rerun your script with
> autodiscover.infinera.mail.onmicrosoft.com
> host name and user as returned by the server, which should give you the
> desired settings. You can copy the ASUrl content into the Host URL and
> the OABUrl content into the OAB URL in Evolution, if they are present.
> You can get multiple addresses for each, some may work only from the
> company network, some can be accessible also from the public addresses.

Yes, I can make autodisovery work by injecting onmicrosoft and https://outlook.office365.com/EWS/....
in the right paces but that is really tedious

>
> On Tue, 2019-07-02 at 11:30 +0000, Joakim Tjernlund wrote:
> > futhermore I notice that
> > - plain http requests are just redirected to https
> > - I never get an user/passwd prompt when I do fetch URL in Evo
>
> It looks like the credentials had been read from the libsecret/gnome-
> keyring. I see a request for "SoupMessage 1 (0x7fd8c86c1e50)", but not
> its response (after the 401 response, which means that the server asked
> for the credentials). It looks like you didn't receive the
> "redirectAddr" within evolution-ews for some reason, or you didn't wait
> long enough to have it included in the log. The next time, try to not
> expose the whole log, remove the private information and the
> information you cannot decipher (like the encoded bits).

If I change Auth to Basic I get prompted for my creds.

> This looks like a very specific case, but if you are willing to help to
> test any changes, then feel free to open a new bug against evolution-ews
> at [3] and we can follow there.

Will do

>         Thanks and bye,
>         Milan
>
> [1] https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fclient-developer%2Fweb-service-reference%2Fredirectaddr-pox&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C607c081c9ab94ab7bc0208d6fee58651%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636976659084606933&amp;sdata=GSW1SJzjreBlEPyak5RZuiGzYQSleTgAzLKzSJOek%2FU%3D&amp;reserved=0
> [2] https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fclient-developer%2Fweb-service-reference%2Faction-pox&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C607c081c9ab94ab7bc0208d6fee58651%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636976659084606933&amp;sdata=gqd3jyEB7%2FjE%2BXe2nG4jxbmCHoKvIzsNiFbBOYTvkEc%3D&amp;reserved=0
> [3] https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.gnome.org%2FGNOME%2Fevolution-ews%2Fissues%2Fnew&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C607c081c9ab94ab7bc0208d6fee58651%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636976659084606933&amp;sdata=MIPKEYecOOV6zcsvWUEkKHes4q%2FHvnKZ0vHs8jfEMQE%3D&amp;reserved=0
>
> _______________________________________________
> evolution-list mailing list
> [hidden email]
> To change your list options or unsubscribe, visit ...
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.gnome.org%2Fmailman%2Flistinfo%2Fevolution-list&amp;data=02%7C01%7Cjoakim.tjernlund%40infinera.com%7C607c081c9ab94ab7bc0208d6fee58651%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C636976659084606933&amp;sdata=J%2FVnMq6h9EYcGIPP1iz4M3qH8QT%2FbYC%2FfE%2BBPCpHBpc%3D&amp;reserved=0

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
Reply | Threaded
Open this post in threaded view
|

Re: evolution ews cannot follow our autodiscovery

Gnome Evolution - General mailing list
On Tue, 2019-07-02 at 13:20 +0000, Joakim Tjernlund wrote:
> > This looks like a very specific case, but if you are willing to
> > help to test any changes, then feel free to open a new bug against
> > evolution-ews at [3] and we can follow there.
>
> Will do

        Hi,
just for the record, this is filled as this now:
https://gitlab.gnome.org/GNOME/evolution-ews/issues/53

        Thanks and bye,
        Milan

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list