davmail-users

[Davmail-users] 2 minute delay when sending mail after network change

[Dan C. <jd...@uw...>]

If I send an email message through davmail, then switch wifi networks,
and then try to send a second message, there is a delay of two minutes.
I have included a debug log below, from the start of the second
connection until just after the 2 minute delay.  (The last two
timestamps differ by 2 minutes.)  I've used davmail for over a year, but
this only started happening recently.  It's possible it started when I
upgraded my system from Ubuntu 21.10 to 22.04, which upgraded davmail
from 5.5.1.3299-5 to 6.0.1.3390-1.  I see that there were O365 changes
there, so maybe they are related?

I have also included my .davmail.properties (minus the refresh token).

Any advice?

Thanks,

Dan

2022-07-28 16:04:39,795 DEBUG [davmail.smtp.SmtpServer] davmail  - Connection from /127.0.0.1 on port 1025
2022-07-28 16:04:39,795 INFO  [davmail.smtp.SmtpServer] davmail.connection  - CONNECT - 127.0.0.1:53760 
2022-07-28 16:04:39,873 DEBUG [SmtpConnection-53760] davmail.http.DavGatewaySSLSocketFactory  - createSocket outlook.office365.com 443
2022-07-28 16:04:40,207 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Test configuration status: 401
2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 220 DavMail 6.0.1-trunk SMTP ready at Thu Jul 28 16:04:40 EDT 2022
2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - < EHLO snowy
2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-snowy
2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-AUTH LOGIN PLAIN
2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250-8BITMIME
2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250 Hello
2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - < AUTH PLAIN ********
2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Got session davmail.exchange.ews.EwsExchangeSession@50e0b9aa from cache
2022-07-28 16:06:40,234 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Session davmail.exchange.ews.EwsExchangeSession@50e0b9aa for user jd...@uw... expired


davmail.ssl.keystoreType=
davmail.ssl.keystorePass=
davmail.proxyPassword=
davmail.oauth.tenantId=
davmail.oauth.clientId=
davmail.smtpPort=1025
davmail.enableKerberos=false
davmail.folderSizeLimit=
davmail.forceActiveSyncUpdate=false
davmail.imapAutoExpunge=false
davmail.useSystemProxies=false
davmail.proxyUser=
davmail.caldavEditNotifications=false
davmail.ssl.nosecuresmtp=false
davmail.caldavPastDelay=0
davmail.ssl.keyPass=
log4j.logger.httpclient.wire=WARN
davmail.noProxyFor=
davmail.server=true
log4j.logger.org.apache.commons.httpclient=WARN
davmail.popMarkReadOnRetr=false
davmail.ssl.nosecureimap=false
davmail.disableTrayActivitySwitch=false
davmail.caldavAutoSchedule=true
davmail.enableProxy=false
davmail.proxyPort=
davmail.logFileSize=10MB
davmail.mode=O365Manual
davmail.smtpSaveInSent=false
davmail.bindAddress=
davmail.ssl.nosecurepop=false
davmail.ssl.pkcs11Library=
log4j.rootLogger=WARN
davmail.ssl.keystoreFile=
log4j.logger.davmail=DEBUG
#log4j.logger.davmail=INFO
davmail.ssl.clientKeystoreType=
davmail.clientSoTimeout=
davmail.ssl.pkcs11Config=
davmail.imapPort=
davmail.ssl.clientKeystorePass=
davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
davmail.sentKeepDelay=0
davmail.ssl.nosecureldap=false
davmail.imapAlwaysApproxMsgSize=false
davmail.ssl.nosecurecaldav=false
davmail.popPort=
davmail.defaultDomain=
davmail.showStartupBanner=false
davmail.proxyHost=
davmail.oauth.persistToken=true
davmail.ldapPort=
davmail.server.certificate.hash=
log4j.logger.org.apache.http.wire=WARN
davmail.disableGuiNotifications=false
davmail.imapIdleDelay=
davmail.allowRemote=false
davmail.disableUpdateCheck=false
log4j.logger.org.apache.http=WARN
davmail.caldavPort=
davmail.enableKeepAlive=true
davmail.ssl.clientKeystoreFile=
davmail.logFilePath=/scratch/davmail.log
davmail.carddavReadPhoto=true
davmail.keepDelay=30
davmail.oauth.redirectUri=
davmail.caldavAlarmSound=

Re: [Davmail-users] 2 minute delay when sending mail after network change

[Dan C. <jd...@uw...>]

I can reproduce the issue with davmail_5.5.1-3299-1_all.deb available
at https://sourceforge.net/projects/davmail/files/davmail/5.5.1/ ,
so the upgrade to davmail doesn't explain the change.  Not sure what
else to suggest.

Dan

On Jul 28, 2022, Dan Christensen <jd...@uw...> wrote:

