From 427d0da3cda0e5246cf89257bcb95b3501ec0048 Mon Sep 17 00:00:00 2001
From: Katharina Fey <kookie@spacekookie.de>
Date: Sun, 7 Apr 2019 22:45:37 +0200
Subject: Removing debugging

---
 content/blog/105_sieve.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 content/blog/105_sieve.md

(limited to 'content')

diff --git a/content/blog/105_sieve.md b/content/blog/105_sieve.md
new file mode 100644
index 0000000..533ff72
--- /dev/null
+++ b/content/blog/105_sieve.md
@@ -0,0 +1,19 @@
+Title: Don't fear the sieve
+Category: Blog
+Tags: /dev/diary, e-mail, programming
+Date: 2019-02-01
+Slug: understanding-sieve
+Status: Draft
+
+If you don't already know, sieve (/siːv/) is an e-mail filtering language.
+It's not touring complete (i.e. it doesn't allow recursion) 
+and has been defined through a series of RFCs for the base language
+as well as several extentions.
+
+The RFCs aren't exactly nice to read.
+But luckily, there are plenty of tutorials on the internet,
+that try to explain sieve.
+Unfortunately most of them are garbage.
+
+The main reason for this is, that the articles never deal
+with a realistic set of constraints of requirements
-- 
cgit v1.2.3