Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: davmail hangs *after* retrieving pop email from Exchange server
Date: Thu, 27 May 2021 14:04:39 +0100	[thread overview]
Message-ID: <87fsy8wcns.fsf@ucl.ac.uk> (raw)

Hello,

TL;DR: how do I figure out what gnus is doing when it hangs after
downloading emails via davmail from an Exchange server?

Longer story: due to the introduction of multi-factor authentication
(MFA) in our institution, I have spent the past 2 days trying to find a
solution that allows me to continue using gnus.

For the record, one interesting albeit less than satisfying solution is
to run Thunderbird with pop access to the exchange server.  Thunderbird
supports OAuth2 access.  Then you can point gnus to the mbox format file
Thunderbird creates to store the downloaded emails.  This does mean
having to have Thunderbird running...

Davmail is the most often suggested solution.  It took some time to get
this working but it's sort of there.  I can download emails using pop
access.  However, for some reason, after retrieving the emails, gnus
hangs until I hit C-g and then the group buffer is updated.

So, my question is: how do I find out what is happening after the emails
have downloaded?  The davmail log doesn't show anything and neither does
*Messages*.  Are there gnus variables I can set to help me figure this
out?  It does seem that davmail has does everything it should and so has
gnus up to a point.

Thank you,
eric

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.4.6 on Debian bullseye/sid



             reply	other threads:[~2021-05-27 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 13:04 Eric S Fraga [this message]
2021-05-27 13:14 ` Dan Christensen
2021-05-27 22:12   ` Eric S Fraga
2021-05-27 15:40 ` Eric Abrahamsen
2021-05-27 16:50   ` Eric S Fraga
2021-05-27 16:59     ` Eric Abrahamsen
2021-05-27 18:49       ` Eric S Fraga
2021-05-27 18:59         ` Eric Abrahamsen
2021-05-27 17:03   ` Eric S Fraga

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=87fsy8wcns.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).