1
00:00:00,000 --> 00:00:05,520
Welcome back to The Deep Dive. Today we are wrestling with a legendary beast of

2
00:00:05,520 --> 00:00:08,000
internet infrastructure, email.

3
00:00:08,000 --> 00:00:08,600
Oh, yeah.

4
00:00:08,600 --> 00:00:13,480
More specifically, we've taken a stack of sources that tackle one of the most notoriously

5
00:00:13,480 --> 00:00:15,200
complex tasks in the tech world,

6
00:00:15,200 --> 00:00:19,630
self-hosting your own email, and we found a surprising solution that makes it

7
00:00:19,630 --> 00:00:20,360
accessible.

8
00:00:20,360 --> 00:00:24,790
You know, for anyone who has ever even tried to run a professional-grade mail

9
00:00:24,790 --> 00:00:27,840
server by hand, you know, it's not just one program.

10
00:00:27,840 --> 00:00:28,160
Yeah.

11
00:00:28,160 --> 00:00:32,880
It's a whole integrated system of, I don't know, half a dozen or more separate

12
00:00:32,880 --> 00:00:33,600
applications.

13
00:00:33,600 --> 00:00:33,880
Right.

14
00:00:33,880 --> 00:00:37,480
I mean, you're talking about manually stitching together software for sending,

15
00:00:37,480 --> 00:00:40,240
receiving, spam, filtering, virus checking, web access.

16
00:00:40,240 --> 00:00:42,800
It just becomes this monster.

17
00:00:42,800 --> 00:00:47,230
It truly becomes a Frankenstein's monster of dependency conflicts and just endless

18
00:00:47,230 --> 00:00:48,440
configuration files.

19
00:00:48,440 --> 00:00:49,320
It's a nightmare.

20
00:00:49,320 --> 00:00:50,440
It sounds like a total nightmare.

21
00:00:50,440 --> 00:00:55,360
And that's why our mission today is to deep dive into Mailcow, Dockerized.

22
00:00:55,360 --> 00:00:58,280
This tool promises to tame that complexity.

23
00:00:58,280 --> 00:01:01,450
We're going to explain what this open source suite is, why it uses the specific

24
00:01:01,450 --> 00:01:05,520
technology it does, and what crucial components it brings together.

25
00:01:05,520 --> 00:01:08,880
And we're going to make it accessible to you, even if you're an absolute beginner.

26
00:01:08,880 --> 00:01:10,000
Exactly.

27
00:01:10,000 --> 00:01:15,150
The core concept is, I have to say, wonderfully elegant, especially for a piece of

28
00:01:15,150 --> 00:01:16,440
heavy infrastructure.

29
00:01:16,440 --> 00:01:19,640
It's all represented by this charming little equation.

30
00:01:19,640 --> 00:01:20,920
The cow plus the whale.

31
00:01:20,920 --> 00:01:23,480
The cow plus a whale equals love.

32
00:01:23,480 --> 00:01:27,600
The cow is male cow, obviously, the software suite itself, and the whale, that's

33
00:01:27,600 --> 00:01:28,720
the logo for Docker.

34
00:01:28,720 --> 00:01:32,120
The containerization technology that acts as the delivery vehicle.

35
00:01:32,120 --> 00:01:36,640
It's a very, I mean, a very succinct way of saying, we've taken the most difficult

36
00:01:36,640 --> 00:01:38,560
server task out there,

37
00:01:38,560 --> 00:01:42,990
male management, and packaged it using the simplest, most reproducible technology

38
00:01:42,990 --> 00:01:43,600
available today.

39
00:01:43,600 --> 00:01:44,960
It just takes the pain away.

40
00:01:44,960 --> 00:01:46,280
It absolutely does.

41
00:01:46,280 --> 00:01:49,960
And before we start decoding that cow and that whale, we should probably thank our

42
00:01:49,960 --> 00:01:52,400
supporter for making this deep dive possible.

43
00:01:52,400 --> 00:01:54,320
We should.

44
00:01:54,320 --> 00:01:56,840
This deep dive is brought to you by Safe Server.

45
00:01:56,840 --> 00:02:01,430
Safe Server handles the hosting of powerful open source software, just like Mail

