Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Subject: Re: vCalendar/iCalendar support for Gnus?
Date: 03 Jan 2001 12:06:34 -0500	[thread overview]
Message-ID: <86bstopntx.fsf@megalith.bp.aventail.com> (raw)
In-Reply-To: <87lmss7fh2.fsf@lynx.ionific.com>

Hannu Koivisto <azure@iki.fi> writes:

> wmperry@aventail.com (William M. Perry) writes:
> 
> | Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> | 
> | > On 03 Jan 2001, Jaap-Henk Hoepman wrote:
> | > 
> | > > 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.
> | > 
> | > 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.

For me, there is no other MIME part.  The content-type of the main message
is text/plain (charset of iso-8859-1), and there is nothing else in the
message.  No iCalendar or vCalendar at all.

All hail exchange and its many faces!

-Bill P.



  reply	other threads:[~2001-01-03 17:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-02 15:24 Hannu Koivisto
2001-01-03 10:31 ` Kevin A. Burton
2001-01-03 17:17   ` Charles Sebold
2001-01-03 17:55     ` Kai Großjohann
2001-01-03 18:14       ` Charles Sebold
2001-01-27  5:55         ` Amos Gouaux
2001-01-03 13:50 ` Jaap-Henk Hoepman
2001-01-03 15:01   ` Hannu Koivisto
2001-01-03 16:48     ` Chris Shenton
2001-01-04  4:20     ` ShengHuo ZHU
2001-01-09 16:58     ` Paul Jarc
2001-01-09 17:03       ` ShengHuo ZHU
2001-01-03 15:47   ` Kai Großjohann
2001-01-03 16:23     ` William M. Perry
2001-01-03 16:44       ` Hannu Koivisto
2001-01-03 17:06         ` William M. Perry [this message]
2001-01-18 18:59           ` Toby Speight

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bstopntx.fsf@megalith.bp.aventail.com \
    --to=wmperry@aventail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).