1.1 --- a/tests/test_handle.py Sun Oct 01 15:08:20 2017 +0200
1.2 +++ b/tests/test_handle.py Sun Oct 01 16:38:10 2017 +0200
1.3 @@ -92,19 +92,15 @@
1.4
1.5 # NOTE: This is a simpler form of the code in imipweb.client.
1.6
1.7 - organiser = get_address(self.obj.get_value("ORGANIZER"))
1.8 -
1.9 - self.update_sender(attendee_attr)
1.10 + self.update_sender_attr(attendee_attr)
1.11 self.obj["ATTENDEE"] = [(self.user, attendee_attr)]
1.12 self.update_dtstamp()
1.13 - self.update_sequence(False)
1.14 + self.update_sequence()
1.15
1.16 - message = self.messenger.make_outgoing_message(
1.17 - [self.obj.to_part(method)],
1.18 - [organiser],
1.19 - outgoing_bcc=get_address(self.user)
1.20 - )
1.21 + parts = [self.obj.to_part(method)]
1.22 + recipients = self.get_recipients()
1.23
1.24 + message = self.make_message(parts, recipients, bcc_sender=True)
1.25 return message.as_string()
1.26
1.27 # A simple main program that attempts to handle a stored request, writing the
1.28 @@ -139,7 +135,8 @@
1.29
1.30 Alternatively, omit the UID and RECURRENCE-ID and provide event-only details on
1.31 standard input to force the script to handle an event not already present in the
1.32 -store.
1.33 +store. The event details must be a fragment of a calendar file, not an entire
1.34 +calendar file, nor a mail message containing calendar data.
1.35
1.36 If 'counter' has been indicated, alternative start and end datetimes are also
1.37 required. If a specific recurrence is being separated from an event, such