46
00:02:01,430 --> 00:02:04,480
Cow, and supports your digital transformation journey.

47
00:02:04,480 --> 00:02:07,960
They make sure your infrastructure keeps pace with your ambition.

48
00:02:07,960 --> 00:02:13,440
You can find more information and support at www.safeserver.de.

49
00:02:13,440 --> 00:02:15,040
OK, let's unpack this.

50
00:02:15,040 --> 00:02:20,890
We've established a cute equation, but for someone coming in cold, what exactly is

51
00:02:20,890 --> 00:02:22,640
Mail Cow Dockerized?

52
00:02:22,640 --> 00:02:25,880
What problem does it solve right out of the box?

53
00:02:25,880 --> 00:02:28,520
Simply put, it's an all-in-one mail server suite.

54
00:02:28,520 --> 00:02:34,280
It's open source, released under the GNU general public license version three.

55
00:02:34,280 --> 00:02:36,720
So you get all that transparency and community oversight.

56
00:02:36,720 --> 00:02:38,120
And the Dockerized part?

57
00:02:38,120 --> 00:02:40,440
The Dockerized part is the fundamental innovation.

58
00:02:40,440 --> 00:02:44,080
It's what solves that Frankenstein's monster problem we were just talking about.

59
00:02:44,080 --> 00:02:46,920
Let's focus on that for a second, because that's a magic trick we really need to

60
00:02:46,920 --> 00:02:47,320
explain

61
00:02:47,320 --> 00:02:48,320
for our audience.

62
00:02:48,320 --> 00:02:50,560
What does using Docker actually mean for the administrator?

63
00:02:50,560 --> 00:02:51,840
OK, think of it this way.

64
00:02:51,840 --> 00:02:56,270
Traditionally, if you install, say, Postfix, you need a specific version of a

65
00:02:56,270 --> 00:02:56,800
library.

66
00:02:56,800 --> 00:03:01,220
Then if you install rspammed, it might need a conflicting version of that same

67
00:03:01,220 --> 00:03:01,560
library.

68
00:03:01,560 --> 00:03:02,920
And then everything breaks.

69
00:03:02,920 --> 00:03:03,920
Everything breaks.

70
00:03:03,920 --> 00:03:09,070
But Docker solves this by bundling each application, Postfix, rspammed, dubcot,

71
00:03:09,070 --> 00:03:10,340
into its own separate

72
00:03:10,340 --> 00:03:13,000
isolated environment, a container.

73
00:03:13,000 --> 00:03:19,530
So if Postfix needs version 1.0 of a library and dubcot needs version 2.0, they can

74
00:03:19,530 --> 00:03:20,000
just

75
00:03:20,000 --> 00:03:23,000
peacefully coexist because they're sealed off from each other.

76
00:03:23,000 --> 00:03:24,000
Precisely.

77
00:03:24,000 --> 00:03:25,960
They're self-contained ecosystems.

78
00:03:25,960 --> 00:03:28,280
And this means the components are portable.

79
00:03:28,280 --> 00:03:31,120
They don't fight over dependencies on your operating system.

80
00:03:31,120 --> 00:03:32,120
And this is crucial.

81
00:03:32,120 --> 00:03:34,400
They are incredibly easy to update.

82
00:03:34,400 --> 00:03:38,860
So instead of manually updating six different programs and just praying nothing

83
00:03:38,860 --> 00:03:39,320
breaks.

84
00:03:39,320 --> 00:03:40,320
Right.

85
00:03:40,320 --> 00:03:44,220
They can essentially just pull a new pre-tested version of the entire MailCow

86
00:03:44,220 --> 00:03:44,800
engine.

87
00:03:44,800 --> 00:03:47,360
It's no wonder this project has such strong community adoption.

88
00:03:47,360 --> 00:03:53,780
I mean, the GitHub source shows 11.9 thousand stars and 1.6 thousand forks.

89
00:03:53,780 --> 00:03:54,860
That's a lot of interest.

90
00:03:54,860 --> 00:03:58,100
That level of professional interest really confirms that they solved a fundamental

91
00:03:58,100 --> 00:03:58,360
pain

92
00:03:58,360 --> 00:03:59,360
point.

93
00:03:59,360 --> 00:04:00,360
It does.

