From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/34020 Path: main.gmane.org!not-for-mail From: Hannu Koivisto Newsgroups: gmane.emacs.gnus.general Subject: Re: vCalendar/iCalendar support for Gnus? Date: 03 Jan 2001 18:44:25 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: <87lmss7fh2.fsf@lynx.ionific.com> References: <87ae9augc9.fsf@lynx.ionific.com> <86itnwpptw.fsf@megalith.bp.aventail.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035170023 28259 80.91.224.250 (21 Oct 2002 03:13:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:13:43 +0000 (UTC) Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=), Jaap-Henk Hoepman , ding@gnus.org Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id B4047D049D for ; Wed, 3 Jan 2001 11:45:25 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id KAB27297; Wed, 3 Jan 2001 10:44:59 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 03 Jan 2001 10:44:24 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id KAA18456 for ; Wed, 3 Jan 2001 10:44:12 -0600 (CST) Original-Received: from lynx.ionific.com (lynx.ionific.com [195.197.252.71]) by mailhost.sclp.com (Postfix) with ESMTP id 4BB29D049D for ; Wed, 3 Jan 2001 11:44:36 -0500 (EST) Original-Received: from azure by lynx.ionific.com with local (Exim 3.12 #1 (Debian)) id 14Dr1V-0008HL-00; Wed, 03 Jan 2001 18:44:25 +0200 X-Draft-From: ("lists.ding" 9618) Original-To: wmperry@aventail.com Mail-copies-to: never Mail-Followup-To: ding@gnus.org In-Reply-To: <86itnwpptw.fsf@megalith.bp.aventail.com> User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Original-Lines: 53 Xref: main.gmane.org gmane.emacs.gnus.general:34020 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:34020 wmperry@aventail.com (William M. Perry) writes: | Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro=DFjohann) writes: |=20 | > On 03 Jan 2001, Jaap-Henk Hoepman wrote: | >=20 | > > I really would love this too (not necessarily within gnus | > > though). Problem is that IMAP appears not to be enough to access the | > > calender and contact items stored on the Exchange server. You can | > > get the subjects, but not the date and time of the | > > appointment. Apparantly MAPI is needed to access these other | > > details. | >=20 | > If I were to implement such stuff, I'd put the additional information | > into some hidden message header fields. So that's probably precisely Uh, you would need quite a lot of header data. Anyways, in Microsoft's case the relevant information is fortunately not in the header fields, it's in the body... | > what Microsoft did not do. But I think it doesn't hurt to do `C-u g' on | > such a message just to be sure. ...but `C-u g' is a good thing to do anyway, because Gnus doesn't display the relevant MIME part by default. | The only thing that is similar is the message always starts with: Yeah, but that's just a mostly useless informal version of the iCalendar REQUEST, which is in the next MIME part... | ----> cut here <---- | When: Friday, December 29, 2000 1:30 PM-3:00 PM (GMT-08:00) Pacific Time | (US & Canada); Tijuana. | Where: @The Roaster |=20 | *~*~*~*~*~*~*~*~*~* | ----> cut here <---- |=20 | Maybe a washing function could be used for these (probably old-style | messages). I know we are not running exchange 2000. ...at least in Exchange 2000. I think there should be a second part in earlier Exchange messages too, but perhaps it's not iCalendar stuff. In any case, if what you cut away was actually not usable information, while it might be "nice" to be able to parse even that informal version, it probably isn't very useful in practise, because you probably cannot reply to the request (here I'm not meaning iCalendar request as this all was assuming that the clipped part was not iCalendar stuff in that earlier Exchange). --=20 Hannu