> If I send an email message through davmail, then switch wifi networks,
> and then try to send a second message, there is a delay of two minutes.
> I have included a debug log below, from the start of the second
> connection until just after the 2 minute delay.  (The last two
> timestamps differ by 2 minutes.)  I've used davmail for over a year, but
> this only started happening recently.  It's possible it started when I
> upgraded my system from Ubuntu 21.10 to 22.04, which upgraded davmail
> from 5.5.1.3299-5 to 6.0.1.3390-1.  I see that there were O365 changes
> there, so maybe they are related?
>
> I have also included my .davmail.properties (minus the refresh token).
>
> Any advice?
>
> Thanks,
>
> Dan
>
> 2022-07-28 16:04:39,795 DEBUG [davmail.smtp.SmtpServer] davmail  - Connection from /127.0.0.1 on port 1025
> 2022-07-28 16:04:39,795 INFO  [davmail.smtp.SmtpServer] davmail.connection  - CONNECT - 127.0.0.1:53760 
> 2022-07-28 16:04:39,873 DEBUG [SmtpConnection-53760] davmail.http.DavGatewaySSLSocketFactory  - createSocket outlook.office365.com 443
> 2022-07-28 16:04:40,207 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Test configuration status: 401
> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 220 DavMail 6.0.1-trunk SMTP ready at Thu Jul 28 16:04:40 EDT 2022
> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - < EHLO snowy
> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-snowy
> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-AUTH LOGIN PLAIN
> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250-8BITMIME
> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250 Hello
> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - < AUTH PLAIN ********
> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Got session davmail.exchange.ews.EwsExchangeSession@50e0b9aa from cache
> 2022-07-28 16:06:40,234 DEBUG [SmtpConnection-53760]
> davmail.exchange.ExchangeSession - Session
> davmail.exchange.ews.EwsExchangeSession@50e0b9aa for user
> jd...@uw... expired
>
>
> davmail.ssl.keystoreType=
> davmail.ssl.keystorePass=
> davmail.proxyPassword=
> davmail.oauth.tenantId=
> davmail.oauth.clientId=
> davmail.smtpPort=1025
> davmail.enableKerberos=false
> davmail.folderSizeLimit=
> davmail.forceActiveSyncUpdate=false
> davmail.imapAutoExpunge=false
> davmail.useSystemProxies=false
> davmail.proxyUser=
> davmail.caldavEditNotifications=false
> davmail.ssl.nosecuresmtp=false
> davmail.caldavPastDelay=0
> davmail.ssl.keyPass=
> log4j.logger.httpclient.wire=WARN
> davmail.noProxyFor=
> davmail.server=true
> log4j.logger.org.apache.commons.httpclient=WARN
> davmail.popMarkReadOnRetr=false
> davmail.ssl.nosecureimap=false
> davmail.disableTrayActivitySwitch=false
> davmail.caldavAutoSchedule=true
> davmail.enableProxy=false
> davmail.proxyPort=
> davmail.logFileSize=10MB
> davmail.mode=O365Manual
> davmail.smtpSaveInSent=false
> davmail.bindAddress=
> davmail.ssl.nosecurepop=false
> davmail.ssl.pkcs11Library=
> log4j.rootLogger=WARN
> davmail.ssl.keystoreFile=
> log4j.logger.davmail=DEBUG
> #log4j.logger.davmail=INFO
> davmail.ssl.clientKeystoreType=
> davmail.clientSoTimeout=
> davmail.ssl.pkcs11Config=
> davmail.imapPort=
> davmail.ssl.clientKeystorePass=
> davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
> davmail.sentKeepDelay=0
> davmail.ssl.nosecureldap=false
> davmail.imapAlwaysApproxMsgSize=false
> davmail.ssl.nosecurecaldav=false
> davmail.popPort=
> davmail.defaultDomain=
> davmail.showStartupBanner=false
> davmail.proxyHost=
> davmail.oauth.persistToken=true
> davmail.ldapPort=
> davmail.server.certificate.hash=
> log4j.logger.org.apache.http.wire=WARN
> davmail.disableGuiNotifications=false
> davmail.imapIdleDelay=
> davmail.allowRemote=false
> davmail.disableUpdateCheck=false
> log4j.logger.org.apache.http=WARN
> davmail.caldavPort=
> davmail.enableKeepAlive=true
> davmail.ssl.clientKeystoreFile=
> davmail.logFilePath=/scratch/davmail.log
> davmail.carddavReadPhoto=true
> davmail.keepDelay=30
> davmail.oauth.redirectUri=
> davmail.caldavAlarmSound=

Re: [Davmail-users] 2 minute delay when sending mail after network change

[Mickaël G. <mgu...@fr...>]

When you say switch wifi network, do you mean your network location IP 
address, ... also changes ?

I had issues a long time ago with company Exchange that had a different 
IP between external and internal facing frontend => had to wait for DNS 
resolution to expire.

However you seem to access O365 so shouldn't be an issue.

The 2 minute delay suggest that cached connections in DavMail fail after 
you switch, and we have an background thread to close idle connections.

Another question: do you have HTTP proxies on one side ?

Regards,


On 28/07/2022 22:38, Dan Christensen wrote:
> I can reproduce the issue with davmail_5.5.1-3299-1_all.deb available
> at https://sourceforge.net/projects/davmail/files/davmail/5.5.1/ ,
> so the upgrade to davmail doesn't explain the change.  Not sure what
> else to suggest.
>
> Dan
>
> On Jul 28, 2022, Dan Christensen <jd...@uw...> wrote:
>
>> If I send an email message through davmail, then switch wifi networks,
>> and then try to send a second message, there is a delay of two minutes.
>> I have included a debug log below, from the start of the second
>> connection until just after the 2 minute delay.  (The last two
>> timestamps differ by 2 minutes.)  I've used davmail for over a year, but
>> this only started happening recently.  It's possible it started when I
>> upgraded my system from Ubuntu 21.10 to 22.04, which upgraded davmail
>> from 5.5.1.3299-5 to 6.0.1.3390-1.  I see that there were O365 changes
>> there, so maybe they are related?
>>
>> I have also included my .davmail.properties (minus the refresh token).
>>
>> Any advice?
>>
>> Thanks,
>>
>> Dan
>>
>> 2022-07-28 16:04:39,795 DEBUG [davmail.smtp.SmtpServer] davmail  - Connection from /127.0.0.1 on port 1025
>> 2022-07-28 16:04:39,795 INFO  [davmail.smtp.SmtpServer] davmail.connection  - CONNECT - 127.0.0.1:53760
>> 2022-07-28 16:04:39,873 DEBUG [SmtpConnection-53760] davmail.http.DavGatewaySSLSocketFactory  - createSocket outlook.office365.com 443
>> 2022-07-28 16:04:40,207 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Test configuration status: 401
>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 220 DavMail 6.0.1-trunk SMTP ready at Thu Jul 28 16:04:40 EDT 2022
>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - < EHLO snowy
>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-snowy
>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-AUTH LOGIN PLAIN
>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250-8BITMIME
>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250 Hello
>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - < AUTH PLAIN ********
>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail.exchange.ExchangeSession  - Got session davmail.exchange.ews.EwsExchangeSession@50e0b9aa from cache
>> 2022-07-28 16:06:40,234 DEBUG [SmtpConnection-53760]
>> davmail.exchange.ExchangeSession - Session
>> davmail.exchange.ews.EwsExchangeSession@50e0b9aa for user
>> jd...@uw... expired
>>
>>
>> davmail.ssl.keystoreType=
>> davmail.ssl.keystorePass=
>> davmail.proxyPassword=
>> davmail.oauth.tenantId=
>> davmail.oauth.clientId=
>> davmail.smtpPort=1025
>> davmail.enableKerberos=false
>> davmail.folderSizeLimit=
>> davmail.forceActiveSyncUpdate=false
>> davmail.imapAutoExpunge=false
>> davmail.useSystemProxies=false
>> davmail.proxyUser=
>> davmail.caldavEditNotifications=false
>> davmail.ssl.nosecuresmtp=false
>> davmail.caldavPastDelay=0
>> davmail.ssl.keyPass=
>> log4j.logger.httpclient.wire=WARN
>> davmail.noProxyFor=
>> davmail.server=true
>> log4j.logger.org.apache.commons.httpclient=WARN
>> davmail.popMarkReadOnRetr=false
>> davmail.ssl.nosecureimap=false
>> davmail.disableTrayActivitySwitch=false
>> davmail.caldavAutoSchedule=true
>> davmail.enableProxy=false
>> davmail.proxyPort=
>> davmail.logFileSize=10MB
>> davmail.mode=O365Manual
>> davmail.smtpSaveInSent=false
>> davmail.bindAddress=
>> davmail.ssl.nosecurepop=false
>> davmail.ssl.pkcs11Library=
>> log4j.rootLogger=WARN
>> davmail.ssl.keystoreFile=
>> log4j.logger.davmail=DEBUG
>> #log4j.logger.davmail=INFO
>> davmail.ssl.clientKeystoreType=
>> davmail.clientSoTimeout=
>> davmail.ssl.pkcs11Config=
>> davmail.imapPort=
>> davmail.ssl.clientKeystorePass=
>> davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
>> davmail.sentKeepDelay=0
>> davmail.ssl.nosecureldap=false
>> davmail.imapAlwaysApproxMsgSize=false
>> davmail.ssl.nosecurecaldav=false
>> davmail.popPort=
>> davmail.defaultDomain=
>> davmail.showStartupBanner=false
>> davmail.proxyHost=
>> davmail.oauth.persistToken=true
>> davmail.ldapPort=
>> davmail.server.certificate.hash=
>> log4j.logger.org.apache.http.wire=WARN
>> davmail.disableGuiNotifications=false
>> davmail.imapIdleDelay=
>> davmail.allowRemote=false
>> davmail.disableUpdateCheck=false
>> log4j.logger.org.apache.http=WARN
>> davmail.caldavPort=
>> davmail.enableKeepAlive=true
>> davmail.ssl.clientKeystoreFile=
>> davmail.logFilePath=/scratch/davmail.log
>> davmail.carddavReadPhoto=true
>> davmail.keepDelay=30
>> davmail.oauth.redirectUri=
>> davmail.caldavAlarmSound=
>
>
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users

