From f53fd92cd333f37eedf97ffa8034519051bfedef Mon Sep 17 00:00:00 2001
From: "Victor \"multun\" Collod" <victor.collod@epita.fr>
Date: Fri, 8 Mar 2019 18:30:07 +0100
Subject: [PATCH] Remove debug leftovers, improve documentation

---
 README.md     | 14 +++++++++++---
 todo/utils.py |  3 ---
 2 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index abdcd2d..4b74a5d 100644
--- a/README.md
+++ b/README.md
@@ -139,11 +139,19 @@ The current django-todo version number is available from the [todo package](http
 
 ## Mail tracking
 
-What if you could turn django-todo into a shared mailbox ?
+What if you could turn django-todo into a shared mailbox?
+Django-todo includes an optional feature that allows emails sent to a
+dedicated mailbox to be pushed into todo as new tasks, and responses to
+be added as comments on that original tasks.
 
- - incoming emails create a new task
- - thread answers create task comments
+This allows support teams to work with a fully unified email + bug
+tracking system to avoid confusion over who's seen or responded to what.
 
+To enable the feature, you need to:
+
+ - define an email backend for outgoing emails
+ - define an email backend for incoming emails
+ - start a worker, which will wait for new emails
 
 ```python
 from todo.mail.producers import imap_producer
diff --git a/todo/utils.py b/todo/utils.py
index 8e682ea..a2cde5b 100644
--- a/todo/utils.py
+++ b/todo/utils.py
@@ -83,8 +83,6 @@ def todo_send_mail(user, task, subject, body, recip_list):
         epoch=int(time.time())
     )
 
-    import sys
-    print("sending mail", file=sys.stderr)
     # the thread message id is used as a common denominator between all
     # notifications for some task. This message doesn't actually exist,
     # it's just there to make threading possible
@@ -106,7 +104,6 @@ def todo_send_mail(user, task, subject, body, recip_list):
             },
             connection=connection,
         )
-        # import pdb; pdb.set_trace();
         message.send()