diff --git a/README.md b/README.md
index 9d761e47..90eb329c 100644
--- a/README.md
+++ b/README.md
@@ -402,7 +402,7 @@ python3 epicyon.py --nickname [yournick] --domain [name] \
 
 Deletion of posts in a federated system is not always reliable. Some instances may not implement deletion, and this may be because of the possibility of spurious deletes being sent by an adversary to cause trouble.
 
-To disallow deletion requests on your server set the **--nodeletion** option.
+To disallow deletion requests by unauthenticated people on your server set the **--nodeletion** option.
 
 Another complication is that the followers collection may change between the time when a post was created and the time it was deleted, leaving some stranded copies.
 
diff --git a/daemon.py b/daemon.py
index 89c0ad7b..17e2a0fd 100644
--- a/daemon.py
+++ b/daemon.py
@@ -206,10 +206,9 @@ class PubServer(BaseHTTPRequestHandler):
         if self.server.debug:
             print('DEBUG: handle any unfollow requests')
         outboxUndoFollow(self.server.baseDir,messageJson,self.server.debug)
-        if not self.server.nodeletion:
-            if self.server.debug:
-                print('DEBUG: handle delete requests')
-            outboxDelete(self.server.baseDir,self.server.httpPrefix,messageJson,self.server.debug)
+        if self.server.debug:
+            print('DEBUG: handle delete requests')
+        outboxDelete(self.server.baseDir,self.server.httpPrefix,messageJson,self.server.debug)
         if self.server.debug:
             print('DEBUG: sending c2s post to named addresses')
             print('c2s sender: '+self.postToNickname+'@'+self.server.domain+':'+str(self.server.port))