-- 
Mickael Guessant
mailto:mgu...@fr...

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

Marc,

Alrightly, nice to meet you too.

All,

It's called Azure AD Graph.  I think that name might be confusing -- it's
used by DavMail when talking to the Office 365 service.

Davmail uses required scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6
as listed in the Office 365 section of https://davmail.sourceforge.net/faq.html

I'm looking for some guidance here -- how does Davmail use this API?

What will stop working when it goes away?   (is it the LDAP, or calendar
services, or POP and IMAP also?  Authentication?)

For someone that knows the source, what is the recommended approach
to deal with this API going away?

I'm happy to crack open the source but I'd like to get some basic understanding first.

I'm also not sure how to test a replacement version, or test what will break
before it actually turns off.

            --Dan



----- Begin forwarded message:

From: Marc <Ma...@f1...>
Subject: RE: [Davmail-users] Azure AD Graph shutdown next year?
To: Dan Grillo <da...@gr...>, "dav...@li..."
    <dav...@li...>
Date: Mon, Feb 6 00:33:51 

Wtf is Azure AD Graph? Can't you test anything yourself? Why should anyone
working on davmail be knowledgable about a azure? 
I have shitty local exchange and davmail works fine on it without azure.


> 
> Pinging again on this -- any thoughts?  It seems like davmail might
> stop working soon.
> 
> 		--Dan
> 
> 
> 
> I opened https://github.com/mguessan/davmail/issues/264 to track this.
> 
>             --Dan
> 
> ----- Begin forwarded message:
> 
> Hi Davmail devs,
> 
> I'm bringing this one up again -- the deadline is approaching, I've been
> told March 31. when Azure AD Graph is getting shut down.
> 
> Will Davmail keep working or will some or all of it break?
> 
> Thank you,
> 
> 			--Dan
> 
> ----- Begin forwarded message:
> 
> Subject: Azure AD Graph shutdown next year?
> To: dav...@li...
> Date: Thu, Nov 17 2022 -0800
> 
> Davmail devs,
> 
> Does Davmail depend on Azure AD Graph?   I think it might because
> the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
> on https://davmail.sourceforge.net/faq.html.
> 
> Microsoft has accounted that Azure AD Graph is getting shut down
> next year:
> 
> https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview
> 
> And Microsoft itself is shutting down internal access in March 2023.
> 
> Thank you,
> 
>                 --Dan
> 
> 
> ----- End forwarded message
> --
> 
> 
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users


----- End forwarded message
-- 

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Rasmus L. <jr...@po...>]

Hear, hear, +1, I for one am crossing my 
fingers someone knows these answers for 
Grillo.  R

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Henrique M. <da...@ma...>]

> It's called Azure AD Graph.  I think that name might be confusing -- it's
> used by DavMail when talking to the Office 365 service.
>
> Davmail uses required scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6
> as listed in the Office 365 section of https://davmail.sourceforge.net/faq.html

This scope stopped working for me when my company updated
something on the Exchange back-end/O365.  I had to register
my own scope within my company's tenantID (probably not
using the proper terms here), which can be done on Azure.

AD Graph is deprecated but not totally "going away", it is
being replaced by Microsoft Graph, thus davmail may need to
be updated accordingly.

This microsoft page explains the process:
  https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq

Assume that one will need at least to migrate the scope from
AD Graph to Microsoft Graph.  Davmail may need to point
elsewhere for authentication with that scope, maybe used a
different API.

-- Henrique

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Mickaël G. <mgu...@fr...>]

Hello all,
As usual namings are misleading DavMail does not rely on Azure AD Graph 
and does not use Azure graph either.

However we used to be able to register applications with;
EWS.AccessAsUser.All (access to EWS API calls)
User.Read (assigned by default)

It seems Microsoft blocked new application registration since september 
2022 so it's no longer possible to register a new application to access 
EWS inside Azure AD.

Alternatives:

  * use the old DavMail clientid and allow it on tenant
  * use a Microsoft application clientId that still has access to EWS,
    e.g. Outlook desktop


