1
00:00:00,000 --> 00:00:03,680
Welcome back to the Deep Dive. This is the show where we take that stack of

2
00:00:03,680 --> 00:00:04,800
documentation you sent

3
00:00:04,800 --> 00:00:09,310
our way, articles, specs, you name it, and we boil it all down into the knowledge

4
00:00:09,310 --> 00:00:10,560
you actually need.

5
00:00:10,560 --> 00:00:16,070
And our focus today is on a really fascinating piece of open source software called

6
00:00:16,070 --> 00:00:16,960
DavMail.

7
00:00:16,960 --> 00:00:21,020
Our mission here is to explain for a beginner what happens when you try to use a

8
00:00:21,020 --> 00:00:22,080
standard tool

9
00:00:22,080 --> 00:00:26,000
like Thunderbird with a big proprietary system like Microsoft Exchange.

10
00:00:26,000 --> 00:00:30,000
We're going to get into the technical conflicts, the clever translations, and the

11
00:00:30,000 --> 00:00:30,560
pretty urgent

12
00:00:30,560 --> 00:00:34,210
future this software is facing, all based on the DavMail project docs we have in

13
00:00:34,210 --> 00:00:34,880
front of us.

14
00:00:34,880 --> 00:00:38,640
It's all about why a translation layer like this is so necessary.

15
00:00:38,640 --> 00:00:42,880
Before we dive in though, this knowledge extraction is made possible by SameServer.

16
00:00:42,880 --> 00:00:46,800
They handle the hosting of complex software and support your digital transformation.

17
00:00:46,800 --> 00:00:50,640
You can find out more at www.safeserver.de.

18
00:00:50,640 --> 00:00:51,760
All right, let's get into it.

19
00:00:51,760 --> 00:00:54,480
Okay, so let's just start with the core motivation here.

20
00:00:54,480 --> 00:00:59,120
The documentation says, and I love this, that a key goal is to get rid of Outlook.

21
00:00:59,120 --> 00:01:02,560
I mean, that statement alone really captures the whole conflict, doesn't it?

22
00:01:02,560 --> 00:01:05,040
It really does. It gets right to the heart of the matter.

23
00:01:05,040 --> 00:01:09,760
It all comes down to vendor lock-in and, well, proprietary communication.

24
00:01:09,760 --> 00:01:13,120
When a company decides to use Microsoft Exchange,

25
00:01:13,120 --> 00:01:15,520
they're not just choosing an email program.

26
00:01:15,520 --> 00:01:18,000
They're buying into an entire ecosystem.

27
00:01:18,000 --> 00:01:23,440
Exactly. An ecosystem that relies on its own closed private ways of doing things.

28
00:01:23,440 --> 00:01:27,920
It's not using the open languages of the internet for calendars or contacts.

29
00:01:27,920 --> 00:01:30,240
It's using Microsoft's specific protocols.

30
00:01:30,240 --> 00:01:32,560
So the problem isn't just the app on your computer.

31
00:01:32,560 --> 00:01:36,720
It's the actual technical handshake happening between your machine and the server.

32
00:01:36,720 --> 00:01:40,640
That's it. It's like, imagine you speak perfect English, a universal standard,

33
00:01:40,640 --> 00:01:44,960
but the server you need to talk to only accepts requests

34
00:01:44,960 --> 00:01:48,960
in a very, very specific proprietary dialect of Klingon.

35
00:01:48,960 --> 00:01:51,200
A standard email client just wouldn't know what to do.

36
00:01:51,200 --> 00:01:53,360
It'd hit a technical wall immediately.

37
00:01:53,360 --> 00:01:57,340
The server just won't recognize its request for, say, your calendar or your mail

38
00:01:57,340 --> 00:01:57,920
folders.

39
00:01:57,920 --> 00:02:00,080
And this is where DavMail gets really clever.

40
00:02:00,080 --> 00:02:04,560
The documentation says it works by using Outlook Web Access, or OWA.

41
00:02:04,560 --> 00:02:08,160
Why is OWA the key to unlocking this?

