davmail-users Mailing List for DavMail POP/IMAP/SMTP/Caldav to Exchange (Page 2)
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: Mickaël G. <mgu...@fr...> - 2023-02-09 12:36:23
|
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... |
From: Lars B. <la...@la...> - 2023-02-09 12:13:58
|
Hi List! For me, DavMail stopped working this morning. DavMail asked me to reauthorize, e.g. open a link in a browser and insert the link from the address bar back. After doing that, I got `All network interfaces down or host unreachable !` The complete debug log is here: http://lamasti.net/files/davml.log Does anyone have hints on how to solve tthe problem? Thanks in advance, Lars |
From: Henrique M. <da...@ma...> - 2023-02-08 14:15:23
|
> 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 |
From: Rasmus L. <jr...@po...> - 2023-02-08 13:44:24
|
Hear, hear, +1, I for one am crossing my fingers someone knows these answers for Grillo. R |
From: Dan G. <da...@gr...> - 2023-02-08 00:27:14
|
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 -- |
From: Borst, M. <mar...@tu...> - 2023-02-07 17:26:02
|
Hi, we observe sync problems when using DAVMails CalDAV implementation with iOS (iPhone) clients (Exchange 2016 On-Prem). Changes on the iPhone are synched correctly to the calendar in the Exchange, but all changes on the server are not synched to the iPhone calendar. It seems that the problem started with iOS 16.3 update, but I don't know what the actual problem is. Does anybody else experience this? I already opened a bug report for this but got no answer yet. Greetings Markus |
From: Rasmus L. <jr...@po...> - 2023-02-06 15:40:29
|
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. |
From: Marc <Ma...@f1...> - 2023-02-06 09:12:44
|
> > > 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. |
From: Geert S. <sta...@st...> - 2023-02-06 09:07:16
|
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 |
From: Marc <Ma...@f1...> - 2023-02-06 09:01:43
|
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 |
From: Dan G. <da...@gr...> - 2023-02-06 06:15:26
|
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 -- |
From: Zvi B. <zvi...@gm...> - 2023-01-18 13:30:46
|
Hi All, I am new to davmail. Apologies if this is a known issue, but I couldn’t find it discussed. I have davmail running as a server on MacOS 12.6, with MailMate as the client. It works fabulously well. However, I just discovered that when I delete a message, two copies of it are create in the trash folder. The duplicates seem entirely identical, with all the same raw headers. I can also confirm that these are “real” duplicates, and not an artifact of the MailMate display, since they show as two messages in Outlook too. I am using davmail with my company’s Outlook365 using SSO login. I apologize if I’m not using the terms properly. But I use EWS with Manual login as the davmail method. I have not had trouble logging in, etc. (although it can be quite slow when processing a large number of messages). I’ve included my server config (omitting OAUTH stuff) below, in case the issue is obvious. Any help would be appreciated. Thanks, Zvi ```# DavMail settings, see http://davmail.sourceforge.net/ for documentation ############################################################# # Basic settings # Server or workstation mode davmail.server=true # connection mode auto, EWS or WebDav or O365Manual or O365Interactive davmail.mode=O365Manual # base Exchange OWA or EWS url davmail.url=https://outlook.office365.com/EWS/Exchange.asmx # Listener ports davmail.caldavPort= davmail.imapPort=1143 davmail.ldapPort=1389 davmail.popPort= davmail.smtpPort=1025 davmail.exchange.maxConnections=100 ############################################################# # Network settings # Network proxy settings davmail.enableProxy=false davmail.useSystemProxies=false davmail.proxyHost= davmail.proxyPort= davmail.proxyUser= davmail.proxyPassword= # proxy exclude list davmail.noProxyFor= # allow remote connection to DavMail davmail.allowRemote=false # bind server sockets to a specific address davmail.bindAddress= # client connection timeout in seconds - default 300, 0 to disable davmail.clientSoTimeout= # DavMail listeners SSL configuration davmail.ssl.keystoreType= davmail.ssl.keystoreFile= davmail.ssl.keystorePass= davmail.ssl.keyPass= # Accept specified certificate even if invalid according to trust store davmail.server.certificate.hash= # disable SSL for specified listeners davmail.ssl.nosecurecaldav=false davmail.ssl.nosecureimap=false davmail.ssl.nosecureldap=false davmail.ssl.nosecurepop=false davmail.ssl.nosecuresmtp=false # disable update check davmail.disableUpdateCheck=true # Send keepalive character during large folder and messages download davmail.enableKeepalive=true # Message count limit on folder retrieval davmail.folderSizeLimit=0 # Default windows domain for NTLM and basic authentication davmail.defaultDomain= ############################################################# # Caldav settings # override default alarm sound davmail.caldavAlarmSound= # retrieve calendar events not older than 90 days davmail.caldavPastDelay=90 # EWS only: enable server managed meeting notifications davmail.caldavAutoSchedule=true # WebDav only: force event update to trigger ActiveSync clients update davmail.forceActiveSyncUpdate=false ############################################################# # IMAP settings # Delete messages immediately on IMAP STORE \Deleted flag davmail.imapAutoExpunge=true # To enable IDLE support, set a maximum client polling delay in minutes # Clients using IDLE should poll more frequently than this delay davmail.imapIdleDelay=1 # Always reply to IMAP RFC822.SIZE requests with Exchange approximate message size for performance reasons davmail.imapAlwaysApproxMsgSize=true ############################################################# # POP settings # Delete messages on server after 30 days davmail.keepDelay=90 # Delete messages in server sent folder after 90 days davmail.sentKeepDelay=90 # Mark retrieved messages read on server davmail.popMarkReadOnRetr=false ############################################################# # SMTP settings # let Exchange save a copy of sent messages in Sent folder davmail.smtpSaveInSent=true ############################################################# # Loggings settings # log file path, leave empty for default path davmail.logFilePath=/Users/xxx/Library/Logs/DavMail/davmail.log # maximum log file size, use Log4J syntax, set to 0 to use an external rotation mechanism, e.g. logrotate davmail.logFileSize=.5MB # log levels log4j.logger.davmail=WARN log4j.logger.httpclient.wire=WARN log4j.logger.org.apache.commons.httpclient=WARN log4j.rootLogger=WARN ############################################################# # Workstation only settings # smartcard access settings davmail.ssl.pkcs11Config= davmail.ssl.pkcs11Library= # SSL settings for mutual authentication davmail.ssl.clientKeystoreType= davmail.ssl.clientKeystoreFile= davmail.ssl.clientKeystorePass= # disable all balloon notifications davmail.disableGuiNotifications=true # disable tray icon color switch on activity davmail.disableTrayActivitySwitch=false # disable startup balloon notifications davmail.showStartupBanner=true # enable transparent client Kerberos authentication davmail.enableKerberos=false ``` |
From: Robert S. <rob...@tu...> - 2023-01-16 16:32:03
|
Hi, it seems that the Januar 2023 Windows Exchange updates yesterday broke our davmail setup , anyone else with equal problems ? Best Regards Robert -- Robert Schetterer Technischer Angestellter Lehrstuhl für Nachrichtentechnik Technische Universität München D-80290 München Tel. +498928923488 Fax +498928923490 Email: rob...@tu... WWW: http://www.lnt.ei.tum.de |
From: Dan G. <da...@gr...> - 2023-01-11 03:04:36
|
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 -- |
From: Dan G. <da...@gr...> - 2023-01-11 02:52:34
|
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 -- |
From: Ingmar L. <in...@in...> - 2023-01-08 14:59:01
|
Thanks all for your comments! I shall now look forward optimistically to the new DMARC use of my organisation. All best! Ingmar On 07/01/2023 16:38, Geert Stappers wrote: > On Fri, Jan 06, 2023 at 10:13:48PM +0100, Ingmar Lippert wrote: >> On 06/01/2023 21:30, Geert Stappers wrote: >>> On Fri, Jan 06, 2023 at 07:24:52PM +0100, Ingmar Lippert wrote: >>>> Dear all, >>> Hi, >> Hello, >> thanks for your reply! >> >>>> without any expectations, but with optimism, I like to ask, whether DavMail >>>> (a wonderful gateway!) already supports DMARC Compliance or might in the >>>> future > >>> Please spend some effort in explaining >>> which benefits DMARC support bring to DavMail. >> >> here is my use story: >> I use DavMail to connect to my organisation's O365 service. The organisation >> is now approaching implementing its government's policy that is expected to >> force public authorities to use DMARC (which occasioned me to write). >> >> The reasoning of my organisation, which is a public authority, is that >> occasionally, its name is misused as an alleged sender to increase >> credibility and to render phishing attacks more likely successful. >> >> To counter such misuse, so the reasoning by the organisation is, DMARC is to >> be used, which they expect will effectively decrease the number of fake >> emails. >> >> Whether that promise will be realised or not, DavMail as a Third Party >> system with which I access the O365 server, will not be able (as far as I >> understand it) to signal effectively to the recipient that it my message is >> not spam. > > Somehow I do read that > as "the problems are nails and a hamer is the solution" > > The picture at https://davmail.sourceforge.net is still a good picture, > that it lacks where evil can harm it, doesn't matter. > > >> So, with DMARC capacity, in my understanding, DavMail would be able to >> ensure that receiving servers that conduct DMARC checks would validate my >> messages as indeed belonging to my organisation's O365 system. >> >> Ok, I hope this effort helps to provide the relevant context, if not I am >> happy to try to answer more specific questions. And I like to apologise in >> case my understanding is so minimal that all this conext "obviously" does >> not make sense. >> >> Thank you for your reading! > > Thanks for expressing a possible improvement. That I'm farely sure that > DMARC does NOT add value to Davmail, doesn't matter. > > >> Ingmar > > Groeten > Geert Stappers |
From: Geert S. <sta...@st...> - 2023-01-07 15:38:56
|
On Fri, Jan 06, 2023 at 10:13:48PM +0100, Ingmar Lippert wrote: > On 06/01/2023 21:30, Geert Stappers wrote: > > On Fri, Jan 06, 2023 at 07:24:52PM +0100, Ingmar Lippert wrote: > > > Dear all, > > Hi, > Hello, > thanks for your reply! > > > > without any expectations, but with optimism, I like to ask, whether DavMail > > > (a wonderful gateway!) already supports DMARC Compliance or might in the > > > future > > > Please spend some effort in explaining > > which benefits DMARC support bring to DavMail. > > here is my use story: > I use DavMail to connect to my organisation's O365 service. The organisation > is now approaching implementing its government's policy that is expected to > force public authorities to use DMARC (which occasioned me to write). > > The reasoning of my organisation, which is a public authority, is that > occasionally, its name is misused as an alleged sender to increase > credibility and to render phishing attacks more likely successful. > > To counter such misuse, so the reasoning by the organisation is, DMARC is to > be used, which they expect will effectively decrease the number of fake > emails. > > Whether that promise will be realised or not, DavMail as a Third Party > system with which I access the O365 server, will not be able (as far as I > understand it) to signal effectively to the recipient that it my message is > not spam. Somehow I do read that as "the problems are nails and a hamer is the solution" The picture at https://davmail.sourceforge.net is still a good picture, that it lacks where evil can harm it, doesn't matter. > So, with DMARC capacity, in my understanding, DavMail would be able to > ensure that receiving servers that conduct DMARC checks would validate my > messages as indeed belonging to my organisation's O365 system. > > Ok, I hope this effort helps to provide the relevant context, if not I am > happy to try to answer more specific questions. And I like to apologise in > case my understanding is so minimal that all this conext "obviously" does > not make sense. > > Thank you for your reading! Thanks for expressing a possible improvement. That I'm farely sure that DMARC does NOT add value to Davmail, doesn't matter. > Ingmar Groeten Geert Stappers -- Silence is hard to parse |
From: <pe...@ch...> - 2023-01-06 22:32:02
|
>>>>> "Ingmar" == Ingmar Lippert <in...@in...> writes: Ingmar> On 06/01/2023 21:30, Geert Stappers wrote: >> On Fri, Jan 06, 2023 at 07:24:52PM +0100, Ingmar Lippert wrote: >>> Dear all, >> Hi, Ingmar> Hello, thanks for your reply!> >>> without any expectations, but with optimism, I like to ask, >>> whether DavMail (a wonderful gateway!) already supports DMARC >>> Compliance or might in the future > >> Please spend some effort in explaining which benefits DMARC support >> bring to DavMail. Ingmar> here is my use story: I use DavMail to connect to my Ingmar> organisation's O365 service. O365does the DMARC bit after davmail has done its stuff. Davmail is only a way to get your outgoing email to the Exchange server --- the Exchange server adds the DMARC headers. Peter C |
From: Ingmar L. <in...@in...> - 2023-01-06 21:14:06
|
On 06/01/2023 21:30, Geert Stappers wrote: > On Fri, Jan 06, 2023 at 07:24:52PM +0100, Ingmar Lippert wrote: >> Dear all, > > Hi, Hello, thanks for your reply!> >> without any expectations, but with optimism, I like to ask, whether DavMail >> (a wonderful gateway!) already supports DMARC Compliance or might in the >> future > > Please spend some effort in explaining > which benefits DMARC support bring to DavMail. here is my use story: I use DavMail to connect to my organisation's O365 service. The organisation is now approaching implementing its government's policy that is expected to force public authorities to use DMARC (which occasioned me to write). The reasoning of my organisation, which is a public authority, is that occasionally, its name is misused as an alleged sender to increase credibility and to render phishing attacks more likely successful. To counter such misuse, so the reasoning by the organisation is, DMARC is to be used, which they expect will effectively decrease the number of fake emails. Whether that promise will be realised or not, DavMail as a Third Party system with which I access the O365 server, will not be able (as far as I understand it) to signal effectively to the recipient that it my message is not spam. Ok what is that country? Denmark ;) Here are the Danish language claims underlying my organisation's reasoning: https://sikkerdigital.dk/myndighed/tekniske-tiltag/dmarc So, with DMARC capacity, in my understanding, DavMail would be able to ensure that receiving servers that conduct DMARC checks would validate my messages as indeed belonging to my organisation's O365 system. Ok, I hope this effort helps to provide the relevant context, if not I am happy to try to answer more specific questions. And I like to apologise in case my understanding is so minimal that all this conext "obviously" does not make sense. Thank you for your reading! Ingmar |
From: Geert S. <sta...@st...> - 2023-01-06 20:48:44
|
On Fri, Jan 06, 2023 at 07:24:52PM +0100, Ingmar Lippert wrote: > Dear all, Hi, > without any expectations, but with optimism, I like to ask, whether DavMail > (a wonderful gateway!) already supports DMARC Compliance or might in the > future? > Unfortunately, I have no programming experience, > so cannot support any efforts towards this. Please spend some effort in explaining which benefits DMARC support bring to DavMail. > With best wishes for 2023 and for DavMail! Yes, Happy New Year. Groeten Geert Stappers -- Silence is hard to parse |
From: Ingmar L. <in...@in...> - 2023-01-06 19:05:32
|
Dear all, without any expectations, but with optimism, I like to ask, whether DavMail (a wonderful gateway!) already supports DMARC Compliance, or might in the future? Unfortunately, I have no programming experience, so cannot support any efforts towards this. With best wishes for 2023 and for DavMail! Ingmar |
From: Dan G. <da...@gr...> - 2022-11-17 22:54:22
|
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 -- |
From: Edward J. S. <edw...@gm...> - 2022-10-01 22:29:53
|
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 |
From: Edward J. S. <edw...@gm...> - 2022-08-11 21:25:38
|
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 |
From: Dan C. <jd...@uw...> - 2022-08-11 18:13:13
|
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 |