94
00:04:00,360 --> 00:04:03,160
And you know, this isn't just a weekend hobby project.

95
00:04:03,160 --> 00:04:07,760
It originated from the work of Andre, or at Andre Ashi, and it's actively managed

96
00:04:07,760 --> 00:04:07,900
and

97
00:04:07,900 --> 00:04:10,960
maintained by the infrastructure company GMBH.

98
00:04:10,960 --> 00:04:15,480
So you get that blend of robust professional maintenance with that open source ethos.

99
00:04:15,480 --> 00:04:16,480
That's it.

100
00:04:16,480 --> 00:04:20,040
Okay, so now that we know what MailCow is and how it's packaged using containers,

101
00:04:20,040 --> 00:04:20,040
let's

102
00:04:20,040 --> 00:04:21,760
look inside the engine.

103
00:04:21,760 --> 00:04:26,640
Since it's an all-in-one suite, it must replace every piece of that old, complex

104
00:04:26,640 --> 00:04:27,560
mail server

105
00:04:27,560 --> 00:04:28,640
puzzle.

106
00:04:28,640 --> 00:04:30,440
What are those essential components?

107
00:04:30,440 --> 00:04:33,560
This is where the scope of the project really comes into focus.

108
00:04:33,560 --> 00:04:37,990
MailCow incorporates a pretty comprehensive stack, and we can break it down by

109
00:04:37,990 --> 00:04:38,640
function.

110
00:04:38,640 --> 00:04:39,640
Okay.

111
00:04:39,640 --> 00:04:42,400
Let's start with the absolute basics of email transport.

112
00:04:42,400 --> 00:04:44,720
The actual act of sending and receiving.

113
00:04:44,720 --> 00:04:45,720
Right.

114
00:04:45,720 --> 00:04:48,240
For sending mail, MailCow uses Postfix.

115
00:04:48,240 --> 00:04:51,320
Think of Postfix as the post office truck, you know.

116
00:04:51,320 --> 00:04:54,840
It implements the SMTP protocol and gets your email from point A to point B.

117
00:04:54,840 --> 00:04:56,000
And for receiving.

118
00:04:56,000 --> 00:04:58,980
For receiving and storing mail, it uses DoveCot.

119
00:04:58,980 --> 00:05:01,360
DoveCot is like the sophisticated filing cabinet.

120
00:05:01,360 --> 00:05:06,410
It handles IMAP and POP3, allowing your client, like your phone or desktop app, to

121
00:05:06,410 --> 00:05:06,800
access

122
00:05:06,800 --> 00:05:08,400
and store all those messages.

123
00:05:08,400 --> 00:05:11,520
Okay, so we've got the delivery truck and the filing cabinet.

124
00:05:11,520 --> 00:05:15,880
But I mean, modern email is utterly unusable without defense.

125
00:05:15,880 --> 00:05:18,200
What about spam and malware?

126
00:05:18,200 --> 00:05:20,280
That's probably the most complex layer.

127
00:05:20,280 --> 00:05:23,080
And MailCow uses layered security here.

128
00:05:23,080 --> 00:05:26,120
For advanced spam and filtering, it integrates spam.

129
00:05:26,120 --> 00:05:27,120
That's a modern tool, right?

130
00:05:27,120 --> 00:05:28,120
Yeah.

131
00:05:28,120 --> 00:05:31,640
It's a modern spam filter that uses sophisticated rules, neural networks, all that

132
00:05:31,640 --> 00:05:32,320
good stuff.

133
00:05:32,320 --> 00:05:35,680
And for mandatory antivirus protection, it includes Clamov.

134
00:05:35,680 --> 00:05:40,110
Our sources also mention Olify, which is often used to detect malicious macros in

135
00:05:40,110 --> 00:05:40,400
documents.

136
00:05:40,400 --> 00:05:44,040
So you can see their layering protection to catch different kinds of threats.

137
00:05:44,040 --> 00:05:47,210
So we have the mail flow, we have the defense system, but I still need a user

138
00:05:47,210 --> 00:05:47,880
interface,

139
00:05:47,880 --> 00:05:48,880
right?

140
00:05:48,880 --> 00:05:51,400
I need to check my mail from a browser, manage my calendar.

