From: Martin Steffen <msteffen@ifi.uio.no>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: alain.cochard@unistra.fr,
"emacs-orgmode\@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Getting email from MS outlook into emacs
Date: Tue, 28 Nov 2023 11:08:49 +0100 [thread overview]
Message-ID: <xk92o7fechqm.fsf@afram.ifi.uio.no> (raw)
In-Reply-To: <87sf4qtdvc.fsf@localhost> (Ihor Radchenko's message of "Tue, 28 Nov 2023 09:40:23 +0000")
>>>>> "Ihor" == Ihor Radchenko <yantar92@posteo.net> writes:
Ihor> Alain.Cochard@unistra.fr writes:
>> ... except when institution prohibits redirecting to another
>> email provider -- my case ...
Ihor> I would then simply use another email for most of the
Ihor> communication. The institution email would then just be
Ihor> needed to communicate with institute-wide announcements.
That's a possibility I had indeed thought about, because also for me
it's forbidden to forward (automatically or not) stuff outwards from the
domain. I think it's not forbidden to "move" or sync emails to local
disk, as far as I can see, though I was not able to reasonably
automatize that (like with davmail, though that almost worked for a time
resp. partially...)
For institutional seasonal greetings or general announcements the
muddled outlook access would even be acceptable for me, who
cares. Unfortunately, there are many emails (from inside the
organization, a university) that are individual, relevant, and at times
urgent and requiring (re-)action and preferably efficient
organization, overview, and handling, but I cannot use alternative
email-addresses for that.
Martin
Ihor> -- Ihor Radchenko // yantar92, Org mode contributor, Learn
Ihor> more about Org mode at <https://orgmode.org/>. Support Org
Ihor> development at <https://liberapay.com/org-mode>, or support my
Ihor> work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-11-28 10:09 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
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 [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xk92o7fechqm.fsf@afram.ifi.uio.no \
--to=msteffen@ifi.uio.no \
--cc=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).