extract_msg.msg_classes.meeting_exception Module

Module contents

class extract_msg.msg_classes.meeting_exception.MeetingException(path, **kwargs)[source]

Class for handling Meeting Exceptions.

Supports all of the options from MSGFile.__init__() with some additional ones.

Parameters:

recipientSeparator – Optional, separator string to use between recipients.
deencapsulationFunc – Optional, if specified must be a callable that will override the way that HTML/text is deencapsulated from the RTF body. This function must take exactly 2 arguments, the first being the RTF body from the message and the second being an instance of the enum DeencapType that will tell the function what type of body is desired. The function should return a string for plain text and bytes for HTML. If any problems occur, the function must either return None or raise one of the appropriate exceptions from extract_msg.exceptions. All other exceptions must be handled internally or they will not be caught. The original deencapsulation method will not run if this is set.

save(**_) → Tuple[SaveType, List[str] | str | None][source]

Meeting Exceptions are hidden attachments with no save behaviors.

If you want something to happen for saving, you can call the save of a parent class or write your own code.

property exceptionReplaceTime: datetime | None

The date and time within the recurrence pattern that the exception will replace.

The value is specified in UTC.

property fExceptionalBody: bool

Indicates that the Exception Embedded Message object has a body that differs from the Recurring Calendar object.

If True, the Exception MUST have a body.

property fInvited: bool: Indicates if invitations have been sent for this exception.