From: Eric S Fraga <email@example.com>
To: Matthieu Lemerre <firstname.lastname@example.org>
Subject: Re: org and microsoft exchange
Date: Fri, 08 Jul 2011 10:02:54 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Matthieu Lemerre's message of "Thu, 07 Jul 2011 21:21:00 +0200")
Matthieu Lemerre <email@example.com> writes:
>> I have no idea what I will need to do! I really am truly ignorant of
>> the whole MS world other than I know, if push comes to shove, I can
>> install cygwin and then Emacs when I have to... ;-)
> Actually, there are emacs binaries for win32 that work without needing
thanks; but cygwin seems natural to install in conjunction with emacs as
I want bash et al. if I ever have to use Windows. having said this,
it's been years since I have had to do this luckily (for me).
>> > For the record, here are some other things that I tried/maybe worth
>> > trying:
>> > - Davmail + thunderbird: allows accessing exchange mail and calendar and
>> > syncinc with it, but did not manage to import org ics into that.
>> > - Evolution and the openexchange client may be other things to try.
>> These two seem to imply using something other than Emacs for my email?
>> Or have I misunderstood?
> Openexchange is a command line tool to synchronize with an exchange
> server. But it is still incomplete, and I found it a nightmare to
> configure and use.
> Evolution is indeed another mail client, but my intent was to use it
> solely as a mean to synchronize the org mode ics file with the exchange
> calendar. Instead of using outlook for this...
Thanks for the explanation.
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 220.127.116.11
: using Org-mode version 7.6 (release_7.6.4.gf305a)
next prev parent reply other threads:[~2011-07-08 9:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 2:09 org and microsoft exchange Skip Collins
2011-06-20 7:52 ` Eric S Fraga
2011-06-20 11:53 ` Holger Wenzel
2011-06-20 12:01 ` Skip Collins
2011-06-20 14:13 ` Jonathan Arkell
2011-06-26 13:35 ` Matthieu Lemerre
2011-06-27 17:14 ` Eric S Fraga
2011-06-27 19:13 ` Matthieu Lemerre
2011-06-28 23:16 ` Bastien
2011-07-07 19:13 ` Matthieu Lemerre
2011-07-08 9:26 ` Bastien
2011-06-29 16:44 ` Eric S Fraga
2011-07-07 19:21 ` Matthieu Lemerre
2011-07-08 9:02 ` Eric S Fraga [this message]
2011-07-08 22:14 ` Achim Gratz
2011-06-20 11:53 ` Org-mode is not able to manage complex calendar events (was: org and microsoft exchange) Karl Voit
2011-06-20 14:38 ` Org-mode is not able to manage complex calendar events Eric S Fraga
2011-06-20 15:51 ` Karl Voit
2011-06-20 17:19 ` Eric S Fraga
2011-06-21 12:32 ` Karl Voit
2011-06-21 12:50 ` Rémi Vanicat
2011-06-21 16:46 ` Karl Voit
2011-06-21 15:12 ` Eric S Fraga
2011-06-21 17:24 ` Karl Voit
2011-06-28 9:36 ` Bastien
2011-06-28 12:19 ` How to place a feature wish (was: Org-mode is not able to manage complex calendar events) Karl Voit
2011-06-20 18:48 ` Org-mode is not able to manage complex calendar events Memnon Anon
2011-07-01 15:18 ` Bastien
2011-07-01 16:25 ` Karl Voit
2011-07-02 9:21 ` Bastien
2011-07-02 10:20 ` Karl Voit
2011-06-20 14:42 ` org and microsoft exchange Philipp Haselwarter
2011-06-20 15:04 ` Nick Dokos
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).