Remove legacy multischleuder.yml from project root

multischleuder.yml

@@ -1,58 +0,0 @@
----
-
-api:
-  url: "https://localhost:4443"
-  token: 24125f2fe0ebc2fd853cf2e02f7599b3fa7f71a4c8e1519b
-  #cafile: /etc/schleuder/schleuder-certificate.pem
-  cafile: ca.pem
-
-lists:
-
-  - target: test@schleuder.example.org
-    unmanaged:
-      - admin@example.org
-    banned:
-      - banned@example.org
-    sources:
-      - test-basel@schleuder.example.org
-      - test-bern@schleuder.example.org
-      - test-zurich@schleuder.example.org
-    from: test-owner@schleuder.example.org
-
-smtp:
-  hostname: localhost
-  port: 8025
-
-conflict:
-  interval: 604800  # 1 week
-  statefile: /var/lib/multischleuder/conflict.json
-  template: |
-    Hi {subscriber},
-    
-    While compiling the subscriber list of {schleuder}, your
-    address {subscriber} was subscribed on multiple sub-lists with
-    different PGP keys.  There may be something fishy or malicious going on,
-    or this may simply have been a mistake by you or a list admin.
-    
-    You have only been subscribed to {schleuder} using the key you
-    have been subscribed with for the *longest* time:
-      
-    {chosen}
-      
-    Please review the following keys and talk to the admins of the
-    corresponding sub-lists to resolve this issue:
-    
-    Fingerprint                               Sub-List
-    -----------                               --------
-    {affected}
-  
-    For your convenience, this message has been encrypted with *all* of the
-    above keys.  If you have any questions, or do not understand this
-    message, please refer to your local Schleuder admin, or reply to this
-    message.
-  
-    Note that this automated message is unsigned, since MultiSchleuder does
-    not have access to Schleuder private keys.
-  
-    Regards
-    MultiSchleuder {schleuder}