Gnus development mailing list
 help / color / mirror / Atom feed
From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: gmail setup (was: how to forward a message that contains attachment)
Date: Mon, 06 Apr 2020 12:19:31 +0200	[thread overview]
Message-ID: <87tv1wvrv0.fsf_-_@eps142.cdf.udc.es> (raw)
In-Reply-To: <87k12tipzw.fsf@dick>

dick.r.chiang writes:

> I continue to bemoan Gnus's de facto guidance, i.e., the top search results
> for "gnus gmail", on the extremely common task of integrating a big-box IMAP
> service -- a task mu4e and notmuch have made much easier than Gnus.

mu4e and notmuch do not have to interact at all with gmail's IMAP —
that is a task for offlineimap or mbsync, as it is stated in their
respective manuals.

And then you will see that everybody has to join the very same
obstacle-avoidance race that is to interact with those specific servers.

-- 
Alberto



  reply	other threads:[~2020-04-07 16:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 14:33 how to forward a message that contains attachment Uwe Brauer
2020-04-04 14:54 ` Eric S Fraga
2020-04-04 18:57   ` Uwe Brauer
2020-04-05  2:00     ` Bob Newell
2020-04-05  6:07       ` Uwe Brauer
2020-04-05 19:31         ` Bob Newell
2020-04-05 13:18     ` Eric S Fraga
2020-04-05 17:11       ` Uwe Brauer
2020-04-05 17:37         ` Adam Sjøgren
2020-04-05 21:25           ` dick.r.chiang
2020-04-06 10:19             ` Alberto Luaces [this message]
2020-04-07 16:42               ` gmail setup dick.r.chiang
2020-04-07 17:46                 ` Alberto Luaces
2020-04-07 18:19                   ` dick.r.chiang
2020-04-07 18:35                     ` Alberto Luaces
2020-04-08  1:53                       ` Bob Newell
2020-04-10 16:56                         ` Alberto Luaces
2020-04-06 10:19           ` how to forward a message that contains attachment Uwe Brauer
2020-04-06 10:26           ` Uwe Brauer
2020-04-07 17:03             ` Adam Sjøgren
2020-04-06 11:36           ` Uwe Brauer

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=87tv1wvrv0.fsf_-_@eps142.cdf.udc.es \
    --to=aluaces@udc.es \
    --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).