141
00:05:51,400 --> 00:05:52,400
Exactly.

142
00:05:52,400 --> 00:05:55,680
For web access and all those critical groupware features, calendars, contacts,

143
00:05:55,680 --> 00:05:56,680
tasks, it includes

144
00:05:56,680 --> 00:05:57,680
SoGo.

145
00:05:57,680 --> 00:05:59,800
It gives you a polished web interface instantly.

146
00:05:59,800 --> 00:06:02,600
And then there are the utilities, the unsung heroes.

147
00:06:02,600 --> 00:06:04,440
The unsung heroes, precisely.

148
00:06:04,440 --> 00:06:09,000
You need Docker Compose to orchestrate all those containers, making sure they start,

149
00:06:09,000 --> 00:06:10,340
stop, and communicate correctly.

150
00:06:10,340 --> 00:06:13,440
And the last one is probably the most important for security.

151
00:06:13,440 --> 00:06:14,440
Oh yeah.

152
00:06:14,440 --> 00:06:15,440
ACME.

153
00:06:15,440 --> 00:06:20,120
ACME automates the management of your SSLTLS certificates.

154
00:06:20,120 --> 00:06:24,560
If your certificates expire, your mail stops working securely, and that is a

155
00:06:24,560 --> 00:06:25,880
massive headache.

156
00:06:25,880 --> 00:06:27,960
MailCal just automates this entirely.

157
00:06:27,960 --> 00:06:31,120
And that is the ultimate value proposition for you, the listener.

158
00:06:31,120 --> 00:06:35,550
You are spared the headache of installing, configuring, and connecting seven

159
00:06:35,550 --> 00:06:36,000
distinct

160
00:06:36,000 --> 00:06:37,300
complex programs.

161
00:06:37,300 --> 00:06:40,000
And hoping they all speak to each other perfectly and securely.

162
00:06:40,000 --> 00:06:41,000
Yes.

163
00:06:41,000 --> 00:06:44,060
MailCal just delivers a fully integrated, pre-calibrated engine.

164
00:06:44,060 --> 00:06:46,840
It's the difference between buying a high-performance engine ready to drop into

165
00:06:46,840 --> 00:06:48,200
your car versus

166
00:06:48,200 --> 00:06:52,280
buying every single nut, bolt, piston, and carburetor separately and just hoping

167
00:06:52,280 --> 00:06:52,520
they

168
00:06:52,520 --> 00:06:53,520
fit together.

169
00:06:53,520 --> 00:06:54,520
A much better proposition.

170
00:06:54,520 --> 00:06:57,400
Now, let's talk about the project's pulse.

171
00:06:57,400 --> 00:06:58,800
This isn't static software.

172
00:06:58,800 --> 00:07:02,820
The source assurance is highly active with these fun-themed update names.

173
00:07:02,820 --> 00:07:09,640
Yeah, like Moosember 2025, October 2025, and February 2025.

174
00:07:09,640 --> 00:07:13,700
What does that steady stream of updates tell us about the quality of the product?

175
00:07:13,700 --> 00:07:18,680
It tells us they're committed to both continuous improvement and, crucially, to

176
00:07:18,680 --> 00:07:19,560
security.

177
00:07:19,560 --> 00:07:24,240
The blog entries we review demonstrate a really immediate response culture.

178
00:07:24,240 --> 00:07:28,900
For instance, the Muli update in July 2025 was a focused security patch.

179
00:07:28,900 --> 00:07:30,640
So they prioritize vulnerabilities.

180
00:07:30,640 --> 00:07:32,880
They prioritize them rapidly when they're discovered.

181
00:07:32,880 --> 00:07:37,310
Can you walk us through a specific, recent security fix, something that shows their

182
00:07:37,310 --> 00:07:37,500
attention

183
00:07:37,500 --> 00:07:38,500
to detail?

184
00:07:38,500 --> 00:07:39,500
Absolutely.

185
00:07:39,500 --> 00:07:43,930
One critical fix they highlighted in the February 2025 update targeted potential

186
00:07:43,930 --> 00:07:44,440
vulnerability

187
00:07:44,440 --> 00:07:47,920
in how DoveCot was interacting with the firewall system, NetFilter.

