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

Attila Lendvai <attila@lendvai.name> writes:

>> 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.

I've had another look at the gnus-draft code, and it hard-codes
"nndraft:drafts" all over the place, and that backend (as far as I can
see) only supports storing drafts locally on disk.

So I don't see how this can happen.  :-)

I'm closing this bug report, but please reopen if anybody experiences
the same.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-09-25 12:57 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
2019-09-25 12:57     ` Lars Ingebrigtsen [this message]

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=874l10wn2w.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=19585@debbugs.gnu.org \
    --cc=attila@lendvai.name \
    /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.