I've got a colleague who keeps sending me attached calendar items from an MS Exchange server. Thunderbird and Mutt can't even see the attachment, but if I view the raw message source, it is there, encoded:
Content-Type: multipart/alternative; boundary="_002_80B708C9C67AE14BA396foo_" MIME-Version: 1.0 --_002_80B708C9C67AE14BA396foo_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 =20 --_002_80B708C9C67AE14BA396foo_ Content-Type: text/calendar; charset="utf-8"; method=REQUEST Content-Transfer-Encoding: base64
I can run the text/calendar portion through
base64 -d and read it just fine, but now I have an external text file that looks like ...
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD ...
Obviously, this isn't my problem. Exchange is turning out poorly formatted email messages. Nonetheless, the nature of this exchange is such that my life will be muuuch easier if I can just figure out a reliable way to read these invites.
Is there a tool I can use to actually read the calendar file? There seem to be a few different date fields and I can't tell which is which. Is there an automated way to push the file to evolution?