188
00:07:47,920 --> 00:07:52,350
Previously, if someone was trying to, say, brute force a password, DoveCot

189
00:07:52,350 --> 00:07:52,840
sometimes

190
00:07:52,840 --> 00:07:56,140
allowed multiple failed login attempts within a single session without being

191
00:07:56,140 --> 00:07:57,120
properly detected.

192
00:07:57,120 --> 00:07:58,360
So the firewall would miss it.

193
00:07:58,360 --> 00:07:59,360
Exactly.

194
00:07:59,360 --> 00:08:02,320
The attack could look like one single failed attempt when it was actually hundreds.

195
00:08:02,320 --> 00:08:06,200
That loophole has now been closed, which is just foundational security work.

196
00:08:06,200 --> 00:08:07,200
What about modernization?

197
00:08:07,200 --> 00:08:10,200
I mean, email security standards are constantly shifting.

198
00:08:10,200 --> 00:08:11,760
They're definitely keeping up.

199
00:08:11,760 --> 00:08:17,840
A major step was detailed in the Mutember update 2025, the introduction of MTA STS

200
00:08:17,840 --> 00:08:18,440
support.

201
00:08:18,440 --> 00:08:19,440
Okay.

202
00:08:19,440 --> 00:08:20,440
That sounds incredibly technical.

203
00:08:20,440 --> 00:08:21,920
What's the simple translation?

204
00:08:21,920 --> 00:08:24,760
It's a mechanism that forces secure delivery.

205
00:08:24,760 --> 00:08:29,190
It basically tells other mail servers, do not talk to me unless you use a secure

206
00:08:29,190 --> 00:08:29,540
encrypted

207
00:08:29,540 --> 00:08:30,540
connection.

208
00:08:30,540 --> 00:08:33,560
It prevents eavesdropping and guarantees encrypted delivery.

209
00:08:33,560 --> 00:08:36,240
Which is pretty much a requirement now for professional email.

210
00:08:36,240 --> 00:08:37,240
It's a standard requirement.

211
00:08:37,240 --> 00:08:38,240
Yeah.

212
00:08:38,240 --> 00:08:42,660
And they also mentioned ongoing work to roll out external authentication, like LDIP

213
00:08:42,660 --> 00:08:42,760
and

214
00:08:42,760 --> 00:08:47,440
OIDC, allowing Mailcow to integrate into larger company identity systems.

215
00:08:47,440 --> 00:08:50,360
We also noticed significant infrastructural changes.

216
00:08:50,360 --> 00:08:53,600
They're swapping out core parts inside the engine itself.

217
00:08:53,600 --> 00:08:55,620
And that's the beauty of containerization.

218
00:08:55,620 --> 00:08:59,600
They updated core dependencies like RSPAM, SOGO, MariaDB.

219
00:08:59,600 --> 00:09:03,030
This constant refresh is vital for getting the latest security patches and

220
00:09:03,030 --> 00:09:03,640
performance

221
00:09:03,640 --> 00:09:04,640
boosts.

222
00:09:04,640 --> 00:09:08,400
And the admin doesn't have to lift a finger for these massive component swaps.

223
00:09:08,400 --> 00:09:09,560
Not a finger.

224
00:09:09,560 --> 00:09:12,480
And it even extends to quality of life improvements.

225
00:09:12,480 --> 00:09:17,760
I saw they fixed a tiny typo in an update script that was failing for some users.

226
00:09:17,760 --> 00:09:19,600
That's an admin nightmare saved right there.

227
00:09:19,600 --> 00:09:20,680
It is.

228
00:09:20,680 --> 00:09:23,280
And a massive win for beginners.

229
00:09:23,280 --> 00:09:28,120
They made enabling HTTPS redirect the default setting for new setups.

230
00:09:28,120 --> 00:09:29,200
That's a great change.

231
00:09:29,200 --> 00:09:33,630
That small default saves countless new administrators the headache of debugging why

232
00:09:33,630 --> 00:09:34,360
their web interface

233
00:09:34,360 --> 00:09:36,600
is only loading insecurely.

234
00:09:36,600 --> 00:09:39,080
It shows they're anticipating user error.

