#davmail — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #davmail, aggregated by home.social.
-
DavMail 6.5 open-source exchange gateway enhances Office 365 login security and refines Linux RPM packages.
https://linuxiac.com/davmail-6-5-exchange-gateway-brings-interactive-office-365-login/ -
-
How nice to finally have #Microsoft 365 email within #mu4e using #msmtp and #davmail. When is someone going to make a #emacs linux OS and boot directly off the kernel like you could do with lilo way back when.
-
How nice to finally have #Microsoft 365 email within #mu4e using #msmtp and #davmail. When is someone going to make a #emacs linux OS and boot directly off the kernel like you could do with lilo way back when.
-
How nice to finally have #Microsoft 365 email within #mu4e using #msmtp and #davmail. When is someone going to make a #emacs linux OS and boot directly off the kernel like you could do with lilo way back when.
-
How nice to finally have #Microsoft 365 email within #mu4e using #msmtp and #davmail. When is someone going to make a #emacs linux OS and boot directly off the kernel like you could do with lilo way back when.
-
How nice to finally have #Microsoft 365 email within #mu4e using #msmtp and #davmail. When is someone going to make a #emacs linux OS and boot directly off the kernel like you could do with lilo way back when.
-
@simoninireland @jtr The need to register a client ID was what stopped me. I’m currently using #davmail https://davmail.sourceforge.net, which works fine, but is very slow.
I recently found this description, which uses Thunderbird’s ID https://brettpresnell.com/post/email/, but haven’t tried it yet. So I look forward to reading how you did it!
-
Compared to using #DavMail to access a #MicrosoftExchange server, using #Kermit to fetch my mail over a dialup line a quarter century ago was lightning fast.
A #UUCP interface to Exchange might be more appropriate…
-
CW: geek, davmail+Exchange
So the logic for davmail Tasks synchronisation with Exchange, when subscribed to a personal and a group calendar, seems to be:
1. client creates a task in personal calendar, and syncs it to the server
2. on the next sync, client receives a copy of the task, apparently in the group calendar!
3. but not really, server side. Whew!
4. removing either on the client removes "both", after more syncs.
-
@true_mxp I just switched to #OfflineIMAP for use with #DavMail.
But my problem was that my Exchange instance somehow assigned duplicate UIDs to different emails in different folders, so #mbsync just couldn't download a large part of my mail. And OffineIMAP had some way to handle that more gracefully.
-
Update on my experiences with #DavMail and #mbsync: after a lot of experimentation, it turned out that the problem of unsynced messages occurred with messages above a certain size. Apparently DavMail behaves in a way that differs from other #IMAP servers and that mbsync doesn’t handle well.
I’ve massively increased the size of buf in src/socket.h (from 100000 to 5000000), and this seems to have solved the problem. The real problem is probably in the protocol handling, but this is at least a workaround that allows me to continue reading mail with #mu4e in #Emacs.
-
@moritz Habe #davmail auf dem MacBook laufen, und da hat es sich gemeldet, als das token abgelaufen ist. Zumindest der teil sollte funktionieren… Mein problem ist vor allem, dass es überhaupt nicht mit #mbsync harmonisiert. Jetzt ist es ein paar tage ohne fehlermeldung gelaufen, aber schon jammert mbsync wieder über volle input buffers :-/ Immerhin fehlen anscheinend noch keine nachrichten … Wenn es zuverlässig funktionieren würde, wäre es auch nicht so schlimm, dass es lahm ist …
-
@Cnoceda @ericsfraga Unfortunately, my experience so far with #davmail, #mbsync, and #MicrosoftExchange: it’s hopeless.
I’ve tried both mbsync 1.4.4 and the current git version. I thought I had it working when it finally didn’t stop with some error—but then I discovered that hundreds of messages were never synchronized.
This is a disaster.
-
Since I’ve just gotten another reminder that #OAuth2 will be required to access UNIL’s #MicrosoftExchange server, I decided to give it another try.
This time I let #mbsync sync to a new, empty directory. It ran into the same problem as last time:
IMAP error: unable to parse INTERNALDATE format
Apparently something is different with #davmail that makes mbsync think that lines in the body that start with “Date:” are headers… The solution seems to be to turn off the “CopyArrivalDate” option in the mbsync configuration (which is actually the default value).
The first run is not finished, but so far, things are looking good… Phew!
-
It seems that some component (#DavMail?) considers *all* lines starting with “Date:” as message dates, but of course with all the TOFU, there are tons of matching lines—but the rest isn’t conformant. I’ve already fixed those that follow some pattern, but there are tons that are completely off (like “Date: 3 f=C3=A9vrier 2022 =C3=A0 11:23:21 UTC+1”).
Of course, all of this could have been avoided by not migrating to #Microsoft hell and its oh-so-modern authentication.
-
@moritz I agree. I precisely needed the VPN yesterday because I was struggling to set up #DavMail so that I can continue to access my mail with a reasonable client.
#Microsoft has an extremely bad track record for… basically everything. One may also wonder how #sustainable it is to outsource the whole IT to a foreign company. -
Interesting. I have heard of #neomutt, but what is #secrettool and #davmail?
I believe I use gnome-keyring to unlock my GnuPG key pair, but I'm not sure.