On 08/02/2023 15:15, Henrique Martins wrote:
>> It's called Azure AD Graph.  I think that name might be confusing -- it's
>> used by DavMail when talking to the Office 365 service.
>>
>> Davmail uses required scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6
>> as listed in the Office 365 section ofhttps://davmail.sourceforge.net/faq.html
> This scope stopped working for me when my company updated
> something on the Exchange back-end/O365.  I had to register
> my own scope within my company's tenantID (probably not
> using the proper terms here), which can be done on Azure.
>
> AD Graph is deprecated but not totally "going away", it is
> being replaced by Microsoft Graph, thus davmail may need to
> be updated accordingly.
>
> This microsoft page explains the process:
>    https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq
>
> Assume that one will need at least to migrate the scope from
> AD Graph to Microsoft Graph.  Davmail may need to point
> elsewhere for authentication with that scope, maybe used a
> different API.
>
> -- Henrique
>
>
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users

-- 
Mickael Guessant
mailto:mgu...@fr...

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

Mickaël Guessant writes:
| 
| Hello all,
| As usual namings are misleading DavMail does not rely on Azure AD Graph and does not use Azure graph
| either. 
| 
| However we used to be able to register applications with;
| EWS.AccessAsUser.All (access to EWS API calls)
| User.Read (assigned by default) 
| 
| It seems Microsoft blocked new application registration since september 2022 so it's no longer
| possible to register a new application to access EWS inside Azure AD. 
| 
| Alternatives: 
|    
|    - use the old DavMail clientid and allow it on tenant 
|    - use a Microsoft application clientId that still has access to EWS, e.g. Outlook desktop 
| 

Hi Mickaël,

I checked with a coworker with access to the tenant configuration at work -- 
here's what he said:

    "The permission being deprecated for all Microsoft customers is
    User.Read, which is provided by Azure AD Graph, so if Davmail needs
    that still, it needs to move to the new implementation which is
    provided by Microsoft Graph APIs.  Davmail been using Azure AD Graph
    all this time whether the author is aware of it or not.  I double
    checked and yes, davmail in our tenant is currently configured to
    use User.Read"

It sounds like still a problem here...

Attached is a screenshot that shows User.Read permission rolls up
into Azure Active Directory Graph api.

                --Dan

Re: [Davmail-users] 2 minute delay when sending mail after network change

[Dan C. <jd...@uw...>]

The problem happens if I switch to a different wifi network in my home.
So I still have the same external IP address, but a different LAN IP
address (192.168.x.y).

It also happens when I switch from home to work, in which case I of
course have a different external IP address.

I don't think either situation should affect how I connect to the remote
O365 server.  I don't use any HTTP proxies, VPNs, etc.

Note that the log shows that after the network change, davmail is still
able to talk to the server: the EHLO gets a response.  It's the
authentication step that seems to block.

If it would help, I can send more logs, e.g. for a fast connection when
the network hasn't changed.

Dan

On Jul 30, 2022, Mickaël Guessant <mgu...@fr...> wrote:

> When you say switch wifi network, do you mean your network location IP address, ... also changes ?
>
> I had issues a long time ago with company Exchange that had a
> different IP between external and internal facing frontend => had to
> wait for DNS
> resolution to expire.
>
> However you seem to access O365 so shouldn't be an issue.
>
> The 2 minute delay suggest that cached connections in DavMail fail
> after you switch, and we have an background thread to close idle
> connections.
>
> Another question: do you have HTTP proxies on one side ?
>
> Regards,
>
>
> On 28/07/2022 22:38, Dan Christensen wrote:
>> I can reproduce the issue with davmail_5.5.1-3299-1_all.deb available
>> at https://sourceforge.net/projects/davmail/files/davmail/5.5.1/ ,
>> so the upgrade to davmail doesn't explain the change.  Not sure what
>> else to suggest.
>>
>> Dan
>>
>> On Jul 28, 2022, Dan Christensen <jd...@uw...> wrote:
>>
>>> If I send an email message through davmail, then switch wifi networks,
>>> and then try to send a second message, there is a delay of two minutes.
>>> I have included a debug log below, from the start of the second
>>> connection until just after the 2 minute delay.  (The last two
>>> timestamps differ by 2 minutes.)  I've used davmail for over a year, but
>>> this only started happening recently.  It's possible it started when I
>>> upgraded my system from Ubuntu 21.10 to 22.04, which upgraded davmail
>>> from 5.5.1.3299-5 to 6.0.1.3390-1.  I see that there were O365 changes
>>> there, so maybe they are related?
>>>
>>> I have also included my .davmail.properties (minus the refresh token).
>>>
>>> Any advice?
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>> 2022-07-28 16:04:39,795 DEBUG [davmail.smtp.SmtpServer] davmail -
>>> Connection from /127.0.0.1 on port 1025
>>> 2022-07-28 16:04:39,795 INFO [davmail.smtp.SmtpServer]
>>> davmail.connection - CONNECT - 127.0.0.1:53760
>>> 2022-07-28 16:04:39,873 DEBUG [SmtpConnection-53760]
>>> davmail.http.DavGatewaySSLSocketFactory - createSocket
>>> outlook.office365.com 443
>>> 2022-07-28 16:04:40,207 DEBUG [SmtpConnection-53760]
>>> davmail.exchange.ExchangeSession - Test configuration status: 401
>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail - >
>>> 220 DavMail 6.0.1-trunk SMTP ready at Thu Jul 28 16:04:40 EDT 2022
>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - < EHLO snowy
>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-snowy
>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-AUTH LOGIN PLAIN
>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250-8BITMIME
>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250 Hello
>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - < AUTH PLAIN ********
>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760]
>>> davmail.exchange.ExchangeSession - Got session
>>> davmail.exchange.ews.EwsExchangeSession@50e0b9aa from cache
>>> 2022-07-28 16:06:40,234 DEBUG [SmtpConnection-53760]
>>> davmail.exchange.ExchangeSession - Session
>>> davmail.exchange.ews.EwsExchangeSession@50e0b9aa for user
>>> jd...@uw... expired
>>>
>>>
>>> davmail.ssl.keystoreType=
>>> davmail.ssl.keystorePass=
>>> davmail.proxyPassword=
>>> davmail.oauth.tenantId=
>>> davmail.oauth.clientId=
>>> davmail.smtpPort=1025
>>> davmail.enableKerberos=false
>>> davmail.folderSizeLimit=
>>> davmail.forceActiveSyncUpdate=false
>>> davmail.imapAutoExpunge=false
>>> davmail.useSystemProxies=false
>>> davmail.proxyUser=
>>> davmail.caldavEditNotifications=false
>>> davmail.ssl.nosecuresmtp=false
>>> davmail.caldavPastDelay=0
>>> davmail.ssl.keyPass=
>>> log4j.logger.httpclient.wire=WARN
>>> davmail.noProxyFor=
>>> davmail.server=true
>>> log4j.logger.org.apache.commons.httpclient=WARN
>>> davmail.popMarkReadOnRetr=false
>>> davmail.ssl.nosecureimap=false
>>> davmail.disableTrayActivitySwitch=false
>>> davmail.caldavAutoSchedule=true
>>> davmail.enableProxy=false
>>> davmail.proxyPort=
>>> davmail.logFileSize=10MB
>>> davmail.mode=O365Manual
>>> davmail.smtpSaveInSent=false
>>> davmail.bindAddress=
>>> davmail.ssl.nosecurepop=false
>>> davmail.ssl.pkcs11Library=
>>> log4j.rootLogger=WARN
>>> davmail.ssl.keystoreFile=
>>> log4j.logger.davmail=DEBUG
>>> #log4j.logger.davmail=INFO
>>> davmail.ssl.clientKeystoreType=
>>> davmail.clientSoTimeout=
>>> davmail.ssl.pkcs11Config=
>>> davmail.imapPort=
>>> davmail.ssl.clientKeystorePass=
>>> davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
>>> davmail.sentKeepDelay=0
>>> davmail.ssl.nosecureldap=false
>>> davmail.imapAlwaysApproxMsgSize=false
>>> davmail.ssl.nosecurecaldav=false
>>> davmail.popPort=
>>> davmail.defaultDomain=
>>> davmail.showStartupBanner=false
>>> davmail.proxyHost=
>>> davmail.oauth.persistToken=true
>>> davmail.ldapPort=
>>> davmail.server.certificate.hash=
>>> log4j.logger.org.apache.http.wire=WARN
>>> davmail.disableGuiNotifications=false
>>> davmail.imapIdleDelay=
>>> davmail.allowRemote=false
>>> davmail.disableUpdateCheck=false
>>> log4j.logger.org.apache.http=WARN
>>> davmail.caldavPort=
>>> davmail.enableKeepAlive=true
>>> davmail.ssl.clientKeystoreFile=
>>> davmail.logFilePath=/scratch/davmail.log
>>> davmail.carddavReadPhoto=true
>>> davmail.keepDelay=30
>>> davmail.oauth.redirectUri=
>>> davmail.caldavAlarmSound=
>>
>>
>> _______________________________________________
>> Davmail-users mailing list
>> Dav...@li...
>> https://lists.sourceforge.net/lists/listinfo/davmail-users