235
00:09:39,080 --> 00:09:43,160
Given this strong professional backing, what are the support options if you run

236
00:09:43,160 --> 00:09:43,560
into a

237
00:09:43,560 --> 00:09:44,560
tricky issue?

238
00:09:44,560 --> 00:09:45,840
Well, there are three main layers.

239
00:09:45,840 --> 00:09:48,480
First, there's comprehensive official documentation.

240
00:09:48,480 --> 00:09:52,680
Second, a vibrant community, including active telegram channels.

241
00:09:52,680 --> 00:09:56,320
They even have off-topic channels, which shows a healthy social side.

242
00:09:56,320 --> 00:09:57,320
They do.

243
00:09:57,320 --> 00:10:01,120
And third, for serious or professional users, they offer paid support options

244
00:10:01,120 --> 00:10:02,680
through ServerCal,

245
00:10:02,680 --> 00:10:05,680
like professional contracts or a one-time service assurance level.

246
00:10:05,680 --> 00:10:08,820
So by supporting the company, you're directly investing in the development of the

247
00:10:08,820 --> 00:10:09,440
open source

248
00:10:09,440 --> 00:10:10,440
suite.

249
00:10:10,440 --> 00:10:11,440
That's the idea.

250
00:10:11,440 --> 00:10:15,870
OK, now we get to the real deep dive nuggets, the specific details that show the

251
00:10:15,870 --> 00:10:16,360
level of

252
00:10:16,360 --> 00:10:18,600
foresight this team has.

253
00:10:18,600 --> 00:10:23,030
We noticed guidance for admins upgrading their operating system, Debian, that

254
00:10:23,030 --> 00:10:23,840
addresses software

255
00:10:23,840 --> 00:10:25,680
MailCow doesn't even use.

256
00:10:25,680 --> 00:10:28,980
That's one of the most compelling pieces of information we found.

257
00:10:28,980 --> 00:10:32,820
In their quick guide for upgrading Debian 12 to 13, they specifically warned

258
00:10:32,820 --> 00:10:33,640
administrators

259
00:10:33,640 --> 00:10:37,800
about a pitfall involving a competing mail server software called Exum.

260
00:10:37,800 --> 00:10:40,240
Wait, MailCow uses Postfix.

261
00:10:40,240 --> 00:10:42,080
Why are they warning about Exum?

262
00:10:42,080 --> 00:10:46,120
Because the MailCow team knows that real-world server environments are messy.

263
00:10:46,120 --> 00:10:50,970
An admin might have Exum installed for other legacy reasons, or it might have been

264
00:10:50,970 --> 00:10:51,320
installed

265
00:10:51,320 --> 00:10:52,640
by default.

266
00:10:52,640 --> 00:10:56,440
So the MailCow team proactively warns their users about conflicts that aren't even

267
00:10:56,440 --> 00:10:56,800
their

268
00:10:56,800 --> 00:10:57,800
fault.

269
00:10:57,800 --> 00:10:58,800
That is incredible.

270
00:10:58,800 --> 00:11:02,000
They're looking at the admin's entire environment, anticipating problems external

271
00:11:02,000 --> 00:11:02,600
to their own

272
00:11:02,600 --> 00:11:03,600
product?

273
00:11:03,600 --> 00:11:07,360
That, more than anything, demonstrates professional, comprehensive support.

274
00:11:07,360 --> 00:11:09,680
That's the definition of going above and beyond.

275
00:11:09,680 --> 00:11:13,800
And that attention to detail also extends to hardening their own code, right?

276
00:11:13,800 --> 00:11:15,480
Right down to the cookies.

277
00:11:15,480 --> 00:11:16,480
Exactly.

278
00:11:16,480 --> 00:11:20,440
The changelogs show a focus on modern security best practices.

279
00:11:20,440 --> 00:11:24,500
For instance, they updated the PHP session cookie to set the same site attribute to

280
00:11:24,500 --> 00:11:24,960
lax.

281
00:11:24,960 --> 00:11:27,520
A small but important change against certain attacks.

282
00:11:27,520 --> 00:11:29,360
A very important one.

283
00:11:29,360 --> 00:11:33,090
And they also standardized the name of that cookie to MCHesed and improved the