42
00:02:08,160 --> 00:02:09,520
It's such a smart approach.

43
00:02:09,520 --> 00:02:13,840
DavMail basically uses Microsoft's own web portal as the bridge.

44
00:02:13,840 --> 00:02:18,960
OWA is designed so that anyone can access their exchange account from a web browser,

45
00:02:18,960 --> 00:02:21,520
which means it provides a known entry point.

46
00:02:21,520 --> 00:02:26,000
Ah, so it doesn't have to crack the deepest, most complex desktop protocols?

47
00:02:26,000 --> 00:02:27,040
Precisely.

48
00:02:27,040 --> 00:02:32,000
It just finds that OWA link and uses that pathway to talk to the exchange server.

49
00:02:32,000 --> 00:02:34,240
It works even if you're outside the company firewall.

50
00:02:34,240 --> 00:02:36,560
So instead of trying to break into the main vault,

51
00:02:36,560 --> 00:02:40,580
DavMail just walks through the public-facing web portal that was already built for

52
00:02:40,580 --> 00:02:41,520
remote access.

53
00:02:41,520 --> 00:02:43,680
And it acts as the interpreter for everything.

54
00:02:43,680 --> 00:02:45,760
Its whole mission is stated so clearly.

55
00:02:45,760 --> 00:02:49,440
Provides standard compliant protocols in front of proprietary exchange.

56
00:02:49,440 --> 00:02:50,880
It's an open source translator.

57
00:02:50,880 --> 00:02:55,600
Okay, let's unpack that translation work because the documentation lists six key

58
00:02:55,600 --> 00:02:56,480
open standards.

59
00:02:56,480 --> 00:03:00,160
And for a beginner, this might just sound like, you know, alphabet soup.

60
00:03:00,160 --> 00:03:05,680
We've got POP, IMP, SMTP, CalDAV, CardDAV, and LDF.

61
00:03:05,680 --> 00:03:08,880
It does sound like a lot, but it's actually a very logical stack.

62
00:03:08,880 --> 00:03:11,680
You can think of DavMail as a specialized switchboard

63
00:03:11,680 --> 00:03:15,200
routing different types of information using these universal standards.

64
00:03:15,200 --> 00:03:18,080
So where do we start? Email, I assume.

65
00:03:18,080 --> 00:03:22,800
Right. The most common one today is IMAP, the Internet Message Access Protocol.

66
00:03:22,800 --> 00:03:28,400
DavMail translates Exchange folders into IMAP so your client can see everything,

67
00:03:28,400 --> 00:03:32,480
not just your inbox, your sent mail, your archive folders, all of it.

68
00:03:32,480 --> 00:03:35,680
That's why your email looks the same on your phone and on your laptop.

69
00:03:35,680 --> 00:03:39,440
Exactly. DavMail makes Exchange just look like a standard IMAP server.

70
00:03:39,440 --> 00:03:41,440
And what about POP? That's an older one, right?

71
00:03:41,440 --> 00:03:44,800
Correct. POP, or Post Office Protocol, is much simpler.

72
00:03:44,800 --> 00:03:48,680
DavMail still supports it, but it typically only lets you download messages from

73
00:03:48,680 --> 00:03:49,520
your inbox.

74
00:03:49,520 --> 00:03:51,280
It's for a more basic setup.

75
00:03:51,280 --> 00:03:55,680
Okay, so IMAP and POP let us pull mail down. How do we send it back out?

76
00:03:55,680 --> 00:03:58,560
That would be SMTP, the Simple Mail Transfer Protocol.

77
00:03:58,560 --> 00:04:00,480
That handles all of your outgoing mail.

78
00:04:00,480 --> 00:04:04,240
So DavMail takes your message, translates it, and hands it off to the Exchange

79
00:04:04,240 --> 00:04:06,000
server using SMTP.

80
00:04:06,000 --> 00:04:08,320
Those three cover all your core email functions.

81
00:04:08,320 --> 00:04:12,080
This is where DavMail becomes more than just an email tool. It integrates

82
00:04:12,080 --> 00:04:13,440
everything else.

