aboutsummaryrefslogtreecommitdiff
path: root/content/blog/105_sieve.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/105_sieve.md')
-rw-r--r--content/blog/105_sieve.md19
1 files changed, 19 insertions, 0 deletions
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