From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Doyley, Marvin M." <m.doyley@rochester.edu>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Getting email from MS outlook into emacs
Date: Tue, 28 Nov 2023 08:58:45 +0000 [thread overview]
Message-ID: <87fs0qjltn.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87y1eitgwi.fsf@localhost> (Ihor Radchenko's message of "Tue, 28 Nov 2023 08:34:53 +0000")
On Tuesday, 28 Nov 2023 at 08:34, Ihor Radchenko wrote:
> ... except when institution also prohibits anything but MS Outlook to
> access the MS Exchange protocol.
Indeed but my experience has often been that such restrictive practices
are the result of blind clicking on the part of the IT department and
can be rescinded through discussion with them. Over the years I have
been in my current institution, I have had these kinds of discussions
several times (using Linux, not Windows; using other MUAs, not Outlook;
etc.) and have managed to get the access I needed almost always.
But some places are probably a lost cause in this regard unfortunately.
Tail wagging the dog comes to mind...
--
: Eric S Fraga, with org release_9.6.7-661-g34ee6f in Emacs 30.0.50
next prev parent reply other threads:[~2023-11-28 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 3:09 Getting email from MS outlook into emacs Doyley, Marvin M.
2023-11-28 8:00 ` Fraga, Eric
2023-11-28 8:34 ` Ihor Radchenko
2023-11-28 8:58 ` Fraga, Eric [this message]
2023-11-28 9:24 ` Ihor Radchenko
2023-11-28 9:25 ` Alain.Cochard
2023-11-28 9:40 ` Ihor Radchenko
2023-11-28 10:08 ` Martin Steffen
2023-11-28 8:40 ` Martin Steffen
2023-11-28 9:10 ` Fraga, Eric
2023-11-30 12:18 ` Max Nikulin
-- strict thread matches above, loose matches on Subject: below --
2023-11-29 19:08 Presnell,Brett Douglas
2023-11-30 9:52 ` Fraga, Eric
2023-12-07 20:11 ` Leo Butler
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=87fs0qjltn.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=m.doyley@rochester.edu \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.