284
00:11:33,090 --> 00:11:33,660
clarity

285
00:11:33,660 --> 00:11:39,950
of the LDAP SSLTLS settings, making it much harder to accidentally misconfigure

286
00:11:39,950 --> 00:11:40,640
secure

287
00:11:40,640 --> 00:11:41,640
connections.

288
00:11:41,640 --> 00:11:46,060
These small internal security fixes are what build trust in a platform that's

289
00:11:46,060 --> 00:11:46,200
handling

290
00:11:46,200 --> 00:11:47,940
mission-critical communication.

291
00:11:47,940 --> 00:11:48,940
They are.

292
00:11:48,940 --> 00:11:52,720
So if we zoom out, what have we learned about self-hosting email in the modern era?

293
00:11:52,720 --> 00:11:57,150
I think we've learned that MailCal provides a simplified, actively maintained, and

294
00:11:57,150 --> 00:11:57,320
fully

295
00:11:57,320 --> 00:12:00,260
featured approach to running your own mail server.

296
00:12:00,260 --> 00:12:03,910
By mastering the use of Docker, it successfully tames that inherent complexity of

297
00:12:03,910 --> 00:12:04,520
components

298
00:12:04,520 --> 00:12:06,700
like Postfix and Rspam.

299
00:12:06,700 --> 00:12:10,200
It ultimately makes enterprise-grade mail management feasible for anyone with a

300
00:12:10,200 --> 00:12:10,800
foundation

301
00:12:10,800 --> 00:12:12,460
in server administration.

302
00:12:12,460 --> 00:12:16,170
So what this all means for you, the learner, is that high-level open-source

303
00:12:16,170 --> 00:12:17,120
infrastructure

304
00:12:17,120 --> 00:12:21,280
doesn't have to be a nightmare to set up, provided you find the right containerized

305
00:12:21,280 --> 00:12:22,280
solution.

306
00:12:22,280 --> 00:12:24,000
It takes the heavy lifting off your plate.

307
00:12:24,000 --> 00:12:27,950
But the journey of MailCal is one of constant focus and streamlining, and that

308
00:12:27,950 --> 00:12:28,400
raises a

309
00:12:28,400 --> 00:12:32,020
really fascinating final question for you to consider.

310
00:12:32,020 --> 00:12:36,660
The January 2025 update notes a major decision.

311
00:12:36,660 --> 00:12:40,920
Which changed the full-text search, and which kicked out Nextcloud?

312
00:12:40,920 --> 00:12:41,920
That's powerful.

313
00:12:41,920 --> 00:12:45,280
I mean, Nextcloud is a massive groupware suite in its own right.

314
00:12:45,280 --> 00:12:48,840
Kicking it out suggests a really serious commitment to a narrow focus.

315
00:12:48,840 --> 00:12:49,840
It does.

316
00:12:49,840 --> 00:12:53,440
It points to this constant evaluation of the suite's core purpose, and it raises an

317
00:12:53,440 --> 00:12:53,920
essential

318
00:12:53,920 --> 00:12:55,880
question for any infrastructure project.

319
00:12:55,880 --> 00:12:56,880
Which is?

320
00:12:56,880 --> 00:13:00,310
Which features are truly essential for a focused, efficient mail server, and which

321
00:13:00,310 --> 00:13:00,700
ones might

322
00:13:00,700 --> 00:13:04,280
actually dilute its mission and introduce unnecessary complexity?

323
00:13:04,280 --> 00:13:06,600
Where do you draw that line?

324
00:13:06,600 --> 00:13:11,090
A question for you to mull over as you start your own deep dive into containerized

325
00:13:11,090 --> 00:13:12,320
infrastructure.

326
00:13:12,320 --> 00:13:15,400
We'd like to thank our supporter for this deep dive, SafeServer.

327
00:13:15,400 --> 00:13:19,830
Find more information about hosting powerful software and support for your digital

328
00:13:19,830 --> 00:13:20,200
transformation

329
00:13:20,200 --> 00:13:22,980
at www.safeserver.de.

330
00:13:22,980 --> 00:13:23,980
Thank you for joining us.

331
00:13:23,980 --> 00:13:27,680
Join us next time for another deep dive into the source material that matters.