83
00:04:13,440 --> 00:04:15,760
Let's talk about calendars and contacts.

84
00:04:15,760 --> 00:04:22,400
Yes. For your calendar, you have CalDAV. This is the open standard for scheduling.

85
00:04:22,400 --> 00:04:26,240
It's what allows an app like Apple's iCal or Thunderbird with the Lightning

86
00:04:26,240 --> 00:04:27,200
extension

87
00:04:27,200 --> 00:04:31,280
to read and write appointments on that Exchange server.

88
00:04:31,280 --> 00:04:34,960
So if CalDAV is for the calendar, I'm guessing Cardav is for contacts.

89
00:04:34,960 --> 00:04:39,360
You got it. Cardav is for synchronizing your personal contacts.

90
00:04:39,360 --> 00:04:43,200
It makes sure that the address book on your local client is always up to date with

91
00:04:43,200 --> 00:04:43,680
what you have

92
00:04:43,680 --> 00:04:48,000
stored in Exchange. That's your personal address book. But in a big company, you

93
00:04:48,000 --> 00:04:48,480
need to be able

94
00:04:48,480 --> 00:04:52,710
to find anyone. You need the global address book. And that is the final piece of

95
00:04:52,710 --> 00:04:53,360
the puzzle.

96
00:04:53,360 --> 00:04:56,880
That's handled by LDAP, the Lightweight Directory Access Protocol.

97
00:04:56,880 --> 00:05:02,480
This is a really powerful feature. DAVmail uses LDAP to give you access to the

98
00:05:02,480 --> 00:05:03,360
entire company

99
00:05:03,360 --> 00:05:07,920
directory. So when you start typing someone's name in the To field... LDAP is what's

100
00:05:07,920 --> 00:05:08,160
looking

101
00:05:08,160 --> 00:05:11,520
that person up in the corporate directory and completing their email address for

102
00:05:11,520 --> 00:05:11,760
you.

103
00:05:11,760 --> 00:05:14,720
Without it, you'd be completely blind to everyone else in your organization.

104
00:05:14,720 --> 00:05:17,920
That one feature is what really makes it feel like a professional,

105
00:05:17,920 --> 00:05:20,880
fully integrated tool, not just some workaround.

106
00:05:20,880 --> 00:05:24,720
It really is. And the way it's built is just as important. The documentation notes

107
00:05:24,720 --> 00:05:25,200
that it's

108
00:05:25,200 --> 00:05:29,760
implemented in Java. Which is key because that's why it should run on any platform,

109
00:05:29,760 --> 00:05:29,920
right?

110
00:05:29,920 --> 00:05:34,320
That's the whole idea behind it. That platform independence is central to its whole

111
00:05:34,320 --> 00:05:35,120
philosophy.

112
00:05:35,680 --> 00:05:40,920
It's tested and released for Windows, for Linux Ubuntu specifically, and for Mac OS

113
00:05:40,920 --> 00:05:41,280
X.

114
00:05:41,280 --> 00:05:43,120
So it's truly cross-platform.

115
00:05:43,120 --> 00:05:47,120
And it even goes beyond the desktop. They mentioned successful tests connecting an

116
00:05:47,120 --> 00:05:47,840
iPhone,

117
00:05:47,840 --> 00:05:50,560
provided DavMail is running on a central server.

118
00:05:50,560 --> 00:05:54,320
So it can be a gateway for an entire organization, not just one person.

119
00:05:54,320 --> 00:05:57,300
Okay, but this is where the documentation gets really surprising. And it gives you

120
00:05:57,300 --> 00:05:57,760
a sense of

121
00:05:57,760 --> 00:06:01,840
just how serious this project is. It's not just a hobbyist project.

122
00:06:01,840 --> 00:06:06,880
No, not at all. This detail is really important. The sources explicitly state that

123
00:06:06,880 --> 00:06:07,760
the CardDAV

124
00:06:07,760 --> 00:06:11,740
implementation, the contact syncing part we just talked about, was sponsored by the

