ManageSieve for Everyone

A spectre is haunting Python Discord -- the spectre of proprietary mail
filtering programs. All the Powers of Big Mail have entered into a holy
alliance to exorcise this spectre: Outlook and GMail, Yahoo and Zoho,
AOL adn iCloud.

Where is the open protocol in opposition that has not been decried as
unprofessional, free and open source by its opponents in power? Where is
the Opposition that has not hurled back the branding reproach of
Internet Standards, against the more advanced opposition protocols, as
well as against its reactionary adversaries?

Two things result from this fact.

I.  Sieve is already standardized as a protocol via the IETF.

II. It is high time that Python Discord users should openly, in the face
of the TLS-encrypted internet, filter their notifications, their love
letters, their mailing lists, and meet this nursery tale of the Spectre
of ManageSieve with a Manifesto of Python Discord Devops itself.

To this end, ManageSieve users of various nationalities have assembled
on jitsi.pydis.wtf, and sketched the following commit, to be published
on the lovelace Python Discord e-mail service.

3 files changed, 10 insertions, 15 deletions

diff --git a/ansible/group_vars/all/nftables.yml b/ansible/group_vars/all/nftables.yml
index df9c853..f45f06b 100644
--- a/ansible/group_vars/all/nftables.yml
+++ b/ansible/group_vars/all/nftables.yml
@@ -18,6 +18,8 @@ nftables_configuration: |
     set mail_accepted {
       type inet_service
       elements = {
+        # Mail configuration
+        sieve,
         # Mail submission
         smtp,
         smtps,
diff --git a/ansible/roles/dovecot/templates/dovecot.conf.j2 b/ansible/roles/dovecot/templates/dovecot.conf.j2
index 4b2c46a..7f1807b 100644
--- a/ansible/roles/dovecot/templates/dovecot.conf.j2
+++ b/ansible/roles/dovecot/templates/dovecot.conf.j2
@@ -87,12 +87,6 @@ dict {
   #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
 }
 
-# PYDIS CONFIG START
-
-protocols = imap lmtp
-
-# PYDIS CONFIG END
-
 # Most of the actual configuration gets included below. The filenames are
 # first sorted by their ASCII value and parsed in that order. The 00-prefixes
 # in filenames are intended to make it easier to understand the ordering.
diff --git a/docs/docs/services/email/mail-clients.md b/docs/docs/services/email/mail-clients.md
index 8c797d0..c2d37bf 100644
--- a/docs/docs/services/email/mail-clients.md
+++ b/docs/docs/services/email/mail-clients.md
@@ -60,15 +60,14 @@ are not provided by the PyDis mailserver please let us know in `#dev-oops`.
 
 We support server-side email filtering with [Pigeonhole
 Sieve](https://doc.dovecot.org/configuration_manual/sieve/pigeonhole_sieve_interpreter/).
-
-!!! example "DevOps Only"
-
-    For now, since this feature requires access to a home directory on the host, it is
-    only accessable to members of the DevOps team. If you are not a member of the DevOps
-    team and wish to configure sieve, please let us know in the #dev-oops channel.
-
-    We may in future investigate further usage of `dovecot-managesieved` to allow for
-    remote management of the Sieve filters.
+Sieve scripts are managed via [the ManageSieve
+protocol](https://datatracker.ietf.org/doc/html/rfc5804). Your e-mail client
+should have built-in functionality for writing and editing these scripts. For a
+listing of clients, see [the official Sieve website](http://sieve.info/clients).
+
+If you're looking for a command-line client,
+[`sieve-connect`](https://people.spodhuis.org/phil.pennock/software/) may be
+what you are looking for.
 
 Using this, users can perform common mail tasks automatically by writing small
 sieve scripts that are able to act on inbound mail before it reaches a user