From: Julien Cubizolles <j.cubizolles@free.fr>
To: help-gnu-emacs@gnu.org
Subject: Re: From Gnus to mu4e
Date: Wed, 26 Aug 2015 08:53:41 +0200 [thread overview]
Message-ID: <87k2sizgju.fsf@free.fr> (raw)
In-Reply-To: 20150821130614.GD31789@chitra.no-ip.org
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>> * If a message is tagged with several labels on Gmail, does it appear in
>> several folders in the local repository ? On a related note, if one
>> were to move a message from a folder in a repository synced with Gmail
>> to another folder not synced (for archiving purposes), I guess the
>> message would remain at least in the [Gmail]/All Mail folder. Is there
>> an easy way to remove it altogether from Gmail ?
>
> There are many subtleties when it comes to Gmail's implementation of the
> IMAP interface. I would recommend reading these two articles:
>
> - https://support.google.com/mail/answer/77657?hl=en
> - https://support.google.com/mail/answer/78755?hl=en
>
> That said, in Gmail, you need something like this:
>
> When a message is marked as deleted and expunged from the last visible IMAP folder:
> - [ ] Archive the message (default)
> - [X] Move the message to the Bin
> - [ ] Immediately delete the message forever
>
> You can also set the last option, choosing the default will leave it in
> Gmail. On top of this, you should make sure the All Mail folder is
> _not_ accessible over IMAP. This is important. As long as the message
> is present in at least one IMAP folder, Gmail will retain it. This is
> where it becomes important how you choose to delete it. With notmuch,
> when you delete a message the delete flag will be forwarded to all the
> respective messages in the maildir, which in turn ensures it is deleted
> from Gmail the next time you sync. Maybe mu4e does something similar.
Thanks a lot for this info: It will be useful regardless of the MUA I
use.
Julien.
next prev parent reply other threads:[~2015-08-26 6:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 21:23 From Gnus to mu4e Julien Cubizolles
2015-08-21 10:28 ` Julien Cubizolles
2015-08-21 10:49 ` Colin Yates
2015-08-21 13:06 ` Suvayu Ali
2015-08-26 6:53 ` Julien Cubizolles [this message]
2015-08-25 5:49 ` Bastien
2015-08-25 6:28 ` Ian Zimmerman
2015-08-25 6:56 ` Bastien Guerry
2015-08-26 7:22 ` Julien Cubizolles
2015-08-27 12:50 ` Rainer M Krug
2015-08-27 17:15 ` Bastien
2015-08-28 8:39 ` Rainer M Krug
2015-08-28 8:44 ` Bastien
2015-08-28 8:51 ` Rainer M Krug
2015-08-28 8:58 ` Rasmus
2015-08-28 9:15 ` Julien Cubizolles
2015-08-28 10:03 ` Rainer M Krug
2015-08-28 10:08 ` Rasmus
2015-08-28 10:41 ` Rainer M Krug
2015-08-28 10:04 ` Rasmus
2015-08-28 8:51 ` Bastien
2015-08-27 21:27 ` Julien Cubizolles
2015-08-27 23:34 ` Suvayu Ali
2015-08-27 23:50 ` Ian Zimmerman
2015-08-28 0:14 ` Suvayu Ali
2015-08-28 0:24 ` Ian Zimmerman
2015-08-28 8:25 ` Rainer M Krug
2015-08-28 9:06 ` Suvayu Ali
2015-08-28 15:31 ` Ian Zimmerman
2015-08-31 0:16 ` Suvayu Ali
2015-08-28 8:21 ` Rainer M Krug
2015-08-27 12:58 ` Suvayu Ali
2015-08-27 15:52 ` Glenn Morris
2015-08-27 17:32 ` Suvayu Ali
2015-08-27 17:11 ` Bastien
2015-08-27 17:08 ` Bastien
2015-08-27 17:30 ` Suvayu Ali
2015-08-27 21:52 ` Julien Cubizolles
2015-08-27 22:18 ` Bastien
2015-08-27 23:30 ` Julien Cubizolles
[not found] <mailman.14.1440105837.31004.help-gnu-emacs@gnu.org>
2015-08-24 11:19 ` Joost Kremers
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2sizgju.fsf@free.fr \
--to=j.cubizolles@free.fr \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).