home.social

#davmail — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #davmail, aggregated by home.social.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. @jeff #Davmail is the best option because it’s a POP/IMAP gateway to Exchange, which enables you to use any standard mail tools you want.

    Alternatively, the Evolution mail client has built-in support for MS Exchange.

  7. @jeff #Davmail is the best option because it’s a POP/IMAP gateway to Exchange, which enables you to use any standard mail tools you want.

    Alternatively, the Evolution mail client has built-in support for MS Exchange.

  8. @jeff #Davmail is the best option because it’s a POP/IMAP gateway to Exchange, which enables you to use any standard mail tools you want.

    Alternatively, the Evolution mail client has built-in support for MS Exchange.

  9. @jeff #Davmail is the best option because it’s a POP/IMAP gateway to Exchange, which enables you to use any standard mail tools you want.

    Alternatively, the Evolution mail client has built-in support for MS Exchange.

  10. @simoninireland @jtr The need to register a client ID was what stopped me. I’m currently using #davmail davmail.sourceforge.net, which works fine, but is very slow.

    I recently found this description, which uses Thunderbird’s ID brettpresnell.com/post/email/, but haven’t tried it yet. So I look forward to reading how you did it!

  11. @simoninireland @jtr The need to register a client ID was what stopped me. I’m currently using #davmail davmail.sourceforge.net, which works fine, but is very slow.

    I recently found this description, which uses Thunderbird’s ID brettpresnell.com/post/email/, but haven’t tried it yet. So I look forward to reading how you did it!

  12. @simoninireland @jtr The need to register a client ID was what stopped me. I’m currently using #davmail davmail.sourceforge.net, which works fine, but is very slow.

    I recently found this description, which uses Thunderbird’s ID brettpresnell.com/post/email/, but haven’t tried it yet. So I look forward to reading how you did it!

  13. @simoninireland @jtr The need to register a client ID was what stopped me. I’m currently using #davmail davmail.sourceforge.net, which works fine, but is very slow.

    I recently found this description, which uses Thunderbird’s ID brettpresnell.com/post/email/, but haven’t tried it yet. So I look forward to reading how you did it!

  14. 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…

  15. 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…

  16. 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…

  17. 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…

  18. 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.

    #DAVmail #Exchange

  19. 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.

    #DAVmail #Exchange

  20. 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.

    #DAVmail #Exchange

  21. #DavMail has always been slow (I’m using it with #mbsync to access my work e-mail), but now it has become unbearably slow: what used to take maybe 30 s, now takes 4–5 min. Has anybody else noticed this?

  22. #DavMail has always been slow (I’m using it with #mbsync to access my work e-mail), but now it has become unbearably slow: what used to take maybe 30 s, now takes 4–5 min. Has anybody else noticed this?

  23. #DavMail has always been slow (I’m using it with #mbsync to access my work e-mail), but now it has become unbearably slow: what used to take maybe 30 s, now takes 4–5 min. Has anybody else noticed this?

  24. #DavMail has always been slow (I’m using it with #mbsync to access my work e-mail), but now it has become unbearably slow: what used to take maybe 30 s, now takes 4–5 min. Has anybody else noticed this?

  25. @true_mxp I just switched to for use with .

    But my problem was that my Exchange instance somehow assigned duplicate UIDs to different emails in different folders, so just couldn't download a large part of my mail. And OffineIMAP had some way to handle that more gracefully.

  26. @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.

  27. @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.

  28. 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.

  29. 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.

  30. 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.

  31. @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 …

  32. @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 …

  33. @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 …

  34. @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.

  35. @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.