From: David Greene <dag@hpe.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
"42131@debbugs.gnu.org" <42131@debbugs.gnu.org>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#42131: Cannot split to IMAP folders
Date: Tue, 08 Sep 2020 11:20:59 -0500 [thread overview]
Message-ID: <nngsgbsutn8.fsf@hpe.com> (raw)
In-Reply-To: <871rjigtgq.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> I typed B r with the point on the article in the Summary buffer and
>> selected nnimap as the split method.
>
> Sorry, I forgot that we were talking about respooling, not splitting --
> there's no split-trace buffer when doing respooling.
I didn't know there was a distinction. Is there a way to manually
"split" a message like with respooling?
> Anyway, this was the bug:
>
>> 10:02:04 [localhost] 538 APPEND "mail.misc" {622647}
>>
>> mail.misc is suspicious because B q says the message should go to a
>> different folder, on that exists. There is no mail.misc IMAP folder so
>> maybe that's why I'm having trouble.
>
> Do you have any idea where mail.misc may be coming from?
I don't. The only instance of that string that I found in my config is
in a commented line.
-David
next prev parent reply other threads:[~2020-09-08 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:31 bug#42131: Cannot split to IMAP folders David A. Greene
2020-07-07 19:52 ` Greene, David
2020-07-07 23:37 ` Eric Abrahamsen
2020-08-20 0:23 ` Stefan Kangas
2020-08-20 16:50 ` Greene, David
2020-08-20 17:57 ` Lars Ingebrigtsen
2020-08-20 18:00 ` Eric Abrahamsen
2020-08-21 15:05 ` David Greene
2020-08-22 13:31 ` Lars Ingebrigtsen
2020-08-24 13:54 ` David Greene
2020-09-04 2:35 ` Lars Ingebrigtsen
2020-09-08 16:20 ` David Greene [this message]
2020-09-08 20:31 ` Lars Ingebrigtsen
2020-09-09 7:02 ` Andreas Schwab
2020-09-09 20:47 ` David Greene
2020-09-11 11:34 ` Lars Ingebrigtsen
2020-09-14 19:22 ` David Greene
2020-09-15 12:25 ` 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
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=nngsgbsutn8.fsf@hpe.com \
--to=dag@hpe.com \
--cc=42131@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).