Re: [Davmail-users] 2 minute delay when sending mail after network change

[Dan C. <jd...@uw...>]

Should I create an issue about this?  It is completely reproducible for
me.

I should have mentioned that I'm using emacs/Gnus to send mail, using
smtpmail with these settings:

  (setq message-send-mail-function 'smtpmail-send-it)
  (setq smtpmail-smtp-server "localhost")
  (setq smtpmail-smtp-service 1025)
  (setq smtpmail-stream-type `plain)

I don't have another email client set up to test with.  Can anyone else
reproduce this (with Gnus or with another client)?  Would additional
logs help?

Dan

On Jul 30, 2022, Dan Christensen <jd...@uw...> wrote:

> The problem happens if I switch to a different wifi network in my home.
> So I still have the same external IP address, but a different LAN IP
> address (192.168.x.y).
>
> It also happens when I switch from home to work, in which case I of
> course have a different external IP address.
>
> I don't think either situation should affect how I connect to the remote
> O365 server.  I don't use any HTTP proxies, VPNs, etc.
>
> Note that the log shows that after the network change, davmail is still
> able to talk to the server: the EHLO gets a response.  It's the
> authentication step that seems to block.
>
> If it would help, I can send more logs, e.g. for a fast connection when
> the network hasn't changed.
>
> Dan
>
> On Jul 30, 2022, Mickaël Guessant <mgu...@fr...> wrote:
>
>> When you say switch wifi network, do you mean your network location
>> IP address, ... also changes ?
>>
>> I had issues a long time ago with company Exchange that had a
>> different IP between external and internal facing frontend => had to
>> wait for DNS
>> resolution to expire.
>>
>> However you seem to access O365 so shouldn't be an issue.
>>
>> The 2 minute delay suggest that cached connections in DavMail fail
>> after you switch, and we have an background thread to close idle
>> connections.
>>
>> Another question: do you have HTTP proxies on one side ?
>>
>> Regards,
>>
>>
>> On 28/07/2022 22:38, Dan Christensen wrote:
>>> I can reproduce the issue with davmail_5.5.1-3299-1_all.deb available
>>> at https://sourceforge.net/projects/davmail/files/davmail/5.5.1/ ,
>>> so the upgrade to davmail doesn't explain the change.  Not sure what
>>> else to suggest.
>>>
>>> Dan
>>>
>>> On Jul 28, 2022, Dan Christensen <jd...@uw...> wrote:
>>>
>>>> If I send an email message through davmail, then switch wifi networks,
>>>> and then try to send a second message, there is a delay of two minutes.
>>>> I have included a debug log below, from the start of the second
>>>> connection until just after the 2 minute delay.  (The last two
>>>> timestamps differ by 2 minutes.)  I've used davmail for over a year, but
>>>> this only started happening recently.  It's possible it started when I
>>>> upgraded my system from Ubuntu 21.10 to 22.04, which upgraded davmail
>>>> from 5.5.1.3299-5 to 6.0.1.3390-1.  I see that there were O365 changes
>>>> there, so maybe they are related?
>>>>
>>>> I have also included my .davmail.properties (minus the refresh token).
>>>>
>>>> Any advice?
>>>>
>>>> Thanks,
>>>>
>>>> Dan
>>>>
>>>> 2022-07-28 16:04:39,795 DEBUG [davmail.smtp.SmtpServer] davmail -
>>>> Connection from /127.0.0.1 on port 1025
>>>> 2022-07-28 16:04:39,795 INFO [davmail.smtp.SmtpServer]
>>>> davmail.connection - CONNECT - 127.0.0.1:53760
>>>> 2022-07-28 16:04:39,873 DEBUG [SmtpConnection-53760]
>>>> davmail.http.DavGatewaySSLSocketFactory - createSocket
>>>> outlook.office365.com 443
>>>> 2022-07-28 16:04:40,207 DEBUG [SmtpConnection-53760]
>>>> davmail.exchange.ExchangeSession - Test configuration status: 401
>>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail - >
>>>> 220 DavMail 6.0.1-trunk SMTP ready at Thu Jul 28 16:04:40 EDT 2022
>>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - < EHLO snowy
>>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-snowy
>>>> 2022-07-28 16:04:40,208 DEBUG [SmtpConnection-53760] davmail  - > 250-AUTH LOGIN PLAIN
>>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250-8BITMIME
>>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - > 250 Hello
>>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760] davmail  - < AUTH PLAIN ********
>>>> 2022-07-28 16:04:40,209 DEBUG [SmtpConnection-53760]
>>>> davmail.exchange.ExchangeSession - Got session
>>>> davmail.exchange.ews.EwsExchangeSession@50e0b9aa from cache
>>>> 2022-07-28 16:06:40,234 DEBUG [SmtpConnection-53760]
>>>> davmail.exchange.ExchangeSession - Session
>>>> davmail.exchange.ews.EwsExchangeSession@50e0b9aa for user
>>>> jd...@uw... expired
>>>>
>>>>
>>>> davmail.ssl.keystoreType=
>>>> davmail.ssl.keystorePass=
>>>> davmail.proxyPassword=
>>>> davmail.oauth.tenantId=
>>>> davmail.oauth.clientId=
>>>> davmail.smtpPort=1025
>>>> davmail.enableKerberos=false
>>>> davmail.folderSizeLimit=
>>>> davmail.forceActiveSyncUpdate=false
>>>> davmail.imapAutoExpunge=false
>>>> davmail.useSystemProxies=false
>>>> davmail.proxyUser=
>>>> davmail.caldavEditNotifications=false
>>>> davmail.ssl.nosecuresmtp=false
>>>> davmail.caldavPastDelay=0
>>>> davmail.ssl.keyPass=
>>>> log4j.logger.httpclient.wire=WARN
>>>> davmail.noProxyFor=
>>>> davmail.server=true
>>>> log4j.logger.org.apache.commons.httpclient=WARN
>>>> davmail.popMarkReadOnRetr=false
>>>> davmail.ssl.nosecureimap=false
>>>> davmail.disableTrayActivitySwitch=false
>>>> davmail.caldavAutoSchedule=true
>>>> davmail.enableProxy=false
>>>> davmail.proxyPort=
>>>> davmail.logFileSize=10MB
>>>> davmail.mode=O365Manual
>>>> davmail.smtpSaveInSent=false
>>>> davmail.bindAddress=
>>>> davmail.ssl.nosecurepop=false
>>>> davmail.ssl.pkcs11Library=
>>>> log4j.rootLogger=WARN
>>>> davmail.ssl.keystoreFile=
>>>> log4j.logger.davmail=DEBUG
>>>> #log4j.logger.davmail=INFO
>>>> davmail.ssl.clientKeystoreType=
>>>> davmail.clientSoTimeout=
>>>> davmail.ssl.pkcs11Config=
>>>> davmail.imapPort=
>>>> davmail.ssl.clientKeystorePass=
>>>> davmail.url=https://outlook.office365.com/EWS/Exchange.asmx
>>>> davmail.sentKeepDelay=0
>>>> davmail.ssl.nosecureldap=false
>>>> davmail.imapAlwaysApproxMsgSize=false
>>>> davmail.ssl.nosecurecaldav=false
>>>> davmail.popPort=
>>>> davmail.defaultDomain=
>>>> davmail.showStartupBanner=false
>>>> davmail.proxyHost=
>>>> davmail.oauth.persistToken=true
>>>> davmail.ldapPort=
>>>> davmail.server.certificate.hash=
>>>> log4j.logger.org.apache.http.wire=WARN
>>>> davmail.disableGuiNotifications=false
>>>> davmail.imapIdleDelay=
>>>> davmail.allowRemote=false
>>>> davmail.disableUpdateCheck=false
>>>> log4j.logger.org.apache.http=WARN
>>>> davmail.caldavPort=
>>>> davmail.enableKeepAlive=true
>>>> davmail.ssl.clientKeystoreFile=
>>>> davmail.logFilePath=/scratch/davmail.log
>>>> davmail.carddavReadPhoto=true
>>>> davmail.keepDelay=30
>>>> davmail.oauth.redirectUri=
>>>> davmail.caldavAlarmSound=
>>>
>>>
>>> _______________________________________________
>>> Davmail-users mailing list
>>> Dav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/davmail-users
>
>
>
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users

[Davmail-users] java.lang.RuntimeException: Unable to configure SunPKCS11 provider Initialization failed slotListIndex is 0 but token only has 0 slots

[Edward J. S. <edw...@gm...>]

Hi. I had DavMail 6.0.1 running fine on CentOS 7.x. My sys admins recently upgraded my Linux box at work to RHEL 8.6 (actually Oracle Linux 8.6 but it's basically identical to RHEL), and now DavMail isn't working. The log shows this:

WARN  [ImapConnection-60182] davmail  - DavMail configuration exception:
Connect exception: java.lang.RuntimeException Unable to configure SunPKCS11 provider Initialization failed slotListIndex is 0 but token only has 0 slots

I'm using O365Manual mode where you copy a URL and paste it in your web browser in order to authenticate with a card reader. But I can't seem to get that far where it will let me do that anymore.

Has anyone else seen this error?

Anyone know the cause? Maybe this is due to some change in the OpenSC library?

Is there any fix or workaround?

I created an issue on GitHub about this last week. Sorry, I keep forgetting DavMail development isn't done on GitHub. :-)

https://github.com/mguessan/davmail/issues/226

Thanks,
Ed

Re: [Davmail-users] java.lang.RuntimeException: Unable to configure SunPKCS11 provider Initialization failed slotListIndex is 0 but token only has 0 slots

[Edward J. S. <edw...@gm...>]

On Aug 11, 2022, at 5:25 PM, Edward J. Sabol <edw...@gm...> wrote:
> Hi. I had DavMail 6.0.1 running fine on CentOS 7.x. My sys admins recently upgraded my Linux box at work to RHEL 8.6 (actually Oracle Linux 8.6 but it's basically identical to RHEL), and now DavMail isn't working. The log shows this:
> 
> WARN  [ImapConnection-60182] davmail  - DavMail configuration exception:
> Connect exception: java.lang.RuntimeException Unable to configure SunPKCS11 provider Initialization failed slotListIndex is 0 but token only has 0 slots
> 
> I'm using O365Manual mode where you copy a URL and paste it in your web browser in order to authenticate with a card reader. But I can't seem to get that far where it will let me do that anymore.
> 
> Has anyone else seen this error?
> 
> Anyone know the cause? Maybe this is due to some change in the OpenSC library?
> 
> Is there any fix or workaround?
> 
> I created an issue on GitHub about this last week. Sorry, I keep forgetting DavMail development isn't done on GitHub. :-)
> 
> https://github.com/mguessan/davmail/issues/226

It was disappointing that I never got any kind of reply about this. After almost 2 months of banging my head on this and not seeing emails sent to me in a timely fashion, I finally found a solution (or a workaround)!

All it required was changing

davmail.ssl.pkcs11Library=/usr/lib64/pkcs11/opensc-pkcs11.so

to

davmail.ssl.pkcs11Library=/usr/lib64/pkcs11/gnome-keyring-pkcs11.so

in my ~/.davmail.properties file.

I came across a completely-unrelated-to-DavMail posting somewhere which recommended switching from opensc-pkcs11.so to gnome-keyring-pkcs11.so for something else, so I thought I'd give it a try. I'm so very happy to discover that it worked for DavMail!

I hope this information helps out someone else who is using DavMail on RHEL 8.

Regards,
Ed

[Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

Davmail devs,

Does Davmail depend on Azure AD Graph?   I think it might because
the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
on https://davmail.sourceforge.net/faq.html.

Microsoft has accounted that Azure AD Graph is getting shut down
next year:

https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview

And Microsoft itself is shutting down internal access in March 2023.

Thank you,

                --Dan

-- 

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

Hi Davmail devs,

I'm bringing this one up again -- the deadline is approaching, I've been told
March 31. when Azure AD Graph is getting shut down.

Will Davmail keep working or will some or all of it break?

Thank you,

			--Dan

----- Begin forwarded message:

Subject: Azure AD Graph shutdown next year?
To: dav...@li...
Date: Thu, Nov 17 2022 -0800

Davmail devs,

Does Davmail depend on Azure AD Graph?   I think it might because
the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
on https://davmail.sourceforge.net/faq.html.

Microsoft has accounted that Azure AD Graph is getting shut down
next year:

https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview

And Microsoft itself is shutting down internal access in March 2023.

Thank you,

                --Dan


----- End forwarded message
-- 

Re: [Davmail-users] Fwd: Azure AD Graph shutdown next year?

[Mickaël G. <mgu...@fr...>]

Well we don't care about Azure AD Graph, we care about EWS support.

I just hope they still need to keep EWS endpoint online for a while for 
older Outlook versions compatibility.


It seems that Microsoft eventually implemented something useful on the 
Azure Graph side:

https://learn.microsoft.com/en-us/graph/outlook-get-mime-message

This looks promising for a future DavMail adapter.


Regards,


>> *From:* Dan Grillo <da...@gr...>
>> *Date:* January 10, 2023 at 9:52:51 PM EST
>> *To:* dav...@li...
>> *Subject:* *Re: [Davmail-users] Azure AD Graph shutdown next year?*
>> 
>> Hi Davmail devs,
>>
>> I'm bringing this one up again -- the deadline is approaching, I've 
>> been told
>> March 31. when Azure AD Graph is getting shut down.
>>
>> Will Davmail keep working or will some or all of it break?
>>
>> Thank you,
>>
>>            --Dan
>>
>> ----- Begin forwarded message:
>>
>> Subject: Azure AD Graph shutdown next year?
>> To: dav...@li...
>> Date: Thu, Nov 17 2022 -0800
>>
>> Davmail devs,
>>
>> Does Davmail depend on Azure AD Graph?   I think it might because
>> the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
>> on https://davmail.sourceforge.net/faq.html.
>>
>> Microsoft has accounted that Azure AD Graph is getting shut down
>> next year:
>>
>> https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview
>>
>> And Microsoft itself is shutting down internal access in March 2023.
>>
>> Thank you,
>>
>>                --Dan
>>
>>
>> ----- End forwarded message
>> -- 
>>
>>
>> _______________________________________________
>> Davmail-users mailing list
>> Dav...@li...
>> https://lists.sourceforge.net/lists/listinfo/davmail-users

-- 
Mickael Guessant
mailto:mgu...@fr...

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

I opened https://github.com/mguessan/davmail/issues/264 to track this.

            --Dan

----- Begin forwarded message:

From: Dan Grillo <da...@gr...>
Subject: Re: [Davmail-users] Azure AD Graph shutdown next year?
To: dav...@li...
Date: Tue, Jan 10 18:29:54 
Organization: /home/grio/.organization-davmail


Hi Davmail devs,

I'm bringing this one up again -- the deadline is approaching, I've been told
March 31. when Azure AD Graph is getting shut down.

Will Davmail keep working or will some or all of it break?

Thank you,

			--Dan

----- Begin forwarded message:

Subject: Azure AD Graph shutdown next year?
To: dav...@li...
Date: Thu, Nov 17 2022 -0800

Davmail devs,

Does Davmail depend on Azure AD Graph?   I think it might because
the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
on https://davmail.sourceforge.net/faq.html.

Microsoft has accounted that Azure AD Graph is getting shut down
next year:

https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview

And Microsoft itself is shutting down internal access in March 2023.

Thank you,

                --Dan


----- End forwarded message
-- 


_______________________________________________
Davmail-users mailing list
Dav...@li...
https://lists.sourceforge.net/lists/listinfo/davmail-users

----- End forwarded message
-- 

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Dan G. <da...@gr...>]

Pinging again on this -- any thoughts?  It seems like davmail might
stop working soon.

		--Dan

----- Begin forwarded message:

From: Dan Grillo <da...@gr...>
Subject: Re: [Davmail-users] Azure AD Graph shutdown next year?
To: dav...@li...
Date: Tue, Jan 10 19:04:29 
Organization: /home/grio/.organization-davmail


I opened https://github.com/mguessan/davmail/issues/264 to track this.

            --Dan

----- Begin forwarded message:

From: Dan Grillo <da...@gr...>
Subject: Re: [Davmail-users] Azure AD Graph shutdown next year?
To: dav...@li...
Date: Tue, Jan 10 18:29:54 
Organization: /home/grio/.organization-davmail


Hi Davmail devs,

I'm bringing this one up again -- the deadline is approaching, I've been
told March 31. when Azure AD Graph is getting shut down.

Will Davmail keep working or will some or all of it break?

Thank you,

			--Dan

----- Begin forwarded message:

Subject: Azure AD Graph shutdown next year?
To: dav...@li...
Date: Thu, Nov 17 2022 -0800

Davmail devs,

Does Davmail depend on Azure AD Graph?   I think it might because
the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
on https://davmail.sourceforge.net/faq.html.

Microsoft has accounted that Azure AD Graph is getting shut down
next year:

https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview

And Microsoft itself is shutting down internal access in March 2023.

Thank you,

                --Dan


----- End forwarded message
-- 

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Marc <Ma...@f1...>]

Wtf is Azure AD Graph? Can't you test anything yourself? Why should anyone working on davmail be knowledgable about a azure? 
I have shitty local exchange and davmail works fine on it without azure.


> 
> Pinging again on this -- any thoughts?  It seems like davmail might
> stop working soon.
> 
> 		--Dan
> 
> 
> 
> I opened https://github.com/mguessan/davmail/issues/264 to track this.
> 
>             --Dan
> 
> ----- Begin forwarded message:
> 
> Hi Davmail devs,
> 
> I'm bringing this one up again -- the deadline is approaching, I've been
> told March 31. when Azure AD Graph is getting shut down.
> 
> Will Davmail keep working or will some or all of it break?
> 
> Thank you,
> 
> 			--Dan
> 
> ----- Begin forwarded message:
> 
> Subject: Azure AD Graph shutdown next year?
> To: dav...@li...
> Date: Thu, Nov 17 2022 -0800
> 
> Davmail devs,
> 
> Does Davmail depend on Azure AD Graph?   I think it might because
> the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
> on https://davmail.sourceforge.net/faq.html.
> 
> Microsoft has accounted that Azure AD Graph is getting shut down
> next year:
> 
> https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview
> 
> And Microsoft itself is shutting down internal access in March 2023.
> 
> Thank you,
> 
>                 --Dan
> 
> 
> ----- End forwarded message
> --
> 
> 
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Geert S. <sta...@st...>]

On Sun, Feb 05, 2023 at 10:15:06PM -0800, Dan Grillo wrote:
> 
> Pinging again on this -- any thoughts?

Actions count


> It seems like davmail might stop working soon.

Not the first (and not the last) product killed by Microsoft.

(And don't blame Microsoft, blame their customers that allow them.)


> 
> 		--Dan
> 
> ----- Begin forwarded message:
> 
> From: Dan Grillo <da...@gr...>
> Subject: Re: [Davmail-users] Azure AD Graph shutdown next year?
> To: dav...@li...
> Date: Tue, Jan 10 19:04:29 
> Organization: /home/grio/.organization-davmail
> 
> 
> I opened https://github.com/mguessan/davmail/issues/264 to track this.
> 
>             --Dan
> 
> ----- Begin forwarded message:
> 
> From: Dan Grillo <da...@gr...>
> Subject: Re: [Davmail-users] Azure AD Graph shutdown next year?
> To: dav...@li...
> Date: Tue, Jan 10 18:29:54 
> Organization: /home/grio/.organization-davmail
> 
> 
> Hi Davmail devs,
> 
> I'm bringing this one up again -- the deadline is approaching, I've been
> told March 31. when Azure AD Graph is getting shut down.
> 
> Will Davmail keep working or will some or all of it break?
> 
> Thank you,
> 
> 			--Dan
> 
> ----- Begin forwarded message:
> 
> Subject: Azure AD Graph shutdown next year?
> To: dav...@li...
> Date: Thu, Nov 17 2022 -0800
> 
> Davmail devs,
> 
> Does Davmail depend on Azure AD Graph?   I think it might because
> the faq mentions scope 311a71cc-e848-46a1-bdf8-97ff7156d8e6 is listed
> on https://davmail.sourceforge.net/faq.html.
> 
> Microsoft has accounted that Azure AD Graph is getting shut down
> next year:
> 
> https://learn.microsoft.com/en-us/graph/migrate-azure-ad-graph-overview
> 
> And Microsoft itself is shutting down internal access in March 2023.
> 
> Thank you,
> 
>                 --Dan
> 
> 
> ----- End forwarded message
> -- 
> 
> 
> _______________________________________________
> Davmail-users mailing list
> Dav...@li...
> https://lists.sourceforge.net/lists/listinfo/davmail-users

-- 
Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Marc <Ma...@f1...>]

> 
> > It seems like davmail might stop working soon.
> 
> Not the first (and not the last) product killed by Microsoft.
> 
> (And don't blame Microsoft, blame their customers that allow them.)
> 

I blame Bill Gates with his stupid reasoning why he thinks it is good to hire lazy people.
 

Re: [Davmail-users] Azure AD Graph shutdown next year?

[Rasmus L. <jr...@po...>]

This might be related to issue 186.  https://github.com/mguessan/davmail/issues/186

mguessan commented Dec 22, 2021
> henning-schild commented Dec 9, 2021
> > 
> > https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-api-deprecations-in-exchange-web-services-for-exchange/ba-p/2813925
> > 
> > What does that mean for davmail? I guess it will stop working and we will need something based on ms graph?
> 
> As mentioned in the thread below the above post, there is no immediate impact on DavMail, however when Microsoft decides to completely remove EWS support current DavMail implementation will no longer work.
> 
> Moving to graph API at the moment is not an option: it lacks many of the fundamental APIs needed to retrieve full message content with properties, i.e. the MIME message body required for IMAP implementation.
> 
> Possible workarounds:
> 
>     wait for Microsoft to do the job properly and implement the missing features in Graph API
>     access O365 over OWA frontend: not sure they will work and would be a step back to old Exchange 2003 DavMail implementation

Ugh, Miscrosoft really seem like Oracle bad guys, shutting down this shutting down that.