125
00:06:11,740 --> 00:06:12,400
French Defense,

126
00:06:12,400 --> 00:06:15,280
the DGA, through a project called Trusted Bird.

127
00:06:15,280 --> 00:06:20,790
Wait, wait, the French Ministry of Defense, a national defense agency sponsored a

128
00:06:20,790 --> 00:06:20,880
feature

129
00:06:20,880 --> 00:06:24,640
for an open source email gateway. Why would they do that?

130
00:06:24,640 --> 00:06:28,160
It tells you everything you need to know about the strategic importance of this.

131
00:06:28,160 --> 00:06:31,840
For a defense organization, being totally dependent on a single,

132
00:06:31,840 --> 00:06:35,680
closed, proprietary system is a massive systemic risk.

133
00:06:35,680 --> 00:06:38,480
They want to avoid vendor lock-in for security reasons.

134
00:06:38,480 --> 00:06:43,920
Exactly. By funding the CardDAV part, they were ensuring they could use secure,

135
00:06:43,920 --> 00:06:48,480
open source clients that they could audit themselves. It elevates DAV mail from

136
00:06:48,480 --> 00:06:48,720
just

137
00:06:48,720 --> 00:06:54,400
a cool community project to, well, a matter of strategic institutional security.

138
00:06:54,400 --> 00:06:58,010
That really drives the point home. And just to be clear, we're looking at a very

139
00:06:58,010 --> 00:06:58,720
recent version

140
00:06:58,720 --> 00:07:04,720
here, 6.5.1, published October 29th, 2025. This is a very active project.

141
00:07:04,720 --> 00:07:08,880
And it has to be. Because DAV mail is in a constant involuntary race against

142
00:07:08,880 --> 00:07:09,520
Microsoft's

143
00:07:09,520 --> 00:07:15,030
own evolution. The roadmap really lays out the project's existential threat and its

144
00:07:15,030 --> 00:07:15,280
plan for

145
00:07:15,280 --> 00:07:19,260
survival. And that brings us to the most critical thing on that roadmap, the jump

146
00:07:19,260 --> 00:07:20,720
to version 7.0.

147
00:07:20,720 --> 00:07:24,480
This isn't just a regular update, is it? No, it's completely mandatory. It's the

148
00:07:24,480 --> 00:07:25,040
single most

149
00:07:25,040 --> 00:07:29,280
important thing in the entire document. Right now, DAV mail's backend relies on

150
00:07:29,280 --> 00:07:29,600
something

151
00:07:29,600 --> 00:07:32,480
called EWS or Exchange Web Services. And what's the problem?

152
00:07:32,480 --> 00:07:37,440
The problem is Microsoft has deprecated EWS. They're going to remove it entirely.

153
00:07:37,440 --> 00:07:37,760
And when

154
00:07:37,760 --> 00:07:41,440
they flip that switch, the current version of DAV mail will just stop working.

155
00:07:41,440 --> 00:07:42,560
Period.

156
00:07:42,560 --> 00:07:45,760
So this is a total rebuild of the foundation just to keep the lights on.

157
00:07:45,760 --> 00:07:50,800
That's it, exactly. Microsoft is pushing everyone to their new graph API. So DAV

158
00:07:50,800 --> 00:07:51,760
mail team is now

159
00:07:51,760 --> 00:07:59,040
forced to implement a brand new, very complex graph API backend in version 7.0.0

160
00:07:59,040 --> 00:07:59,280
just to

161
00:07:59,280 --> 00:08:02,560
maintain the functionality they already have. That feels like a never-ending game

162
00:08:02,560 --> 00:08:03,520
of whack-a-mole.

163
00:08:03,520 --> 00:08:08,560
If Microsoft keeps moving the goalposts like this, is relying on a gateway like DAV

164
00:08:08,560 --> 00:08:08,880
mail

165
00:08:08,880 --> 00:08:13,040
an inherently risky strategy for a company? That is the core tension. It's a

166
00:08:13,040 --> 00:08:14,240
calculated risk.

