Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Exchange server Calendar folder analysis (Was: Synching diary with an exchange server?)
Date: Wed, 11 Jun 2008 21:51:37 +0200	[thread overview]
Message-ID: <87ej73agxi.fsf@dod.no> (raw)
In-Reply-To: <878wxgna1u.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

> Is there eg. something that can take an iCalendar export from the emacs
> diary, and can use it to update my Exchange calendar?

That I still don't know the answer to, but I've been told that the
Calendar is just a folder on the server.

So I browsed the Exchange nnimap server today, from the server buffer,
and found a folder at the top, named Calendar.

I subscribed to this folder, and visited it, and in it where messages
with the following headers:

Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C8CAD5.5F6B4710"
Content-class: urn:content-classes:appointment

The Content-class is something Microsoft'ish, not MIME, but I'm guessing
it has to be there for the messages to work.

Then there is either just a text part or a multipart/alternative with a
text/plan and an HTML part.

Then there is a part (at the top level) with headers like this.

Content-class: urn:content-classes:appointment
Content-Type: text/calendar;
	charset="UTF-8";
	method=REQUEST
Content-Transfer-Encoding: 8bit

The content in there looks to be in the vCalendar format.

What's in there, are all invites, whether I've responded to them, or
not.  So I guess to mark a meeting as accepted, the contents of the
calendar part has to be modified...?

Only it's not possible to modify messages with IMAP.  The only way would
be to download the message, modify it, delete the original message, and
upload the modified message.

This will result in the modified calendar entry having a different
server message id than the original calendar entry.  I don't know if
that would break some magic, or not...?

But if this is all that needs doing to get a working calendar
synchronization, it's strange that no work has been done to accomplish
it.  At least none that a quick google and gmane search can find.

I found this thread on gmane, but it's pretty old:
	http://thread.gmane.org/gmane.emacs.gnus.general/33977

Appearently then, the vCalendar payload wasn't accessable from the
message.  It seems to be now.

It did mention some iCalendar or vCalendar stuff that was introduced
into Gnus at about that time (2001), but not what it was about.
Grepping for iCalendar or vCalendar in the .el files in the current CVS
Gnus, gives no matches.

Does anyone know if there are any obvious showstoppers with accessing
the Calendar folder using IMAP?  To maybe create something like nndiary
that would create articles in the required form, and store them in that
particular nnimap folder?

Thanx!


- Steinar




  reply	other threads:[~2008-06-11 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 22:40 Synching diary with an exchange server? Steinar Bang
2008-06-11 19:51 ` Steinar Bang [this message]
2008-06-12  7:57   ` Exchange server Calendar folder analysis Bjørn Mork
2008-06-12 10:58     ` Steinar Bang
2008-06-12 19:14       ` Steinar Bang

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=87ej73agxi.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /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).