all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19585@debbugs.gnu.org
Subject: bug#19585: 23.4; message-mode quietly saves plaintext in draft folder (potentially remote IMAP servers)
Date: Mon, 23 Sep 2019 19:06:19 +0200	[thread overview]
Message-ID: <CAE4vfcJh2QZ6LbV-7R61BKDCueThW+3PorD+f9tM=EgTnkfcNQ@mail.gmail.com> (raw)
In-Reply-To: <87sgon8ch9.fsf@gnus.org>

> > i have a gmail+gnus setup. when a message is marked to be encrypted in
> > message-mode (with a <#secure ...> tag) then drafts of the message end
> > up being saved quietly in cleartext to the gmail drafts folder.
>
> I'm not quite sure I understand.  How does the draft end up in Gmail in
> the first place?  I didn't think Gnus supported storing the drafts on an
> IMAP server?

unfortunately i don't remember the details anymore.

i suspect what happened was something like this: i configured
gmail/IMAP as the "backend" for gnus, and the local draft folder got
linked to the gmail/IMAP draft folder.

keep in mind that i'm not an expert in gnus. i was in the process of
evaluating whether to move my emailing over to emacs when this
happened.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“It isn't enough to say: "I was mistaken"; one must say how one was mistaken.”
— Claude Bernard (1813–1878), paraphrased





  reply	other threads:[~2019-09-23 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 16:49 bug#19585: 23.4; message-mode quietly saves plaintext in draft folder (potentially remote IMAP servers) Attila Lendvai
2017-01-25 21:13 ` Lars Ingebrigtsen
2019-09-23 11:43 ` Lars Ingebrigtsen
2019-09-23 17:06   ` Attila Lendvai [this message]
2019-09-25 12:57     ` Lars Ingebrigtsen

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='CAE4vfcJh2QZ6LbV-7R61BKDCueThW+3PorD+f9tM=EgTnkfcNQ@mail.gmail.com' \
    --to=attila@lendvai.name \
    --cc=19585@debbugs.gnu.org \
    --cc=larsi@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.
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.