When 'Use TNEF Contents' is set to 'Replace', meeting requests aren't actually replaced, they're just removed.
If Outlook is set to HTML (and/or so is the contact) and/or the Exchange server is set to not send TNEF (set-remotedomain -name default -TNEFEnabled:$false) it actually sends vcalender in base64 under a text/calendar content-type. In the latter case if outlook does send TNEF to the server exchange will convert it to text/calendar content-type.
With for example ytnef the file can easily be extracted. Would be nice if the replace function would actually replace the meeting with a vcalendar.
When 'Use TNEF Contents' is set to 'Replace', meeting requests aren't actually replaced, they're just removed.
If Outlook is set to HTML (and/or so is the contact) and/or the Exchange server is set to not send TNEF (set-remotedomain -name default -TNEFEnabled:$false) it actually sends vcalender in base64 under a text/calendar content-type. In the latter case if outlook does send TNEF to the server exchange will convert it to text/calendar content-type.
With for example ytnef the file can easily be extracted. Would be nice if the replace function would actually replace the meeting with a vcalendar.
$ ytnef -f . winmail1.dat ./MtgReq.ics $ cat MtgReq.ics BEGIN:VCALENDAR METHOD:REQUEST PRODID:-//The Gauntlet//ytnef 2.0.0//EN ...
That basically looks similar to the base64 decoded.
Could it actually replace the meeting so people don't receive a plain/text message instead of a meeting when it's set to replace?