davmail-users Mailing List for DavMail POP/IMAP/SMTP/Caldav to Exchange (Page 3)
Brought to you by:
mguessan
You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(2) |
May
(2) |
Jun
(5) |
Jul
(2) |
Aug
(4) |
Sep
(16) |
Oct
(13) |
Nov
(33) |
Dec
(48) |
2010 |
Jan
(16) |
Feb
(45) |
Mar
(15) |
Apr
(41) |
May
(18) |
Jun
(29) |
Jul
(62) |
Aug
(99) |
Sep
(81) |
Oct
(40) |
Nov
(28) |
Dec
(23) |
2011 |
Jan
(24) |
Feb
(17) |
Mar
(57) |
Apr
(22) |
May
(40) |
Jun
(39) |
Jul
(32) |
Aug
(27) |
Sep
(30) |
Oct
(21) |
Nov
(99) |
Dec
(21) |
2012 |
Jan
(27) |
Feb
(60) |
Mar
(35) |
Apr
(19) |
May
(33) |
Jun
(6) |
Jul
(5) |
Aug
(7) |
Sep
(9) |
Oct
(1) |
Nov
(8) |
Dec
(1) |
2013 |
Jan
(21) |
Feb
(4) |
Mar
(13) |
Apr
(20) |
May
(38) |
Jun
(26) |
Jul
(18) |
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(10) |
Dec
(5) |
2014 |
Jan
(3) |
Feb
(5) |
Mar
(2) |
Apr
(12) |
May
(7) |
Jun
(17) |
Jul
(19) |
Aug
(3) |
Sep
(1) |
Oct
(19) |
Nov
(10) |
Dec
(4) |
2015 |
Jan
(5) |
Feb
(5) |
Mar
(4) |
Apr
(4) |
May
(2) |
Jun
(6) |
Jul
(3) |
Aug
(10) |
Sep
(4) |
Oct
(31) |
Nov
(6) |
Dec
(3) |
2016 |
Jan
(3) |
Feb
(8) |
Mar
(13) |
Apr
(11) |
May
(19) |
Jun
(8) |
Jul
(7) |
Aug
(7) |
Sep
(2) |
Oct
(3) |
Nov
(3) |
Dec
(11) |
2017 |
Jan
(24) |
Feb
(9) |
Mar
(11) |
Apr
(7) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(21) |
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(1) |
2018 |
Jan
(4) |
Feb
(11) |
Mar
(4) |
Apr
|
May
|
Jun
(4) |
Jul
(4) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(11) |
Dec
(3) |
2019 |
Jan
(13) |
Feb
(10) |
Mar
(2) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(2) |
Oct
(4) |
Nov
(10) |
Dec
(5) |
2020 |
Jan
|
Feb
(3) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(5) |
Aug
|
Sep
(1) |
Oct
(5) |
Nov
|
Dec
(2) |
2021 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
2022 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2023 |
Jan
(10) |
Feb
(20) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(2) |
Nov
|
Dec
(1) |
2025 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Dan C. <jd...@uw...> - 2022-07-30 14:11:43
|
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 |
From: Mickaël G. <mgu...@fr...> - 2022-07-30 12:42:40
|
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... |
From: Dan C. <jd...@uw...> - 2022-07-28 20:38:45
|
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= |
From: Dan C. <jd...@uw...> - 2022-07-28 20:21:11
|
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= |
From: D <ka...@ai...> - 2022-07-20 21:24:28
|
I use davmail with an office365 email account and it works fine. Now I'm trying to configure another account, on a separate davmail instance (both instances are server instances). The relevant config is, as per instructions: davmail.url=https://outlook.office365.com/EWS/Exchange.asmx davmail.mode=O365Modern With the new account, when I attempt the first login I see an auth URL in the logs, which I open manually, and give the required permissions to the application. I seem to remember that, with the working account, on subsequent connections I got an authenticator request which I approved, and from then on everything worked fine. With the account I'm trying to setup, when I connect again to davmail, I get the following errors in the logs: davmail-acc | 2022-07-20 21:03:42,700 WARN [ImapConnection-58118] davmail.exchange.ExchangeSession - All network interfaces down or host unreachable ! davmail-acc | 2022-07-20 21:03:42,700 WARN [ImapConnection-58118] davmail.exchange.ExchangeSession - All network interfaces down or host unreachable ! davmail-acc | 2022-07-20 21:03:42,701 DEBUG [ImapConnection-58118] davmail.exchange.ExchangeSession - java.io.IOException: org.codehaus.jettison.json.JSONException: JSONObject["sCtx"] not found. JSONObject["sCtx"] not found. davmail-acc | java.io.IOException: org.codehaus.jettison.json.JSONException: JSONObject["sCtx"] not found. JSONObject["sCtx"] not found. davmail-acc | at davmail.exchange.auth.O365Authenticator.authenticate(O365Authenticator.java:238) davmail-acc | at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:182) davmail-acc | at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:93) davmail-acc | at davmail.imap.ImapConnection.run(ImapConnection.java:155) Don't know where to look as, like I said, I have another identical setup which works. Thanks for any help |
From: Mike B. <mi...@mb...> - 2022-04-05 13:22:14
|
I was a bit hasty with the logs, after 5 minutes they looked like this: DavMail: ``` 2022-04-05 14:16:53,142 INFO [davmail.smtp.SmtpServer] davmail.connection - CONNECT - 0:0:0:0:0:0:0:1:62631 2022-04-05 14:16:53,217 INFO [SmtpConnection-62631] org.apache.commons.httpclient.auth.AuthChallengeProcessor - ntlm authentication scheme selected 2022-04-05 14:16:53,217 INFO [SmtpConnection-62631] org.apache.commons.httpclient.HttpMethodDirector - No credentials available for NTLM <any realm>@mail.pmcs.de:443 2022-04-05 14:21:53,223 ERROR [SmtpConnection-62631] davmail - Read timed out java.net.SocketTimeoutException: Read timed out at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283) at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309) at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350) at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803) at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966) at java.base/java.net.Socket$SocketInputStream.read(Socket.java:961) at java.base/java.io.FilterInputStream.read(FilterInputStream.java:82) at java.base/java.io.PushbackInputStream.read(PushbackInputStream.java:135) at davmail.AbstractConnection$LineReaderInputStream.readLine(AbstractConnection.java:55) at davmail.AbstractConnection.readClient(AbstractConnection.java:223) at davmail.smtp.SmtpConnection.run(SmtpConnection.java:68) 2022-04-05 14:21:53,224 INFO [SmtpConnection-62631] davmail.connection - DISCONNECT - 0:0:0:0:0:0:0:1:62631 ``` MailMate: ``` 12:16:53 Running action 12:16:53 Handling request 12:16:53 Clearing connection to localhost 12:16:53 Ready to run action (type: 1000, retry count: 0) 12:16:53 Clearing connection to localhost 12:16:53 Trying to connect to localhost on port 1025 (CFNetwork) with STARTTLS (not required) 12:16:53 Resolved hostname (localhost). 12:16:53 Successful connection. 12:16:53 Ready for reading. 12:16:53 S: 220 DavMail 5.5.1-3299 SMTP ready at Tue Apr 05 14:16:53 CEST 2022 12:16:53 Warning: Unknown response ignored: '220 DavMail 5.5.1-3299 SMTP ready at Tue Apr 05 14:16:53 CEST 2022' (status: 'DAVMAIL'). 12:21:53 Waited 300 seconds on read. 12:21:53 S: 421 Read timed out 12:21:53 Warning: Unknown response ignored: '421 Read timed out ' (status: 'READ'). 12:21:53 Error: Reading ended without error. 12:21:53 S: <<< terminated reading >>> 12:21:53 Error code: 10 12:21:53 Failed action (1000). Reset observed read/write timeouts: 203/8 12:21:53 Handling reply ``` -- Best Regards Mike |
From: Mike B. <mi...@mb...> - 2022-04-05 12:31:04
|
Moin, today, to test something, I removed my company mail account, which had been working smoothly until recently, and then tried to create a new one. Suddenly there is no synchronisation at all. MailMate 1.14 (5882) + DavMail 5.5.1-3299 on macOS Monterey 12.3 DavMail says: ``` 2022-04-05 13:54:55,588 INFO [davmail.smtp.SmtpServer] davmail.connection - CONNECT - 0:0:0:0:0:0:0:1:62298 2022-04-05 13:54:55,956 INFO [SmtpConnection-62298] org.apache.commons.httpclient.auth.AuthChallengeProcessor - ntlm authentication scheme selected 2022-04-05 13:54:55,956 INFO [SmtpConnection-62298] org.apache.commons.httpclient.HttpMethodDirector - No credentials available for NTLM <any realm>@mail.pmcs.de:443 2022-04-05 13:57:56,967 INFO [SmtpConnection-62298] davmail.connection - DISCONNECT - 0:0:0:0:0:0:0:1:62298 ``` The MailMate activity viewer says: ``` 12:08:07 Running action 12:08:07 Handling request 12:08:07 Clearing connection to localhost 12:08:07 Ready to run action (type: 1000, retry count: 0) 12:08:07 Clearing connection to localhost 12:08:07 Trying to connect to localhost on port 1025 (CFNetwork) with STARTTLS (not required) 12:08:07 Resolved hostname (localhost). 12:08:07 Successful connection. ``` and than nothing happens, apart from a spinning wheel on the account in the sidebar. Does anyone have an idea where the problem might be? -- Best Regards Mike |
From: Rasmus L. <jr...@po...> - 2022-03-30 11:47:15
|
I'm glad to hear that. |
From: Lars B. <la...@la...> - 2022-03-30 11:30:25
|
Thank you! davmail.mode=O365Manual works perfectly. Lars On Tue, Mar 29, 2022 at 10:59:43PM +0000, Rasmus Liland wrote: > Dear Lars, > > cf. [1], maybe try to add > > davmail.authenticator=davmail.exchange.auth.O365ManualAuthenticator > > to get a url in the terminal? But, I > have not tried this myself ... > > Best, > Rasmus > > [1] https://sourceforge.net/p/davmail/discussion/644056/thread/85824d313b/?limit=25 |
From: Rasmus L. <jr...@po...> - 2022-03-29 23:18:18
|
Dear Lars, cf. [1], maybe try to add davmail.authenticator=davmail.exchange.auth.O365ManualAuthenticator to get a url in the terminal? But, I have not tried this myself ... Best, Rasmus [1] https://sourceforge.net/p/davmail/discussion/644056/thread/85824d313b/?limit=25 |
From: Lars B. <la...@la...> - 2022-03-22 14:34:02
|
Hi, list! I've used DavMail for years. Yesterday my company started to use two factor authentication. As I'm blind, and are only using the text console in Linux, and programs like mutt and vdirsyncer, it seems that I cannot activate the O365Interactive mode in DavMail to provide the needed credentials. So my questions is: - Is there a way to activate O365Interactive mode without GUI? - If not, how can I get DavMail working again? Thanks in advance Lars |
From: Cassio P. de C. <cas...@gm...> - 2022-01-20 10:37:00
|
Dear all, When using thunderbird + davmail (with the app code of thunderbird into davmail), I am getting an error from the MS server: "AADSTS90027: We are unable to issue tokens from this API version on the MSA tenant. Please contact the application vendor as they need to use version 2.0 of the protocol to support this." I know that the app code is being accepted by the server (since before was denied leading to another error, but this was resolved). Is this something faced by anybody who has a solution to it? Am I missing something obvious? I have been searching around for a while but did not find a way yet. Thanks in advance, cassio. |
From: Ole H. N. <Ole...@fy...> - 2021-12-21 11:29:28
|
Now there is a new CVE https://nvd.nist.gov/vuln/detail/CVE-2021-4104 which states: > JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. Question: Does davmail configure the use of JMSAppender and become vulnerable? Thanks, Ole On 12/14/21 18:23, Mickaël Guessant wrote: > The good news is that DavMail is *not* vulnerable to latest Log4J 2 CVE as > it depends on log4J version 1. > > Regards, > > > Le 14/12/2021 à 08:52, Ole Holm Nielsen via Davmail-users a écrit : >> Hi, >> >> We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS >> 7.9. However, it's only a few days ago that the Vulnerability in Apache >> Log4j (CVE-2021-44228-Log4j) was announced. We note that Davmail >> includes a log4j component: >> >> $ rpm -ql davmail | grep log4j >> /usr/share/davmail/lib/log4j-1.2.16.jar >> /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar >> >> Question: Is davmail vulnerable to log4j? If so, when could we expect a >> security fix? |
From: Geert S. <sta...@st...> - 2021-12-14 18:00:51
|
On Tue, Dec 14, 2021 at 06:23:29PM +0100, Mickaël Guessant wrote: To: dav...@li... > Le 14/12/2021 à 08:52, Ole Holm Nielsen via Davmail-users a écrit : > > Hi, > > > > We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS > > 7.9. However, it's only a few days ago that the Vulnerability in Apache > > Log4j (CVE-2021-44228-Log4j) was announced. We note that Davmail > > includes a log4j component: > > > > $ rpm -ql davmail | grep log4j > > /usr/share/davmail/lib/log4j-1.2.16.jar > > /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar > > > > Question: Is davmail vulnerable to log4j? If so, when could we expect a > > security fix? > > > > Thanks, > > Ole > > > The good news is that DavMail is *not* vulnerable to latest Log4J 2 CVE as > it depends on log4J version 1. FWIW: That matches https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001684#38 > Regards, > Mickaël Guessant @Alexandre: FYI, your message didn't yet reach Davmail mailinglist subscribers. Groeten Geert Stappers -- Silence is hard to parse |
From: Mickaël G. <mgu...@fr...> - 2021-12-14 17:23:39
|
The good news is that DavMail is *not* vulnerable to latest Log4J 2 CVE as it depends on log4J version 1. Regards, Le 14/12/2021 à 08:52, Ole Holm Nielsen via Davmail-users a écrit : > Hi, > > We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS > 7.9. However, it's only a few days ago that the Vulnerability in > Apache Log4j (CVE-2021-44228-Log4j) was announced. We note that > Davmail includes a log4j component: > > $ rpm -ql davmail | grep log4j > /usr/share/davmail/lib/log4j-1.2.16.jar > /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar > > Question: Is davmail vulnerable to log4j? If so, when could we expect > a security fix? > > Thanks, > Ole > |
From: Geert S. <sta...@st...> - 2021-12-14 15:09:27
|
On Tue, Dec 14, 2021 at 08:52:50AM +0100, Ole Holm Nielsen via Davmail-users wrote: > Hi, > > We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS 7.9. > However, it's only a few days ago that the Vulnerability in Apache Log4j > (CVE-2021-44228-Log4j) was announced. We note that Davmail includes a log4j > component: > > $ rpm -ql davmail | grep log4j > /usr/share/davmail/lib/log4j-1.2.16.jar > /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar > > Question: Is davmail vulnerable to log4j? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001684 discusses the same concern > If so, > when could we expect a security fix? Qouting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001684#17 Also, since a while already, Java now has its own internal logging framework (java.util.logging.Logger), so there should be less and less reason to use potentially unsafe third-party logging libraries (but switching to java's internal logging might be more difficult to do in the short run than just upgrading to a newer version). Groeten Geert Stappers -- Silence is hard to parse |
From: Geert S. <sta...@st...> - 2021-12-14 15:04:30
|
On Tue, Dec 14, 2021 at 08:52:50AM +0100, Ole Holm Nielsen via Davmail-users wrote: > Hi, > > We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS 7.9. > However, it's only a few days ago that the Vulnerability in Apache Log4j > (CVE-2021-44228-Log4j) was announced. We note that Davmail includes a log4j > component: > > $ rpm -ql davmail | grep log4j > /usr/share/davmail/lib/log4j-1.2.16.jar > /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar > > Question: Is davmail vulnerable to log4j? If so, when could we expect a > security fix? Qouting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001684#22 Debian maintainer of Davmail, Alexandre Rossi: > Also, since a while already, Java now has its own internal logging > framework (java.util.logging.Logger), so there should be less and > less reason to use potentially unsafe third-party logging libraries > (but switching to java's internal logging might be more difficult > to do in the short run than just upgrading to a newer version). I'll try to report this upstream. And I hope this helps Groeten Geert Stappers -- Silence is hard to parse |
From: Ole H. N. <Ole...@fy...> - 2021-12-14 11:26:07
|
Hi, We have installed davmail 6.0.1 dated Dec. 3, 2021 as an RPM on CentOS 7.9. However, it's only a few days ago that the Vulnerability in Apache Log4j (CVE-2021-44228-Log4j) was announced. We note that Davmail includes a log4j component: $ rpm -ql davmail | grep log4j /usr/share/davmail/lib/log4j-1.2.16.jar /usr/share/davmail/lib/slf4j-log4j12-1.7.25.jar Question: Is davmail vulnerable to log4j? If so, when could we expect a security fix? Thanks, Ole -- Ole Holm Nielsen PhD, Senior HPC Officer Department of Physics, Technical University of Denmark |
From: Mickaël G. <mgu...@fr...> - 2021-12-03 16:50:54
|
Bugfix release with a few Office 365 enhancements ### O365 - O365: default to MSCAPI on windows for native client certificate access - O365: name button Send instead of OK in manual authenticator dialog - OS65: merge https://github.com/mguessan/davmail/pull/158 Added Copy to Clipboard button Manual auth dialog ### Linux - Linux: improve "davmail azul" error handling - Linux: Update changelog in RPM spec - Linux: Fix RPM spec, remote source does not work - Linux: Merge RPM spec contribution from michals on https://build.opensuse.org, check for systemd support and deploy the right service ### HC4 - HC4: make DavMail Kerberos configuration provider ### EWS - EWS: merge https://github.com/mguessan/davmail/pull/106 Support servers only offering EWS/Services.wsdl instead of EWS/Exchange.asmx ### Documentation - Doc: Remove HttpClient migration warning - Doc: instructions on standalone setup on Linux for best O365 support - Update readme for Github home page -- Mickaël Guessant |
From: Gregor Z. <tel...@gm...> - 2021-07-31 10:42:16
|
Hi Mickaël, Rasmus, --text follows this line-- thanks for your help, I figured to not configure davmail.oauth.clientId otherwise my ~/.davmail.properties contains: davmail.oauth.tenantId=xxxxxxxxxxxxxxxxxxxxxxxxx davmail.mode=O365Interactive davmail.url=https://outlook.office365.com/EWS/Exchange.asmx davmail.oauth.redirectUri=https://login.microsoftonline.com/common/oauth2/nativeclient this works, hurray! But imap access is very slooow with mutt although configured to use a cache. Ciao and thanks for your help and davmail; Gregor * Mickaël Guessant <mgu...@fr...> [2021-07-28; 19:35]: > Indeed Rasmus, using native Outlook desktop clientId is a workaround. > > However if you have administrator access to target O365 tenant using > your own clientId is better to help you track logs. > > Anyway Gregor please make sure you give your custom clientId the right > scopes, see: > > http://davmail.sourceforge.net/faq.html > > Note that those scopes are *not* graph API scopes. |
From: Henrique M. <da...@ma...> - 2021-07-29 20:01:14
|
> Is this a davmail problem, or maybe different java Java problem, fixed. Next problem:-) On the machine I'm having trouble, if I set davmail.server=false davmail.mode=Interactive when I try to fetch mail, davmail opens a connection to the o365 login screen, but if I set davmail.mode=Modern it does not give me the URL for me cut an paste to a browser, authenticate through MFA, etc. Error message is: All network interfaces down or host unreachable ! but looking in the log file (debug=ALL) the real reason seems to be: java.io.IOException: MFA authentication methods not supported and the methods listed above were Authentication method: OneWaySMS Authentication method: TwoWayVoiceMobile Is there an authentication method missing? And why only on this second machine? -- Henrique |
From: Henrique M. <da...@ma...> - 2021-07-28 20:57:14
|
I'm trying to run davmail on two very similarly configured Fedora 34 computers. I downloaded a recent .zip from sourceforge, which I unzipped it into a ~/.davmail directory on each machine. To run davmail, I cd into that directory, and run "./davmail davmail.properties". The only difference between the two property files (now), is that one now has a refreshToken (davmail worked). I have enabled SSL pointing to a keystore file, davmail.p12. That file is different between the two machines, one has a LetsEncrypt certificate, the other a DigiCert certificate. On one machine if I run: openssl s_client -showcerts -connect fqdn:port it works fine. I can use this davmail instance and get my email from the remote imap server. On another machine I get an openssl error 140485856540480:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:331: which seems to indicate that davmail is either not accepting tls connections, or is using the tls version. Is this a davmail problem, or maybe different java configuration or security between the machines? Is there a quick way to check this independently of using davmail? -- Henrique |
From: Mickaël G. <mgu...@fr...> - 2021-07-28 17:35:12
|
Indeed Rasmus, using native Outlook desktop clientId is a workaround. However if you have administrator access to target O365 tenant using your own clientId is better to help you track logs. Anyway Gregor please make sure you give your custom clientId the right scopes, see: http://davmail.sourceforge.net/faq.html Note that those scopes are *not* graph API scopes. Regards, |
From: Rasmus L. <jr...@po...> - 2021-07-28 17:16:27
|
Hello Gregor, I battled so much with davmail and MS365 earlier in the year you would not believe it when my employer switched from on-prem Exchange 2010 to 365. I was not able to create my own clientId, but read alot all around Google, and in the end came up with this config, where I believe the clientId is the same as the native outlook id: davmail.defaultDomain= # https://github.com/mguessan/davmail/issues/19 sun.net.http.allowRestrictedHeaders=true log4j.logger.davmail=INFO log4j.logger.httpclient.wire=INFO log4j.logger.org.apache.commons.httpclient=INFO log4j.rootLogger=INFO davmail.logFilePath=~/.davmail.office365.log davmail.logFileSize=4MB davmail.caldavPort=10801 davmail.imapPort=11431 davmail.ldapPort=13891 davmail.popPort= davmail.proxyPort= davmail.smtpPort=10251 davmail.mode=O365Interactive davmail.url=https://outlook.office365.com/EWS/Exchange.asmx davmail.oauth.clientId=d3590ed6-52b3-4102-aeff-aad2292ab01c davmail.oauth.redirectUri=urn:ietf:wg:oauth:2.0:oob davmail.oauth.persistToken=true Take note: I changed the port numbers ... Remember to set your BROWSER='chromium' and edit xdg-open as per https://sourceforge.net/p/davmail/discussion/644057/thread/fb0bcdddfd/?limit=25 to get the saved string after you athenticate using your phone. Rememeber you need OpenJFX https://wiki.openjdk.java.net/display/OpenJFX/Main but this is broken on both FreeBSD and OpenBSD, so you have to stay on ArchLinux or something https://archlinux.org/packages/?q=openjfx Best, Rasmus |
From: Gregor Z. <tel...@gm...> - 2021-07-28 12:51:42
|
Hello, * Gregor Zattler <tel...@gm...> [2021-06-23; 21:41]: > * Gregor Zattler <tel...@gm...> [2021-06-23; 21:25]: >> Hello, I registered an App as Global Admin in MS 365 Azure >> AD amd configured davmail with the resulting Client-Id and >> Tenant-Id. In Azure AD iI gave rights to access email and send email and granted them as admin. I did not know which redirect URI I should configure, I used https://login.microsoftonline.com/common/oauth2/nativeclient because that's mentioned in the davmail faq. Now, when accessing imap://xxx@xxx.xx@localhost:1143 a dialog opens, I enter my work email address, I'm taken to the SSO Service of my employer (all very find) but in the end I get: 2021-07-28 14:46:09,966 INFO [main] davmail - O365Interactive is not compatible with SWT, do not try to create SWT tray 2021-07-28 14:46:10,275 INFO [main] davmail - DavMail Gateway 5.5.1-trunk listening on SMTP port 1025 POP port 1110 IMAP port 1143 CALDAV port 1080 LDAP port 1389 2021-07-28 14:46:29,543 INFO [davmail.imap.ImapServer] davmail.connection - CONNECT - 0:0:0:0:0:0:0:1:51820 2021-07-28 14:46:30,411 INFO [ImapConnection-51820] org.apache.commons.httpclient.auth.AuthChallengeProcessor - basic authentication scheme selected 2021-07-28 14:46:30,413 INFO [ImapConnection-51820] org.apache.commons.httpclient.HttpMethodDirector - No credentials available for BASIC ''@outlook.office365.com:443 2021-07-28 14:46:39,451 WARN [ImapConnection-51820] davmail.exchange.auth.O365Token - refresh token failed javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption. 2021-07-28 14:46:52,241 WARN [ImapConnection-51820] org.apache.commons.httpclient.HttpMethodDirector - Unable to respond to any of these challenges: {bearer=Bearer client_id="00000002-0000-0ff1-ce00-000000000000", trusted_issuers="00000001-0000-0000-c000-000000000000@*", token_types="app_asserted_user_v1 service_asserted_app_v1", authorization_uri="https://login.windows.net/common/oauth2/authorize", error="invalid_token",Basic Realm=""} 2021-07-28 14:46:52,245 INFO [ImapConnection-51820] davmail.connection - FAILED - 0:0:0:0:0:0:0:1:51820 g.z...@iz... 2021-07-28 14:46:52,246 ERROR [ImapConnection-51820] davmail - Authentication failed: invalid user or password davmail.exception.DavMailAuthenticationException: Authentication failed: invalid user or password at davmail.exchange.ews.EwsExchangeSession.checkEndPointUrl(EwsExchangeSession.java:240) at davmail.exchange.ews.EwsExchangeSession.buildSessionInfo(EwsExchangeSession.java:249) at davmail.exchange.ews.EwsExchangeSession.<init>(EwsExchangeSession.java:198) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:186) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:99) at davmail.imap.ImapConnection.run(ImapConnection.java:140) 2021-07-28 14:46:52,714 WARN [ImapConnection-51820] org.apache.commons.httpclient.HttpMethodDirector - Unable to respond to any of these challenges: {bearer=Bearer client_id="00000002-0000-0ff1-ce00-000000000000", trusted_issuers="00000001-0000-0000-c000-000000000000@*", token_types="app_asserted_user_v1 service_asserted_app_v1", authorization_uri="https://login.windows.net/common/oauth2/authorize", error="invalid_token",Basic Realm=""} 2021-07-28 14:46:52,714 INFO [ImapConnection-51820] davmail.connection - FAILED - 0:0:0:0:0:0:0:1:51820 g.z...@iz... 2021-07-28 14:46:52,714 ERROR [ImapConnection-51820] davmail - Authentication failed: invalid user or password davmail.exception.DavMailAuthenticationException: Authentication failed: invalid user or password at davmail.exchange.ews.EwsExchangeSession.checkEndPointUrl(EwsExchangeSession.java:240) at davmail.exchange.ews.EwsExchangeSession.buildSessionInfo(EwsExchangeSession.java:249) at davmail.exchange.ews.EwsExchangeSession.<init>(EwsExchangeSession.java:198) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:186) at davmail.exchange.ExchangeSessionFactory.getInstance(ExchangeSessionFactory.java:99) at davmail.imap.ImapConnection.run(ImapConnection.java:113) 2021-07-28 14:46:54,721 INFO [ImapConnection-51820] davmail.connection - DISCONNECT - 0:0:0:0:0:0:0:1:51820 Is this a problem with the redirect URI? What am I doing wrong? Any ideas how to configure the application in Azure or davmail? Ciao; Gregor -- -... --- .-. . -.. ..--.. ...-.- |