167
00:08:14,240 --> 00:08:18,560
The benefit is you get freedom of choice for your clients. But the cost is this

168
00:08:18,560 --> 00:08:19,280
perpetual

169
00:08:19,280 --> 00:08:23,280
maintenance cycle, relying on the DAV mail team to constantly chase whatever

170
00:08:23,280 --> 00:08:24,480
changes Microsoft makes.

171
00:08:24,480 --> 00:08:28,480
And if they can't keep up? The gateway fails. The roadmap does mention some other

172
00:08:28,480 --> 00:08:28,720
things

173
00:08:28,720 --> 00:08:32,880
they're considering, though, once the big graph API transition is done. Yeah, they're

174
00:08:32,880 --> 00:08:33,280
looking at

175
00:08:33,280 --> 00:08:38,800
quality of life improvements. Things like using a new OVBRS endpoint, adding CalDAV

176
00:08:38,800 --> 00:08:39,360
attachments,

177
00:08:39,360 --> 00:08:45,050
better IMAP folder management. But all of that is secondary to the main survival

178
00:08:45,050 --> 00:08:45,920
effort. And it's

179
00:08:45,920 --> 00:08:51,190
also clear about what they are not doing, what's been explicitly ruled out. They've

180
00:08:51,190 --> 00:08:51,680
made some hard

181
00:08:51,680 --> 00:08:55,390
choices. They're not implementing the ActiveSync backend, which a lot of mobile

182
00:08:55,390 --> 00:08:56,160
devices use.

183
00:08:56,160 --> 00:09:01,670
They're also not adding instant messaging or chat. They're staying laser focused on

184
00:09:01,670 --> 00:09:02,320
email,

185
00:09:02,320 --> 00:09:05,930
calendar, and context. It makes sense. You have to focus your resources when you're

186
00:09:05,930 --> 00:09:06,560
facing that kind

187
00:09:06,560 --> 00:09:11,520
of mandatory rebuild. You absolutely do. It really shows that open source freedom

188
00:09:11,520 --> 00:09:12,720
comes with the price

189
00:09:12,720 --> 00:09:17,220
of constant vigilance. So let's wrap this up. For you, the listener, I think the

190
00:09:17,220 --> 00:09:18,320
core takeaway here

191
00:09:18,320 --> 00:09:22,710
is that DavMail is this crucial open source translator. It gives you freedom,

192
00:09:22,710 --> 00:09:23,120
letting you

193
00:09:23,120 --> 00:09:26,750
use the client you want in the lockdown world of Microsoft Exchange. But that

194
00:09:26,750 --> 00:09:28,160
freedom isn't free.

195
00:09:28,160 --> 00:09:32,620
It has to be constantly defended through these huge technical efforts, like the

196
00:09:32,620 --> 00:09:33,360
mandatory shift

197
00:09:33,360 --> 00:09:36,970
to the graph API. It's a constant battle. Which leaves you with a really important

198
00:09:36,970 --> 00:09:37,280
question to

199
00:09:37,280 --> 00:09:42,120
think about. If adopting this new API means DavMail is always playing on Microsoft's

200
00:09:42,120 --> 00:09:43,040
home turf

201
00:09:43,040 --> 00:09:47,410
by Microsoft's rules, what happens if Microsoft decides to change those rules every

202
00:09:47,410 --> 00:09:48,240
six months?

203
00:09:48,240 --> 00:09:53,120
Can an open source project ever guarantee long-term stability when faced with that

204
00:09:53,120 --> 00:09:53,280
kind

205
00:09:53,280 --> 00:09:56,800
of mandated obsolescence? A question of digital sovereignty, really. That's a

206
00:09:56,800 --> 00:09:57,520
perfect thought to

207
00:09:57,520 --> 00:10:01,680
end on. This deep dive was supported by Safe Server, helping you with hosting and

208
00:10:01,680 --> 00:10:02,000
digital

209
00:10:02,000 --> 00:10:07,840
transformation solutions. Learn more at www.safeserver.de. We hope this gives you a

210
00:10:07,840 --> 00:10:09,280
shortcut to being well informed.