# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1427326026 -3600
# Node ID 9b8237cc00bd26e56f3d5a111fda59a714d12c39
# Parent  ca59ce0f3198d4e92dacee0057f9813ea0513b11
Added remarks about explicitly setting the BCC recipient.

diff -r ca59ce0f3198 -r 9b8237cc00bd imiptools/mail.py
--- a/imiptools/mail.py	Wed Mar 25 18:23:37 2015 +0100
+++ b/imiptools/mail.py	Thu Mar 26 00:27:06 2015 +0100
@@ -53,6 +53,10 @@
         using the given 'sender' identity if indicated, indicating an
         'outgoing_bcc' identity if indicated, delivering to a local mail system
         using LMTP if 'lmtp_socket' is provided.
+
+        The 'outgoing_bcc' argument is required when sending on behalf of a user
+        from the calendar@domain address, since this will not be detected as a
+        valid participant and handled using the outgoing transport.
         """
 
         if lmtp_socket:
diff -r ca59ce0f3198 -r 9b8237cc00bd imipweb/handler.py
--- a/imipweb/handler.py	Wed Mar 25 18:23:37 2015 +0100
+++ b/imipweb/handler.py	Thu Mar 26 00:27:06 2015 +0100
@@ -93,6 +93,9 @@
                 make_freebusy(freebusy, uid, self.user, user_attr)
                 ]))
 
+        # Explicitly specify the outgoing BCC recipient since we are sending as
+        # the generic calendar user.
+
         message = self.messenger.make_outgoing_message(parts, recipients, outgoing_bcc=sender)
         self.messenger.sendmail(recipients, message.as_string(), outgoing_bcc=sender)